\(an\_s\+\)\@=file

Hello Vim List, \(an\_s\+\)\@=file is the first example in help for \@= Since \_s\+ should find one or more white space characters (including end-of-line characters), why doesn't this match when there is more than one end-of-line in the white space? For example, this doesn't match: an

Re: \(an\_s\+\)\@=file

On 6/13/06, Bill McCarthy [EMAIL PROTECTED] wrote: Hello Vim List, \(an\_s\+\)\@=file is the first example in help for \@= Since \_s\+ should find one or more white space characters (including end-of-line characters), why doesn't this match when there is more than one end-of-line in the white

Textwidth setting Directory Listing

I noticed a problem that occurs whenever I open a file via the Directory listing. Whenever a file is opened via the directory listing it screws up the textwidth settings for all the buffers. I am not sure if it is the directory listing plugin or vim 7 itself that is causing the problem. Even

Picking nits about 'ballooneval' + 'mousehide'

I'm running gvim 7 under windows xp pro. I like to set 'mousehide' so that the pointer gets out of my way while I'm actually editing text. Recently I started fooling around with the 'ballooneval' feature, and I'd like to be able to make the balloon dissapear when I begin editing, just like the

Re: gf , isfname and @

Hi, Emmanuel Sixou wrote: I am using vim7. The char @ seems not to be considered as a filename character even though it appears in the isfname set variable, for the commands gf, gF. What's wrong? inside isfname and some other options @ is a placeholder for all characters where isalpha()

Re: Textwidth setting Directory Listing

jbw wrote: I noticed a problem that occurs whenever I open a file via the Directory listing. Whenever a file is opened via the directory listing it screws up the textwidth settings for all the buffers. I am not sure if it is the directory listing plugin or vim 7 itself that is causing the

Re: Calling through a function reference with a variable argument list

