Re: :spelldump not working
On Mo, 23 Sep 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Hi Dimitar!
On Mo, 23 Sep 2013, Dimitar DIMITROV wrote:
Hi,
Here is what I tried:
:setlocal spelllang=bg spell
then
:spelldump
and all I get is an empty window
'local' is the issue, with a simple :set it all works.
I reckon the solution would be to take the settings from the current
window and use them in the new results window.
This patch fixes it:
[...]
Looks like this doesn't take care of 'spelllang' when it was set local
to the window.
Indeed. Here is an updated patch:
Sorry, one more update to free the allocated memory:
diff --git a/src/spell.c b/src/spell.c
--- a/src/spell.c
+++ b/src/spell.c
@@ -15580,11 +15580,21 @@
ex_spelldump(eap)
exarg_T *eap;
{
+ char_u *spl;
+ long dummy;
+
if (no_spell_checking(curwin))
return;
/* Create a new empty buffer by splitting the window. */
+ get_option_value((char_u*)spl, dummy, spl, OPT_LOCAL);
do_cmdline_cmd((char_u *)new);
+
+ /* enable spelling locally */
+ set_option_value((char_u*)spell, TRUE, (char_u*), OPT_LOCAL);
+ set_option_value((char_u*)spl, dummy, spl, OPT_LOCAL);
+ vim_free(spl);
+
if (!bufempty() || !buf_valid(curbuf))
return;
Mit freundlichen Grüßen
Christian
Hi Bram,
Just wanted to make sure this path hadn't gone unnoticed,
Cheers
Dimitar Dimitrov
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
dw (or any operator) not working at end of line and beyond
Test done with the latest version out of mercurial Hi, Here is a bug: if you place your cursor at the end of a line and try dw, all that happens is the character under cursor is deleted but the line is not joined with the one below. de however is ALMOST working meaning that it does work in the usual settings but not with :se ve=all. In that case, if you go beyond the end of a line the joining of lines happens but your cursor position changes to the end of line instead of remaining in its place. Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
:spelldump not working
Test done with the latest version from Mercurial Hi, Here is what I tried: :setlocal spelllang=bg spell then :spelldump and all I get is an empty window 'local' is the issue, with a simple :set it all works. I reckon the solution would be to take the settings from the current window and use them in the new results window. Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: dw (or any operator) not working at end of line and beyond
Test done with the latest version out of mercurial Hi, Here is a bug: if you place your cursor at the end of a line and try dw, all that happens is the character under cursor is deleted but the line is not joined with the one below. hm, dw deletes just the last character on the line but vw highlights that and also the first character on the next line. w by itself is an exclusive motion, though. You make me wonder if it's a bug or a feature. Aah, found it (a few paragraphs below :help word and :help WORD): Another special case: When using the w motion in combination with an operator and the last word moved over is at the end of a line, the end of that word becomes the end of the operated text, not the first word in the next line. the end of that word becomes the end of the operated text, so it is indeed a feature, or at least something documented in the help. You are right, I should have read the help de however is ALMOST working meaning that it does work in the usual settings but not with :se ve=all. In that case, if you go beyond the end of a line the joining of lines happens but your cursor position changes to the end of line instead of remaining in its place. For me, de with ve=all and the cursor beyond the end of the line removes the end-of-line and the first word of the next line. So, the place where the cursor was just before I issued the command doesn't exist anymore, and it goes, quite logically IMHO, to the first character after the deleted EOL and word. You are also right, although in this case I think the cursor not moving would feel more natural with ve=all. I use this setting and I am used to the cursor never moving. Ex: rr when past the line creates all necessary spaces and keeps the cursor where it is the e motion is described as forward to end of word, inclusive, doesn't stop on an empty line. Regards Dimitar What is 'selection' set to on your installation? :verbose set sel? with question mark Mine is set to inclusive. inclusive as well Best regards, Tony. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: cgn nowrapscan-like issue
Tested with the latest version of Vim from Mercurial. After a * search, then cgn and then . to repeat it for all matches, I cannot continue past the end of file and change any matches before my initial position Try the attached patch. That fixes it, thanks Dimitar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
cgn nowrapscan-like issue
Hi, Tested with the latest version of Vim from Mercurial. After a * search, then cgn and then . to repeat it for all matches, I cannot continue past the end of file and change any matches before my initial position Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
setpos() and up = wrong position
Hi all,
I will use the following text as an example:
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis
nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure [d]olor in reprehenderit in voluptate velit esse cillum dolore
eu
fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
culpa qui officia deserunt mollit anim id est laborum.
My cursor is on [d] as shown above:
Now try :ec getpos('.') - [0, 4, 17, 0]
Move away and :call setpos('.',[0,4,17,0])
If you use up down k or j you will not move just above/below the char but
in some weird location
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
mitk...@yahoo.fr
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: setpos() and up = wrong position
If you use up down k or j you will not move just above/below the char but in some weird location My vim 7.4 doesn't do this, but 7.3.547 does, so it looks like a bug that's been fixed. I used version 7.4 with Included patches: 1-5 so not sure how come you're not seing it. Also used: vim -nNX -u NONE Regards, John Little Dimitar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: I wish I had known this earlier; please put it in the docs!
On Mon, Aug 19, 2013 at 3:53 PM, Manuel Ortega mannyvim...@gmail.com wrote: Dear Bram, While perusing $VIMRUNTIME/syntax/vim.vim, I noticed that many of the attributes to the command :command can be abbreviated. Namely: instance: -n[args] -com[plete] -ra[nge] -cou[nt] -re[gister] -ban[g] I didn't ever know this before. No wonder! As far as I can tell, there is nothing at all in the docs that says this can be done. It's not in :h :command after scrolling down. It's not in usr_40.txt. Even :helpg comes up empty when fed -n=, -ra=, etc. This is VERY useful info and I could really have used it years ago. Please add it to the docs. It should be included in the relevant subheadings of :h :command, such as :h command-nargs and so forth. One shouldn't have to be poking through a super-complicated syntax file to discover things like this :) In fact, not only was none of this in the docs, but I couldn't find ANY *usages* of it ANYWHERE in the entire runtime directory, except for 4 occurrences of -na= (which isn't even as short as it could be) in the vimball plugin. So I conclude I'm not the only one who didn't know about it :) Your point about the lack of documentation is well taken. However, I would not conclude that absence of use is evidence of absence of knowledge. The only time those arguments are used is when defining a command, which is almost always done in one's .vimrc or in a plugin and hardly ever done from the command line, so there is little advantage to the shorter form. Further, the shorter form are significantly less intelligible. Whenever I put a Vim command in my .vimrc or in a plugin, I almost always use the long form of all commands simply because I think it is easier to understand. If I looked at a command definition that contained -ban for example, I would wonder what the heck that meant, whereas I would immediately know what -bang meant. When I'm defining a command, the difference in time or space between typing the long form and the short form is insignificant. Agreed. Just wanted to mention a few very usefull :help related shortcuts not very well known: :h i^x^n Vs :help i_CTRL-X_CTRL-N :h^x^n works as well (no spaces needed, ^x can be entered as caret+x or c-v followed by c-x) :h:: Regards, Gary Dimitar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
omap puzzle
Hi all, I've noted this behaviour with omaps: in my omap I jump to a place in the buffer, then after an if test I select visually something. So all is good when the test succeds and only the visual area gets modified. Now if the test fails, no visual selection is created and the omap acts on my motion in the buffer instead of being cancelled. Is there a way to tell in the test, if it fails to cancel the omap? Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: omap puzzle
Hi all, I've noted this behaviour with omaps: in my omap I jump to a place in the buffer, then after an if test I select visually something. So all is good when the test succeds and only the visual area gets modified. Now if the test fails, no visual selection is created and the omap acts on my motion in the buffer instead of being cancelled. Is there a way to tell in the test, if it fails to cancel the omap? I think this question belongs on the vim_use list. Try returning Esc. BTW: Have you tried the patch yet? Hi Christian, Sorry for not doing the test earlier, just tried and yes your patch fixes the issue (gUgn) thanks! Could you explain how to return esc and ok, I will ask next time in the right list. I tried: return 'esc', execute ':normal! esc', feedkeys(\cr) and none worked regards, Christian -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
vaB issue with :se ve=all
Hi,
First vim -nNX -u NONE ad :se ve=all
Then enter the following test with X representing the cursor:
if {
X
}
Now vaB is wrong
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
mitk...@yahoo.fr
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vaB issue with :se ve=all
Hi,
First vim -nNX -u NONE ad :se ve=all
Then enter the following test with X representing the cursor:
if {
X
}
Now vaB is wrong
I don't see anything wrong. For me it selects all text from the opening { to
the closing }. What do you see?
I tried gvim 7.3.822 on Windows, and also vim (not gvim) 7.4b.14 on Solaris,
both with Huge features. What version are you using?
Obviously I wasn't clear enough here so I will detail a bit:
First of all, because I am setting 've to all I hope it is clear that my cursor
is simply where it is without any white spaces before = so in 'virtual' space
And what I get is:
if {
*
*
*
*
*
*
*
*
*
}X
* representing visual selection
Instead of
if {*
*
*
*
*
*
*
*
*
*
}
I used latest vim from hg to perform the test
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
gUgn not repeated with .
As per the subject :) Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: gUgn not repeated with .
As per the subject :) Verified that . has no effect after a gUgn that capitalized a match for the last search, on 7.3.822 Windows, and also 7.4b.14 on Solaris. Doesn't work for g~ either (or ~ with 'top set). Haven't checked the others Dimitar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Highlighting not refreshed after setting smartcase
Hi, Not sure this is an actual issue. In a buffer enter this text: loRem lorem then set hls ic Now search for /loRem and you have 2 matches Finally, after set smartcase the highlighting is not refreshed Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
paragraph object issue
Hi all, If you open the latest vim (vim -nNX -u NONE) and insert these lines: .jpg 01;35 .jpeg 01;35 .gif 01;35 .bmp 01;35 .pbm 01;35 .pgm 01;35 .ppm 01;35 .tga 01;35 .xbm 01;35 .xpm 01;35 .tif 01;35 .tiff 01;35 .png 01;35 .svg 01;35 .svgz 01;35 .mng 01;35 .pcx 01;35 .mov 01;35 .mpg 01;35 .mpeg 01;35 .m2v 01;35 .mkv 01;35 .webm 01;35 .ogm 01;35 .mp4 01;35 .m4v 01;35 .mp4v 01;35 .vob 01;35 .qt 01;35 .nuv 01;35 .wmv 01;35 .asf 01;35 .rm 01;35 .rmvb 01;35 .flc 01;35 .avi 01;35 .fli 01;35 .flv 01;35 .gl 01;35 .dl 01;35 .xcf 01;35 .xwd 01;35 .yuv 01;35 .cgm 01;35 .emf 01;35 then go to the top (gg) and try vap... There is an issue Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: paragraph object issue
Hi all, If you open the latest vim (vim -nNX -u NONE) and insert these lines: .jpg 01;35 .jpeg 01;35 .gif 01;35 .bmp 01;35 .pbm 01;35 .pgm 01;35 .ppm 01;35 With no filetype, a paragraph is defined by the 'paragraphs' setting. The '.pp' beginning the above line is treated as one of the `nroff` macros that typically starts a paragraph. [...] then go to the top (gg) and try vap... There is an issue Not an issue. Just a weird historical default. Indeed, I was editing my ~/.dir_colors and it surprised me. I should only use these defaults for nroff files, otherwise :se para= Cheers For more info, see: :help paragraph Dimitar Dimitrov -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
autocmd wrong example
Hi, I was reading :h40.3 and tried the example from line 446. That never worked because FileWritePre is irrelevant and BufWritePre should be used Cheers Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Strange pattern matches for \_.*
Hi all, Not sure why /\_.* matches at every line Vs only once... I would expect a single match at start of file because \_. matches any char including end of line and * is greedy /pattern\_.* does what I expect: it matches from pattern to end of file Dimitar An update/clarification on this: :%s/\_.* does correctly erase the whole file. What is actually incorrect and I didn't explain it well in my above statement is the behaviour of n, N. /, :/ So, n goes to every line Vs stay at the first byte of the file and never move Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Strange pattern matches for \_.*
Hi all, Not sure why /\_.* matches at every line Vs only once... I would expect a single match at start of file because \_. matches any char including end of line and * is greedy /pattern\_.* does what I expect: it matches from pattern to end of file Dimitar An update/clarification on this: :%s/\_.* does correctly erase the whole file. What is actually incorrect and I didn't explain it well in my above statement is the behaviour of n, N. /, :/ So, n goes to every line Vs stay at the first byte of the file and never move I think this is correct. \_.* doesn't say, Vim should start matching only at the start of the file, so Vim will try matching at each line again. I disagree, following your logic, after /lorem\_.*ipsum and the following file: lorem ipsum n would move us to both lines which is not correct The point is not about matching at the start of the file. What I am saying is, because there is only one match, that's what should happen. I think, Vim has always done this and restarted trying to match after linebreaks. If you want to keep matching at the start of the file, use the \%^ atom. regards, Christian Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Strange pattern matches for \_.*
Hi all, Not sure why /\_.* matches at every line Vs only once... I would expect a single match at start of file because \_. matches any char including end of line and * is greedy /pattern\_.* does what I expect: it matches from pattern to end of file Dimitar An update/clarification on this: :%s/\_.* does correctly erase the whole file. What is actually incorrect and I didn't explain it well in my above statement is the behaviour of n, N. /, :/ So, n goes to every line Vs stay at the first byte of the file and never move I think this is correct. \_.* doesn't say, Vim should start matching only at the start of the file, so Vim will try matching at each line again. I disagree, following your logic, after /lorem\_.*ipsum and the following file: lorem ipsum n would move us to both lines which is not correct Of course not. the lorem part doesn't match at the next line (ipsum). Try this example: aann nnbb and search for /n\_[n]* All I am trying to say is that this is a *single* match (/n\_[n]* matches *all* n in your example) so a single n move would make more sense, same as in this non-multiline pattern: aa, /a* is a single match and n won't move once for every letter hitting n will move you to the next line. regards, Christian Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Strange pattern matches for \_.*
Hi all, Not sure why /\_.* matches at every line Vs only once... I would expect a single match at start of file because \_. matches any char including end of line and * is greedy /pattern\_.* does what I expect: it matches from pattern to end of file Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[PATCH] makeprg for gcc
Hi, Found that many default compiler plugins lacked the makeprg setting. I basically opened a perl file, then a c file and tried to compile it with :mak and it tried to use perl -c this patch fixes it for gcc: *** gcc.vim 2013-07-23 12:32:14.0 +0100 --- /tmp/gcc.vim 2013-07-23 12:32:08.453563055 +0100 *** *** 11,16 --- 11,17 let s:cpo_save = cpo set cpovim + CompilerSet makeprg=gcc\ %\ $* CompilerSet errorformat= \%*[^\]\%f\%*\\D%l:%c:\ %m, \%*[^\]\%f\%*\\D%l:\ %m, Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] makeprg for gcc
Hi, Found that many default compiler plugins lacked the makeprg setting. I basically opened a perl file, then a c file and tried to compile it with :mak and it tried to use perl -c this patch fixes it for gcc: *** gcc.vim 2013-07-23 12:32:14.0 +0100 --- /tmp/gcc.vim 2013-07-23 12:32:08.453563055 +0100 *** *** 11,16 --- 11,17 let s:cpo_save = cpo set cpovim + CompilerSet makeprg=gcc\ %\ $* CompilerSet errorformat= \%*[^\]\%f\%*\\D%l:%c:\ %m, \%*[^\]\%f\%*\\D%l:\ %m, For C programs, 'makeprg' should not be gcc, it should be make. The makefile specifies the compiler and how it is to compile the program. Ok, I realize it now. I should have used a Makefile. Also the message states it. But in fact there is still an issue. If you fist open a perl file (as an example) and right after you open a c file, makeprg is not updated. Is this intentional and the user is supposed to run :comp gcc? Regards, Gary Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Vim slow after big count insert
There is no use case If you do something stupid by accident most vim operations can be aborted by ctrl-c (exception: python, rbuy, .. scripts) Try to abort it you will see the success you have. So there is still nothing to fix or talk about unless there is a use case. Marc Weber Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Vim slow after big count insert
Hi, Did a search on the vim_dev archives but couldn't find anything related to this. Sorry if this is redundant. Basically vim is exponentially slow after 100iHello esc as mentionned in this link: http://www.galexander.org/vim_sucks.html Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
$MYVIMRC not set
Hi, After reading the docs about -u, I can't see it mentioned that in that case $MYVIMRC wouldn't be setup. But it isn't. Try with vim -u ~/.vimrc Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
:global wrong delimiters
Hi list, From :h:g (line 57) I get it :g9pattern9ACTION shouldn't work, but it does. These work as well: :gpatternACTION :g|pattern|ACTION Regards Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Vim slow after big count insert
Hi,
Did a search on the vim_dev archives but couldn't find anything related to
this. Sorry if this is redundant.
Basically vim is exponentially slow after 100iHello esc as mentioned
in this link:
http://www.galexander.org/vim_sucks.html
Let's discuss the use case, first. Is there one ? If not let's forgett
about it ..
There is no use case I suppose but you could end doing this accidentally as
this guy mentioned in the link.
Also fixing it may have wider implications and end up speeding Vim in other
parts.
Vim sucks in many ways - but on average it is very helpful for me.
You could try c-r=repeat('Hello', insanely-large-int)cr as
alternative - maybe its faster, maybe its not, I don't want to wait
50 min for this case unless there is a use case.
Marc Weber
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
mitk...@yahoo.fr
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
:set show values when it shouldn't
Hi all, According to :h:se, :se isn't supposed to output anything at all when in default mode but it does when started like this: command vim -nNX -u NONE Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
:set show values when it shouldn't
On 2013-07-17, Gary Johnson wrote: On 2013-07-17, Dimitar DIMITROV wrote: Hi all, According to :h:se, :se isn't supposed to output anything at all when in default mode but it does when started like this: command vim -nNX -u NONE Actually, :help :set doesn't say that--it says it shows all options that differ from their default value. Vim usually considers options that it sets itself as a result of external factors to be different from their default values. What options are you seeing? I would expect you to be seeing at least noloadplugins because you used -n and updatecount=0 because you used -u NONE. Oops. I meant: I would expect you to be seeing at least updatecount=0 because you used -n and noloadplugins because you used -u NONE. Regards, Gary Thanks Gary, I get it. This is what :se shows for me: helplang=en noloadplugins scroll=25 ttyfast ttymouse=sgr updatecount=0 fileencodings=ucs-bom,utf-8,default,latin1 After reading more carefully I see that the above are not default values and why they are set, except for 'helplang maybe for which the help is not very clear about the default value. Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Main help display issue
Hi all, 1. command vim -nNX -u NONE 2. :h 3. :on 4. :se cole=2 lbr 5. :sy on Now you can see a misaligned paragraph starting on line 36 First tought this was a tab vs space issue as you can see with :se list but 'cole is somehow also involved as setting it to 0 removes the misalignment Cheers Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
k moves to incorrect column after g$
Hi list, 1. vim -nNX -u NONE 2. :se ve=all 3. 3otestesc 4. g$ Then I expect k to move me up in the same column but it goes at $ in the previous line. Note: in step 4 if I move to g$ using l then k moves the cursor correctly Cheers PS: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
vim stops
Hi, running the latest version of vim (from mercurial) I experience the following weird behaviour: 1. command /usr/local/bin/vim -nNX -u NONE 2. shift (hold on to z then simultaneosly press shift) Vim stops Ran it under valgrind but it reports: definitely lost: 0 bytes in 0 blocks Version: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: vim stops
No, I didn't right ZZ but zz. It's different :) Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr De : tooth pik toothp...@gmail.com À : vim_dev@googlegroups.com Envoyé le : Lundi 8 juillet 2013 14h36 Objet : Re: vim stops On Mon, Jul 08, 2013 at 02:05:19PM +0100, Dimitar DIMITROV wrote: Hi, running the latest version of vim (from mercurial) I experience the following weird behaviour: 1. command /usr/local/bin/vim -nNX -u NONE 2. shift (hold on to z then simultaneosly press shift) Vim stops it's a feature -- ZZ is a quit command -- see :h ZZ -- _|_ _ __|_|_ ._ o| |_(_)(_)|_| ||_)|| | -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Vim stops
Resending this as apparently it wasn't clear, hope it is now Hi, running the latest version of vim (from mercurial) I experience the following weird behaviour: 1. command /usr/local/bin/vim -nNX -u NONE 2. shift explanation: press z and hold for a few seconds now while pressing z, press also shift so it results in +shift NOT ZZ or shift+z Vim stops Ran it under valgrind but it reports: definitely lost: 0 bytes in 0 blocks Version: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
modeless-selection distorts all characters in gVim
And here is my version of gVim :ve VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 13 2012 20:47:10) Included patches: 1-409 Modified by Gentoo-7.3.409 Compiled by root@winterfell Huge version with GTK2-GNOME GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg +path_extra -perl +persistent_undo +postscript +printer +profile +python -python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: /etc/vim/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc system gvimrc file: /etc/vim/gvimrc user gvimrc file: $HOME/.gvimrc system menu file: $VIMRUNTIME/menu.vim fall-back for $VIM: /usr/share/vim Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2 .0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/libdrm -DORBIT 2=1 -pthread -D_REENTRANT -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring- 1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/g dk-pixbuf-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib64/gnome-vfs-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/ lib64/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1 .0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/cairo -I/usr/in clude/pixman-1 -I/usr/include/libpng15 -I/usr/include/libdrm -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -L/usr/local/lib -Wl,--as-needed -o gvim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -lart_l gpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgconf-2 -lgthread-2.0 -lgmodule-2.0 -lrt -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lelf -lcurses -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynami c Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: modeless-selection distorts all characters in gVim
On Wed, Apr 17, 2013 at 11:06 AM, Ben Fritz fritzophre...@gmail.com wrote: See image attached to my next message for what I see. And please bottom-post. Thanks Ben, can't see clearly your image but maybe indeed the bug was fixed in your version. Here is what I see (attached image) Thanks for sending the screenshot. I don't see character distortion, so I assume you're talking about the partial white background on some of the letters. So, it looks to me like the following is a description of your problem: 1. You launched gvim 7.3.409 on operating system. 2. You entered :e and then stayed in command-line mode 3. You selected some text *in the buffer* with the mouse 4. You see white backgrounds under some of your black letters within the selection Is this a correct problem description? If so, WHAT OPERATING SYSTEM ARE YOU USING? I don't see your issue still in Windows 7. Hi Ben, Sorry for not mentioning this. These are my OS details: Distribution: Gentoo Base System release 2.1 Machine hardware name: x86_64 Hardware platform: GenuineIntel Processor type: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Kernel name: Linux Kernel release: 3.7.10-gentoo Compiled on: #1 SMP Tue Apr 2 13:12:22 BST 2013 Operating system: GNU/Linux You are also correct that this is not distortion but background coloring issues. The background color was white in my screenshot but can be of any color in a syntax highlighted code file. Turns out I used :e but this simply happens in modeless selection and not only *in the buffer* but anywhere, command line included. Regards -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
modeless-selection distorts all characters in gVim
Hi, Anyone knows why in gVim modeless-selection distorts all characters which makes the selection quite unreadable? Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: modeless-selection distorts all characters in gVim
Hi Ben, what I meant is modeless selection (:h modeless) so try to select the text after using :e for instance (and before hitting esc or ^c of course) Cheers Note: my gVim version is: 7.3.409 Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr De : Ben Fritz fritzophre...@gmail.com À : vim_dev@googlegroups.com Cc : Dimitar DIMITROV mitk...@yahoo.fr Envoyé le : Mercredi 17 avril 2013 16h17 Objet : Re: modeless-selection distorts all characters in gVim On Wednesday, April 17, 2013 9:23:58 AM UTC-5, Dimitar DIMITROV wrote: Hi, Anyone knows why in gVim modeless-selection distorts all characters which makes the selection quite unreadable? Works fine for me on gvim 7.3.822 in Windows 7 64-bit. When I am in normal mode, and use the mouse to select some text in my buffer, the text looks unchanged to me (aside from being highlighted). :set mouse? selectmode? mouse=a selectmode=mouse,key Can you provide more detail as to your system, configuration, and steps taken to see the problem? And maybe a screenshot too? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: modeless-selection distorts all characters in gVim
Dimitar wrote: On Wed, Apr 17, 2013 at 11:06 AM, Ben Fritz fritzophre...@gmail.com wrote: See image attached to my next message for what I see. And please bottom-post. Thanks Ben, can't see clearly your image but maybe indeed the bug was fixed in your version. Here is what I see (attached image) -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. attachment: screen.png
unnamedplus issue
On Tuesday, February 12, 2013 8:38:02 AM UTC-6, Dimitar DIMITROV wrote: Hi Ingo, You did explain the help for 'unnamedplus but there is still the problem I described: 1. gvim -NX -u NONE -c 'se cb^=unnamedplus' I use Windows gvim, where the -X flag does nothing according to the help, so I started with: gvim -N -u NONE -i NONE 2. iLorem ipsum doloresc 3. yvbgevbp = E353: Nothing in register + I would have expected a result of: Lorem dolor dolor Without clipboard equal to unnamedplus I get the expected result. With clipboard equal to either unnamedplus or unnamed I do not get any error message. However, I also see no changes to the text. The reason the text does not change is that the deleted text is placed into the '+' register before pasting from this register. I thought this was fixed in a patch recently but I don't see any such patch in ftp://ftp.vim.org/pub/vim/patches/7.3/README. Maybe I just remember a thread without a patch? I don't know why you're getting the nothing in register error. Maybe because you're using the -X startup flag, which explicitly tells Vim NOT to connect to X? Thanks Ben, all my bad, you are right, when not using -X it works according to the docs. Not sure why you are having the issue you describe. Thanks for your help and apologies to the list. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
unnamedplus issue
Hi, 1. gvim -NX -u NONE -c 'se cb^=unnamedplus' 2. iLorem ipsum doloresc 3. yvbgevbp = E353: Nothing in register + I would have expected a result of: Lorem dolor dolor Also, I can't make sense of the help for 'unnamedplus. It reads that all operations except yank go to +, then first thing it says after is yank copies to +. Can someone explain? Cheers Dimitar Vim version: VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 17 2012 15:42:46) Included patches: 1-409 Modified by Gentoo-7.3.409 Compiled by root@winterfell Huge version with GTK2-GNOME GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg +path_extra -perl +persistent_undo +postscript +printer +profile +python -python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: /etc/vim/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc system gvimrc file: /etc/vim/gvimrc user gvimrc file: $HOME/.gvimrc system menu file: $VIMRUNTIME/menu.vim fall-back for $VIM: /usr/share/vim Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/ include/libdrm -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 - I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib64/gnome-vfs-2.0/include -I/usr/i nclude/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/u sr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng15 -I/usr/include/libdrm -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -L/usr/local/lib -Wl,--as-needed -o gvim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_p ixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-acti vation -lORBit-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgconf-2 -lgthrea d-2.0 -lgmodule-2.0 -lrt -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lelf -lcurses -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config -lpython2.7 - lpthread -ldl -lutil -lm -Xlinker -export-dynamic --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: gf - incorrect behaviour
Hi all,
I think the following might (I am testing with Vim 7.3.409) be a bug:
command vim -nNX -u NONE
then insert: bla:///path/to/file
then, with cursor being on p, use gf
It tries to open bla:///path/to/file although : is not in 'isf and bla:/// =
isn't a protocol
I haven't checked the sources but I think this is hard coded.
It's intentional that this does not depend in 'isfname', so that things
like http:// work with the default 'isfname' value.
Is this really a problem?
It's an issue with puppet code which uses paths like:
puppet:///modules/module_name/my_file that maps to real paths like
$base_path/modules/module_name/files/my_file
I wanted to be able to use gf with 'inex in order to be able to open 'my_file'
this is the 'inex I was trying to use: set
includeexpr=substitute(v:fname,'modules/.\\{-1,}/\zs','files/','')
If puppet is the only language using this kind of paths, no, this is not a real
issue
--
hundred-and-one symptoms of being an internet addict:
208. Your goals for the future are obtaining an T1 connection and
a 130 gig hard drive.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
gf - incorrect behaviour
Hi all, I think the following might (I am testing with Vim 7.3.409) be a bug: command vim -nNX -u NONE then insert: bla:///path/to/file then, with cursor being on p, use gf It tries to open bla:///path/to/file although : is not in 'isf and bla:/// isn't a protocol Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
:global// bug
Hi, I don't have the latest version of Vim installed, so this might not be a real bug. Please check! 1. 60obuttercrchocolateesc (120 lines) 2. qwq 3. :g/butter/y W 4. at the -- More -- prompt hit q 5. in a new window: wP Result: you have copied only half the words (or a screenfull in fact) :silent g/butter/y W will do it but if you hadn't thought about using :silent, you would have to use G on the -- More -- prompt in order to have the correct result. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
:global// bug [2]
Hi, Sorry, forgot to mention that you need :set report=0 Cheers -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Dictionary completion problem
Hi all, I have maybe found a little issue: 1. vim -N -u NONE -U NONE 2. :imap c-k c-oD 3. :set spell 4. inoc-xc-k Instead of trying to complete using the 'dict option, it is trying to use the mapping... Also, in insert.txt line 64: 'The key that ends CTRL-X mode (any key that is not a valid CTRL-X mode command) is mapped' What means that the key is mapped? Cheers -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Weird highlightings after /pattern + ^f
Hi all, Here is what to do (tried on windows only): 1. gvim.exe -u NONE -U NONE -N 2. i(oge)esc 3. :se iscr 4. /(oge)^f 5. Now just go up/down, left/right and there will be weird highlightings everywhere Version: 7.3, 1-138 PS: Sorry if this has already been reported Dimitar Dimitrov -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Possible lazyredraw bug
Hi, On windows XP: 1. I did: gvim.exe -u NONE -U NONE -N then :ls which displays :ls 1 %a [No Name]line 1 Press ENTER or type command to continue 2. Then I did: :set lazyredraw, and this time :ls wouldn't display anything Tested with Vim 7.3, 1-138 Dimitar Dimitrov -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : tr() problem ?
Thanks James,
I'll use \u0440 as you suggested
D
De : James Vega james...@jamessan.com
À : vim_dev@googlegroups.com
Envoyé le : Mer 9 février 2011, 19h 10min 55s
Objet : Re: tr() problem ?
On Wed, Feb 9, 2011 at 12:04 PM, Dimitar DIMITROV mitk...@yahoo.fr wrote:
But this doesn't:
command! Translate call setline(line('.'), tr(getline('.'),
\'ABVGDEWZIJKLMNOPRSTUYFHXC$^}{!|Qabvgdewzijklmnoprstuyfhxc467][1\q',
\'АБВГДЕЖЗИЙКЛМНОПРСТУYФХXЦЧШЩЪЬЮЮЯабвгдежзийклмнопрстуyфхxцчшщъьююя'))
then :Translate on any line
The error is:
E475: Invalid argument:
ABVGDEWZIJKLMNOPRSTUYFHXC$^}{!|Qabvgdewzijklmnoprstuyfhxc467][1\q
This has something to do with how Vim is storing the U+0440 character
(which breaks down to \xd1\x80) in the to string. A minimal
reproduction can be done with this simplified version:
command! Translate echo tr(getline('.'), 'r', 'р')
and then use Translate with your cursor on the line defining the
command.
In fact, if you use the following erroneous version of the command, the
error string that Vim prints when you try to use :Translate will show
that the U+0440 character has been corrupted:
command! Translate echo tr(getline('.'), 'r', \'p')
I end up getting: E15: Invalid expression: \'рfeX')
Everything works fine if the command is defined using \u0440 instead
of the literal character.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@jamessan.com
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Re : E315: ml_get: invalid lnum
Dimitar DIMITROV wrote: Hi, 1. :help 2. 10GVjesc 3. :ene 4. Use MiddleMouse to paste the text but don't do it above line 1 5. u 6. Use MiddleMouse to paste the text and do it above line 1 7. ddu^R Error message: E315: ml_get: invalid lnum: 3 E315: ml_get: invalid lnum: 3 I can't reproduce it. What would be useful, is for you to put a breakpoint in a debugger at memline.c:2452 where E315 happens and send us the stack. I suspect that a plugin has an autocommand which could trigger this. Which plugins are you using? What autocommands are in your ~/.vimrc? How about also enabling plugins one at at time to see which once triggers the bug. -- Dominique Thanks for the suggestions. I was finally able to isolate the problem. The above steps will raise the error if one starts like this (see below) AND the MiddleMouse clicks are NOT above column one: gvim.exe +se nocp ve=all nosol -u NONE -U NONE I love ve=all but it seems to be a bit fragile -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : E315: ml_get: invalid lnum
Dimitar Dimitrov wrote: 1. :help 2. 10GVjesc 3. :ene 4. Use MiddleMouse to paste the text but don't do it above line 1 5. u 6. Use MiddleMouse to paste the text and do it above line 1 7. ddu^R Error message: E315: ml_get: invalid lnum: 3 E315: ml_get: invalid lnum: 3 :version VIM - Vi IMproved 7.3d BETA (2010 Aug 4, compiled Aug 4 2010 18:38:10) MS-Windows 32-bit GUI version with OLE support I don't see the error. When doing dd, which line are you deleting? The last one Did you start with vim -u NONE? I hadn't. Now I did and there is a different error. At the end we still should have one line but all disappears. Here is how you can reproduce it: gvim.exe -u NONE -U NONE :help yy ^w^w p u P j dd u ^r -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : Re : E315: ml_get: invalid lnum
Right... Just tried: gvim.exe +se nocp -u NONE -U NONE None of the errors is triggered Cheers De : Lech Lorens lech.lor...@gmail.com À : vim_dev@googlegroups.com Envoyé le : Ven 6 août 2010, 11h 05min 59s Objet : Re: Re : E315: ml_get: invalid lnum On 6 August 2010 10:56, Dimitar DIMITROV mitk...@yahoo.fr wrote: I hadn't. Now I did and there is a different error. At the end we still should have one line but all disappears. Here is how you can reproduce it: gvim.exe -u NONE -U NONE :help yy ^w^w p u P j dd u ^r This is not an error. This is due to Vim being run in Vi-compatible mode. Try removing 'u' from 'cpoptions'. -- Regards, Lech Lorens -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
PHP syntax script problem
Hi,
When using
:vglobal/\S/,/\S/-j|noh (this reduces several empty lines following one another
to just one line)
on a php file:
?php
class Test {
public function init()
{
echo '1';
echo '2';
echo '3';
echo '4';
echo '5';
}
}
with
:set foldmethod=syntax
and everything folded (zM)
the code is scrambled:
?php
class Test {
public function init()
{
echo '1';
echo '2'; echo '3'; echo '4'; echo '5'; }
}
I imagine this is a PHP syntax script problem
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
E315: ml_get: invalid lnum
Hi, 1. :help 2. 10GVjesc 3. :ene 4. Use MiddleMouse to paste the text but don't do it above line 1 5. u 6. Use MiddleMouse to paste the text and do it above line 1 7. ddu^R Error message: E315: ml_get: invalid lnum: 3 E315: ml_get: invalid lnum: 3 :version VIM - Vi IMproved 7.3d BETA (2010 Aug 4, compiled Aug 4 2010 18:38:10) MS-Windows 32-bit GUI version with OLE support Compiled by b...@kibaale Big version with GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole -osfiletype +path_extra +perl/dyn +persistent_undo -postscript +printer -profile +python/dyn +python3/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save +xpm_w32 system vimrc file: $VIM\vimrc user vimrc file: $HOME\_vimrc 2nd user vimrc file: $VIM\_vimrc user exrc file: $HOME\_exrc 2nd user exrc file: $VIM\_exrc system gvimrc file: $VIM\gvimrc user gvimrc file: $HOME\_gvimrc 2nd user gvimrc file: $VIM\_gvimrc system menu file: $VIMRUNTIME\menu.vim Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL - DNDEBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\tcl83.dll\ -DDYNAMIC_TCL_VER=\8.3 \ -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\ -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\python31.dll\ -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DL L=\perl512.dll\ -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\msvcrt-ruby191.dll\ -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi 32.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib /nodefaultlib:python27.lib /nodefaultlib:pytho n31.lib e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib /PDB:gvim.pdb -debug -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : PHP syntax script problem
Hi,
When using
:vglobal/\S/,/\S/-j|noh (this reduces several empty lines following one
another
to just one line)
on a php file:
?php
class Test {
public function init()
{
echo '1';
echo '2';
echo '3';
echo '4';
echo '5';
}
}
with
:set foldmethod=syntax
and everything folded (zM)
the code is scrambled:
?php
class Test {
public function init()
{
echo '1';
echo '2'; echo '3'; echo '4'; echo '5'; }
}
I imagine this is a PHP syntax script problem
I forgot to precise:
:version
VIM - Vi IMproved 7.3d BETA (2010 Aug 4, compiled Aug 4 2010 18:38:10)
MS-Windows 32-bit GUI version with OLE support
Compiled by b...@kibaale
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+conceal +cryptv +cscope
+cursorbind +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path
+float +folding -footer +gettext/dyn
-hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
+mouse +mouseshape
+multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole -osfiletype
+path_extra +perl/dyn +persistent_undo -postscript +printer -profile
+python/dyn
+python3/dyn +quickfix +reltime
+rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +startuptime
+statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white
+tcl/dyn -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-xfontset -xim -xterm_save +xpm_w32
system vimrc file: $VIM\vimrc
user vimrc file: $HOME\_vimrc
2nd user vimrc file: $VIM\_vimrc
user exrc file: $HOME\_exrc
2nd user exrc file: $VIM\_exrc
system gvimrc file: $VIM\gvimrc
user gvimrc file: $HOME\_gvimrc
2nd user gvimrc file: $VIM\_gvimrc
system menu file: $VIMRUNTIME\menu.vim
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400
-D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -D
NDEBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32
-DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL
-DDYNAMIC_TCL_DLL=\tcl83.dll\ -DDYNAMIC_TCL_VER=\8.3\
-DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\
-DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\python31.dll\
-DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\
perl512.dll\ -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191
-DDYNAMIC_RUBY_DLL=\msvcrt-ruby191.dll\ -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib
kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib
uuid.lib
/machine:i386 /nodefaultlib gdi3
2.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib
/machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib
/nodefaultlib:python27.lib /nodefaultlib:python3
1.lib e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib
/PDB:gvim.pdb
-debug
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Re : A few notes
Dimitar Dimitrov wrote: On 29/07/10 10:49, Dimitar DIMITROV wrote: Hi, I've noticed that there is no mention in the help files that one can use things like: 1. :h i^x^k or even :h^x^k instead of :h i_CTRL-X_CTRL-K 2. [count] gqq will format count lines Cheers -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php I didn't know about i^x, but I knew about :help :| and :help x (and similar) which will replace | by bar or by quote. I don't know if it's documented anywhere either. i^x^k doesn't work, at least not if compiled with +digraphs (the Ctrl-K waits for a digraph or special key). You can type ^ then k. For ^x you can use the Ctrl modifier Best regards, Tony. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
A few notes
Hi, I've noticed that there is no mention in the help files that one can use things like: 1. :h i^x^k or even :h^x^k instead of :h i_CTRL-X_CTRL-K 2. [count] gqq will format count lines Cheers -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
tab Competing after ~ on Windows
Hi, On linux systems I can open Vim and type: :e~/dtab which expands (for me) to :e~/dev/ and I can go on... but on Windows: :e~/dtab expands to :eD:\dev\ and therefore I can't go on with my completion unless I start over again using :e ~/dtab (note the space) The whole point is: I need a space before trying to complete after ~ which I would like to avoid -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Tr : Re : Minor problems...
- Message transféré De : Dimitar DIMITROV mitk...@yahoo.fr À : Bram Moolenaar b...@moolenaar.net Envoyé le : Mar 27 juillet 2010, 13h 32min 56s Objet : Re : Minor problems... Dimitar Dimitrov wrote: I wrote: Dimitar Dimitrov wrote: I always have 'cursorline' set. Try this: :h'exrc Setting the cursor on this line...: setting the 'secure' option (see initialization). Using a local ...makes it move right. Same thing if you turn off cursorline but position your cursor on the left parens... I think this is related to the new conceal feature and the vertical bars appearing (|) The concealing is not done when there is something highlighted in the line. I'm not sure if this is required. Perhaps it would be highlighting the wrong position otherwise. But for 'cursorline' this doesn't matter. Vince? Looking at this again, I think it's bad that the cursor is at the wrong position. E.g. a search lands in the wrong place. Even when 'modifiable' is off a user would still want to copy text, and we don't want to copy something else than what's displayed. The highlighting does not appear to be a problem. Perhaps I didn't try the right kind? I pushed a new version that does it this way, please check for how it works now. I tried with Vim 7.3b and the problem is gone when cursorline is on but I still find it strange that vertical bars and stars would appear when highlighting the text. It may be relevant for other filetypes but I don't think it is for help files. Here is what I get when copying: 1.txt| About the manuals |usr_02.txt| The first steps in Vim |usr_03.txt| Moving around |usr_04.txt| Making small changes |usr_05.txt| Set your settings |usr -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : Minor problems...
Dimitar Dimitrov wrote: I wrote: Dimitar Dimitrov wrote: I always have 'cursorline' set. Try this: :h'exrc Setting the cursor on this line...: setting the 'secure' option (see initialization). Using a local ...makes it move right. Same thing if you turn off cursorline but position your cursor on the left parens... I think this is related to the new conceal feature and the vertical bars appearing (|) The concealing is not done when there is something highlighted in the line. I'm not sure if this is required. Perhaps it would be highlighting the wrong position otherwise. But for 'cursorline' this doesn't matter. Vince? Looking at this again, I think it's bad that the cursor is at the wrong position. E.g. a search lands in the wrong place. Even when 'modifiable' is off a user would still want to copy text, and we don't want to copy something else than what's displayed. I agree, copying right now from the help files brings up the concealed text (| or *) which is unwanted. The highlighting does not appear to be a problem. Perhaps I didn't try the right kind? I pushed a new version that does it this way, please check for how it works now. I am unable to test at work unless there is a new version of the gVim executable. At home, I am using a debian stable distribution but somehow compiling Vim from the mercurial repo broke my session and I had to create a new user account to deal with the problem. I am still investigating it... -- ARTHUR:A scratch? Your arm's off! BLACK KNIGHT: No, it isn't. ARTHUR:Well, what's that then? BLACK KNIGHT: I've had worse. The Quest for the Holy Grail (Monty Python) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Minor problems...
Hi, I always have 'cursorline' set. Try this: :h'exrc Setting the cursor on this line...: setting the 'secure' option (see initialization). Using a local ...makes it move right. Same thing if you turn off cursorline but position your cursor on the left parens... I think this is related to the new conceal feature and the vertical bars appearing (|) -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
find completion fails
:find tab crashed my gVim on Windows XP VIM - Vi IMproved 7.3a BETA (2010 Jul 18, compiled Jul 18 2010 21:51:55) MS-Windows 32-bit GUI version with OLE support Compiled by b...@kibaale Big version with GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole -osfiletype +path_extra +perl/dyn +persistent_undo -postscript +printer -profile +python/dyn +python3/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save +xpm_w32 system vimrc file: $VIM\vimrc user vimrc file: $HOME\_vimrc 2nd user vimrc file: $VIM\_vimrc user exrc file: $HOME\_exrc 2nd user exrc file: $VIM\_exrc system gvimrc file: $VIM\gvimrc user gvimrc file: $HOME\_gvimrc 2nd user gvimrc file: $VIM\_gvimrc system menu file: $VIMRUNTIME\menu.vim Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -D NDEBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\tcl83.dll\ -DDYNAMIC_TCL_VER=\8.3\ -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\ -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\python31.dll\ -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\ perl512.dll\ -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\msvcrt-ruby191.dll\ -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi3 2.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib /nodefaultlib:python27.lib /nodefaultlib:python3 1.lib e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib /PDB:gvim.pdb -debug -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
gVim stops responding...
gVim on Windows XP
1. 77ia,esc
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}cr
3. :h\{cr
Then gVim stops responding
VIM - Vi IMproved 7.3a BETA (2010 Jul 18, compiled Jul 18 2010 21:51:55)
MS-Windows 32-bit GUI version with OLE support
Compiled by b...@kibaale
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+conceal +cryptv +cscope
+cursorbind +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path
+float +folding -footer +gettext/dyn
-hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
+mouse +mouseshape
+multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole -osfiletype
+path_extra +perl/dyn +persistent_undo -postscript +printer -profile
+python/dyn
+python3/dyn +quickfix +reltime
+rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +startuptime
+statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white
+tcl/dyn -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-xfontset -xim -xterm_save +xpm_w32
system vimrc file: $VIM\vimrc
user vimrc file: $HOME\_vimrc
2nd user vimrc file: $VIM\_vimrc
user exrc file: $HOME\_exrc
2nd user exrc file: $VIM\_exrc
system gvimrc file: $VIM\gvimrc
user gvimrc file: $HOME\_gvimrc
2nd user gvimrc file: $VIM\_gvimrc
system menu file: $VIMRUNTIME\menu.vim
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400
-D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -D
NDEBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32
-DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL
-DDYNAMIC_TCL_DLL=\tcl83.dll\ -DDYNAMIC_TCL_VER=\8.3\
-DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\
-DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\python31.dll\
-DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\
perl512.dll\ -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191
-DDYNAMIC_RUBY_DLL=\msvcrt-ruby191.dll\ -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib
kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib
uuid.lib /machine:i386 /nodefaultlib gdi3
2.lib version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib
/machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib
/nodefaultlib:python27.lib /nodefaultlib:python3
1.lib e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib
/PDB:gvim.pdb
-debug
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Memory leak
1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE 2. ZQ ==14191== LEAK SUMMARY: ==14191==definitely lost: 36 bytes in 1 blocks. ==14191==indirectly lost: 120 bytes in 10 blocks. ==14191== possibly lost: 0 bytes in 0 blocks. ==14191==still reachable: 40,689 bytes in 261 blocks. ==14191== suppressed: 0 bytes in 0 blocks. VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 13 2010 20:27:14) Included patches: 1-446 Compiled by mi...@debian Normal version without GUI. Features included (+) or not (-): -arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv -cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +float +folding -footer +fork() -gettext -hangul_input -iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape -mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse +mouse_xterm -multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl +postscript +printer -profile -python +quickfix +reltime -rightleft -ruby +scrollbind -signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/local/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -D_FORTIFY_SOURCE=1 Linking: gcc -L/usr/local/lib -o vim -lm -lncurses -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Memory leak
valgrind --leak-check=full --show-reachable=yes gvim
1. cc, then a,a,a,a,a,a,a,a,a,a,a,
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}
3. :h\{
4. Close gvim
==3987== LEAK SUMMARY:
==3987==definitely lost: 12,986 bytes in 47 blocks.
==3987==indirectly lost: 28,332 bytes in 1,403 blocks.
==3987== possibly lost: 349,216 bytes in 498 blocks.
==3987==still reachable: 3,245,978 bytes in 47,532 blocks.
==3987== suppressed: 0 bytes in 0 blocks.
VIM - Vi IMproved 7.1 (2007 May 12, compiled Oct 17 2008 18:04:59)
Included patches: 1-314
Compiled by james...@debian.org
Huge version with GTK2 GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl
+cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape
+dialog_con_gui +diff +digraphs +dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path
+folding -footer +fork() +gettext
-hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap
+menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm
-mouse_jsbterm +mouse_netterm +mouse_xterm
+multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl
+postscript +printer +profile +python
+quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff
+statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse
+textobjects +title +toolbar +user_commands
+vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu +windows +writebackup +X11
-xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
system vimrc file: $VIM/vimrc
user vimrc file: $HOME/.vimrc
user exrc file: $HOME/.exrc
system gvimrc file: $VIM/gvimrc
user gvimrc file: $HOME/.gvimrc
system menu file: $VIMRUNTIME/menu.vim
fall-back for $VIM: /usr/share/vim
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/
usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1
-g
-O2 -O2 -g -Wall-D_REENTRANT -D_
GNU_SOURCE -DDEBIAN -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/lib/perl/5.10/CORE -I/u
sr/include/python2.5 -pthread -I/usr/include/tcl8.4 -D_REENTRANT=1
-D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1 -I/us
r/lib/ruby/1.8/i486-linux
Linking: gcc -L. -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,--as-needed
-L/usr/local/lib -o vim -lgtk-x11-2.0 -l
gdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo
-lgobject-2.0 -lgmodule-2.0 -lglib-2.0
-lXt -lncurses -lselinux -lacl -lgpm -Wl,-E -L/usr/local/lib
-L/usr/lib/perl/5.10/CORE -lperl -L/usr/lib/python2.5
/config -lpython2.5 -lutil -Xlinker -export-dynamic -Wl,-O1
-Wl,-Bsymbolic-functions -L/usr/lib -ltcl8.4 -lieee -lrub
y1.8 -lm
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Memory leak
1. f1 2. 3yy`] 3. 5yy`] ==4008== LEAK SUMMARY: ==4008==definitely lost: 37,350 bytes in 116 blocks. ==4008==indirectly lost: 28,332 bytes in 1,403 blocks. ==4008== possibly lost: 319,554 bytes in 469 blocks. ==4008==still reachable: 2,425,077 bytes in 30,351 blocks. ==4008== suppressed: 0 bytes in 0 blocks. VIM - Vi IMproved 7.1 (2007 May 12, compiled Oct 17 2008 18:04:59) Included patches: 1-314 Compiled by james...@debian.org Huge version with GTK2 GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc system gvimrc file: $VIM/gvimrc user gvimrc file: $HOME/.gvimrc system menu file: $VIMRUNTIME/menu.vim fall-back for $VIM: /usr/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/ usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1 -g -O2 -O2 -g -Wall-D_REENTRANT -D_ GNU_SOURCE -DDEBIAN -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl/5.10/CORE -I/u sr/include/python2.5 -pthread -I/usr/include/tcl8.4 -D_REENTRANT=1 -D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1 -I/us r/lib/ruby/1.8/i486-linux Linking: gcc -L. -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,--as-needed -L/usr/local/lib -o vim -lgtk-x11-2.0 -l gdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXt -lncurses -lselinux -lacl -lgpm -Wl,-E -L/usr/local/lib -L/usr/lib/perl/5.10/CORE -lperl -L/usr/lib/python2.5 /config -lpython2.5 -lutil -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -L/usr/lib -ltcl8.4 -lieee -lrub y1.8 -lm -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re : Update on Vim 7.3 status
That said, I think persistent undo is more or less useless and, well, just a big pile of potential problems. Persistent undo is in the version control system, not in the editor. I agree with that. This would probably be best left to versionning systems. Shouldn't Vim be used for purely text editing tasks only? -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
:find problem?
I would like to report some unexpected behaviour: 1. :set path+=~/dev/** 2. :find test.c works 1. :set path+=~/dev 2. :find **/test.c doesn't work And yet, :h wildcard suggests that it should... Note: File in ~/dev/project/example/test.c --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Request: suppression of plugins
Hi, I just wanted to support all the complainers. Even if the standard plugins do not slow Vim down, some of them are useless. tohtml for instance produces code which is not compliant with any modern standards. It is a shame to have it bundled. Besides, even if I never use it, I would like other user defined command to have priority over the TOHtml command. Ex: I use Tabularize and would like to use it as T instead of Ta I think all these shouldn't be standard: let loaded_rrhelper = 1 let g:loaded_zipPlugin = 1 let g:loaded_vimballPlugin = 1 let g:loaded_tarPlugin = 1 let g:loaded_getscriptPlugin = 1 let loaded_gzip = 1 let loaded_spellfile_plugin = 1 Regards Dimitar Dimitrov --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
]) bug?
I still think there is a little problem here. Fist, setting cpo+=% is not a solution because it breaks /* */ and # jumping... What I am saying is: (( )use % ) - here we will jump to the very first ( so using ]) should work as well... (for jumping to the last one) Also, (use % () ) - here we shouldn't jump to the parens inside the . I understand it this way in the help. ( use [( ( )) - this should also work --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
]) bug?
Hi, I think this is a bug. I hope it is just my version which is not recent enough but I didn't find anything on the FAQ. While inside a string : ( cursor ) [( and ]) won't work. Without the presence of a .vimrc it doesn't happen. Just after: touch .vimrc, the bug appears! Dimitar Dimitrov My version: VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Feb 25 2009 17:43:03) Included patches: 1-108 Compiled by 'http://www.opensuse.org/' Huge version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl +postscript +printer +profile -python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent +sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: /etc/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /etc f-b for $VIMRUNTIME: /usr/share/vim/current Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wall -pipe -fno-strict-aliasing -fstack-protector-all Linking: gcc -L/usr/local/lib -o vim -lm -lncurses -lacl --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