On 6/12/06, Hari Krishna Dara [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006 at 4:07pm, Charles E Campbell Jr wrote: Bob Hiestand wrote: On 6/2/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote: Bob Hiestand wrote: My question is whether there is a simpler way to pass an unknown

Re: R: Vim doesn't open files with chinese file names

On 6/11/06, Wu Yongwei [EMAIL PROTECTED] wrote: On 6/11/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Cesar Romani wrote: -Messaggio originale- Da: A.J.Mechelynck [mailto:[EMAIL PROTECTED] Inviato: venerdì 9 giugno 2006 23.34 A: Cesar Romani Cc: Vim Oggetto: Re: Vim doesn't

Re: Vim: Reading from stdin

Hi Mikolaj, I get: Vim: Reading from stdin What happens when you do this: date | /usr/bin/vim -u NONE - Assuming that your vim is installed at /usr/bin/vim. What version of Vim are you using? --Eljay

Re: negative match pattern, again

It follows the general form of a negative line search for embedded search: /^\%(.*[limit0.*]search[.*limit1]\)[EMAIL PROTECTED] For example, to match a line that contains foo but does not contain bar between big and tummy: /\%(.*big.*bar.*tummy\)[EMAIL PROTECTED] Edward Wong wrote:

Re: Vim: Reading from stdin

On Tue, 13 Jun 2006, John Love-Jensen wrote: Hi Mikolaj, I get: Vim: Reading from stdin What happens when you do this: date | /usr/bin/vim -u NONE - Vim does its job, and after quitting vim I get: [EMAIL PROTECTED] ~ $ date | /usr/bin/vim -u NONE - Vim: Reading from

RE: gf , isfname and @

Thanks Emmanuel Sixou Mobileye Vision Technologies Project Manager - ASIC Department Tel: +972 (2) 541 7311 Fax: +972 (2) 541 7300 Cell: +972 (54) 5665 206 E-mail: [EMAIL PROTECTED] -Original Message- From: Jürgen Krämer [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 17:31 To:

***SPAM*** Error detected while processing function SNR1_BMShow

I use vim 7.0 on Windows XP compiled with MS Visual C. If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: -- Error detected while processing function SNR1_BMShow: line 12: E329: No menu Buffer Error detected while processing

Re: Vim: Reading from stdin

Hi Jorge, Vim does its job, and after quitting vim I get: Actually, you are getting the Vim: Reading from stdin... first, and then Vim does it's job. When Vim quits, it restores the screen (available in some termcaps), which includes the prior Vim message that it was reading from stdin. I

Re: Vim: Reading from stdin

On Tue, 13 Jun 2006, John Love-Jensen wrote: Hi Jorge, Vim does its job, and after quitting vim I get: Actually, you are getting the Vim: Reading from stdin... first, and then Vim does it's job. When Vim quits, it restores the screen (available in some termcaps), which includes the prior

Re: Vim: Reading from stdin

Hi Jorge, That would be worse than the message! You should modify the Vim source code so it does not emit the message, and compile your own version. Note: the message is there so it does not appear that your machine is hung if vim is being sent a large amount of input, or a input from a slow

Re: Error detected while processing function SNR1_BMShow

On Tue, Jun 13, 2006 at 05:37:13PM +0200, Cesar Romani wrote: I use vim 7.0 on Windows XP compiled with MS Visual C. If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: -- Error detected while processing function

Re: non-latin characters aren't displayed correctly in Windows menu

On 6/13/06, A.J.Mechelynck wrote: Mojca Miklavec wrote: On 6/12/06, A.J.Mechelynck wrote: You must make sure that you have: - an 'encoding' which includes the non-Latin characters you want to use - (in console Vim) a terminal code page which includes them What is that? And console vim if

Re: Error detected while processing function SNR1_BMShow

Cesar Romani wrote: I use vim 7.0 on Windows XP compiled with MS Visual C. If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: -- Error detected while processing function SNR1_BMShow: line 12: E329: No menu Buffer Error

Re: ***SPAM*** Error detected while processing function SNR1_BMShow

Mathias Michaelis wrote: Hello Andalou I use vim 7.0 on Windows XP compiled with MS Visual C. If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: -- Error detected while processing function SNR1_BMShow: line 12: E329: No

Re: non-latin characters aren't displayed correctly in Windows menu

Mojca Miklavec wrote: On 6/13/06, A.J.Mechelynck wrote: Mojca Miklavec wrote: On 6/12/06, A.J.Mechelynck wrote: You must make sure that you have: - an 'encoding' which includes the non-Latin characters you want to use - (in console Vim) a terminal code page which includes them What is

Re: FTDetect

On 2006-06-13, Max Dyckhoff [EMAIL PROTECTED] wrote: I am having some issues with filetype detection stuff. Here is what I am doing, so far as I can see I am doing exactly what it says in the help. 1. I am on Windows, my runtimepath is ~/vimfiles,C:\Program Files\Vim/vimfiles,c:\Progam

Re: Error detected while processing function SNR1_BMShow

Tony, Andalou If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: [...] E329: No menu Buffer [...] I can confirm that behaviour of gvim, but I think it is a feature, not a bug. [...] However, under :help -u it is said that -u NONE disables vimrc, gvimrc, and all

Re: omni completion, calling different types

Dnia poniedziałek, 12 czerwca 2006 19:39, Silent1 napisał: I'm using the omni completion so far on my php scripts and i'm wondering if there are ways i can call different sets of data with different key strokes. You can use 'completefunc' to call different completion script. ctrl-x+ctrl+o

Re: Vim: Reading from stdin

Dnia wtorek, 13 czerwca 2006 17:22, John Love-Jensen napisał: date | /usr/bin/vim -u NONE - Still the same. Vim7.017 m.

Re: FTDetect

Max Dyckhoff wrote: Thank you for your answers. See :help ftdetect. The augroup statements are also not necessary. The variable did_load_filetypes is set to 1 by $VIMRUNTIME/filetype.vim (at line 10 in the version for Vim 7.0, lat change May 02). Your script is sourced from line 2166 of the

Re: I sometimes have to double strike when using gvim7 over Hummingbird Exceed

Hi DrC, et al, On Fri, Jun 02, 2006 at 12:17 PM PDT, Charles E. Campbell, Jr. wrote: ... Text Deleted ... CECJ I suggest narrowing down the problem. CECJ CECJ vim -u NONE -U NONE CECJ CECJ for starters. Then try to source in a minimal file (I believe you CECJ mentioned something about

Re: non-latin characters aren't displayed correctly in Windows menu

Mojca Miklavec wrote: On 6/13/06, A.J.Mechelynck wrote: Mojca Miklavec wrote: Courier_New has a larger variety of glyphs than most other fixed-width encodings. If Lucida_Console hasn't got the glyphs you need, I recommend Courier_New. No, Lucide_Console is OK (and Courier_New as well), but

Re: Error detected while processing function SNR1_BMShow

Mathias Michaelis wrote: Tony, Andalou If I do: gvim -u NONE -U NONE -c set verbosefile=C:/vim.log I get: [...] E329: No menu Buffer [...] I can confirm that behaviour of gvim, but I think it is a feature, not a bug. [...] However, under :help -u it is said that -u

Vim7 auto-downloading spell dictionary

Does the vim7 automatic downloading of a new spellcheck dictionary work as advertised in :help spellfile.vim? The command in help is: autocmd SpellFileMissing * call Download_spell_file(expand('amatch')) but in spellfile.vim is: autocmd SpellFileMissing * call

Re: non-latin characters aren't displayed correctly in Windows menu

On 6/14/06, A.J.Mechelynck wrote: In $VIMRUNTIME/vimrc_example.vim for Vim 7.0, last change 2002 Sep 19, at line 56 filetype plugin indent on ... Thanks for all the hints. Using the extensive explanation and after playing with all possible combinations: the most crutial part was setting

Re: negative match pattern, again

Very great explanation! Many thanks to Gerald and Chip Campbell. Now I _really_ got it. :) On 6/13/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote: It follows the general form of a negative line search for embedded search: /^\%(.*[limit0.*]search[.*limit1]\)[EMAIL PROTECTED] For

Re: non-latin characters aren't displayed correctly in Windows menu

Mojca Miklavec wrote: On 6/14/06, A.J.Mechelynck wrote: In $VIMRUNTIME/vimrc_example.vim for Vim 7.0, last change 2002 Sep 19, at line 56 filetype plugin indent on ... Thanks for all the hints. Using the extensive explanation and after playing with all possible combinations: the most

A question on langmenu setting

I read vim doc, it says: Language to use for menu translation. Tells which file is loaded from the lang directory in 'runtimepath': lang/menu_ . langmenu . .vim (without the spaces). For example, to always use the

Re: Bug: Gvim window resizes during save with :w

Jochen Baier wrote: hi, i have weird behavior here (latest svn gvim, linux, Gnome or Wmii) if i save with :w the window change the size to larger size (5 pixel) for moment then it size back to the orginal size. The left scrollbar is visible during this. no problems with normal konsole vim. is

[Fwd: Re: I just updated my Vim site]

Hi Steve, I got the attached email privately. I believe it is meant for you. Best regards, Tony. ---BeginMessage--- A.J.Mechelynck wrote: And even if someday you do understand RPM (used by RedHat and SuSE), you'll still have to figure out dpkg (for Debian) and what-not... I have compiled gvim

incorrect behavior of gzip.vim plugin?

I was following Chip Campbell's advice in the vim list to download v100 of the netrw plugin when I discovered the following undesirable behavior of the gzip.vim plugin. I downloaded netrw.vba.gz, then opened it with view netrw.vba.gz and saw the following messages at the bottom of the

Re: incorrect behavior of gzip.vim plugin?

Gary Johnson wrote: I was following Chip Campbell's advice in the vim list to download v100 of the netrw plugin when I discovered the following undesirable behavior of the gzip.vim plugin. I downloaded netrw.vba.gz, then opened it with view netrw.vba.gz and saw the following messages

Re: incorrect behavior of gzip.vim plugin?

Charles E Campbell Jr wrote: [...] The problem here is :so % doesn't source the buffer, it sources the underlying file. Thus the file must needs be gunzip'ed first. Vimball could be set up not to gunzip the file, but then sourcing it would fail. Regards, Chip Campbell Looking at the

Documentation bug about matchparen

*pi_paren.txt* For Vim version 7.0. Last change: 2006 Apr 24 line 46 (i.e. 5th from bottom) there is 'synmaxcolumn' there should be 'synmaxcol' Best regards, Tony.