Re: RFE: :noswapfile prefix

Am 2014-03-14 06:14, schrieb Tony Mechelynck: Did you forget an entry in runtime/syntax/vim.vim or is that taken care of automagically? If I recall correctly, this is generated automatically. So I usually don't bother to change anything there. Best, Christian -- -- You received this

Re: Support for termcap %e and %c

On 13 March 2014, celel...@gmail.com wrote: Hello, I reported a bug in the debian BTS, but found that it also apply to upstream vim. Here it is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741400 In summary, it looks like vim do not support termcaps %e nor %c (corresponding to

Re: Is there any way to get the vim executable path from within vim?

Hi, Viktor Kojouharov wrote: To easily use the remote-expr feature. You need to start a new instance of vim and point it to the current running vim server. And I need the full executable path in order to start the remote-expr. Vim is usually in the path on linux systems, but that's not the

Re: Is there any way to get the vim executable path from within vim?

On 14-Mar-2014 08:20 +0100, Jürgen Krämer wrote: Hi, Viktor Kojouharov wrote: To easily use the remote-expr feature. You need to start a new instance of vim and point it to the current running vim server. And I need the full executable path in order to start the remote-expr. Vim is

Re: Is there any way to get the vim executable path from within vim?

On 14/03/14 08:20, Jürgen Krämer wrote: Hi, Viktor Kojouharov wrote: To easily use the remote-expr feature. You need to start a new instance of vim and point it to the current running vim server. And I need the full executable path in order to start the remote-expr. Vim is usually in the path

[patch] escape %,# in bang commands before storeing them in the redo buffer

Bram, condsider this: #v+ ~$vim -u NONE -N ((seq 1 10)) [Enter the following normal mode commands:] !!printf \%s foobarcr j. :w !cat foobar /proc/26234/fd/11s 3 4 5 ... #v- Note, that the second line, does not contain the foobar line, but contains the filename. This happens, because when

Re: Is there any way to get the vim executable path from within vim?

I was hoping using the python sys.argv would return the vim path as the first item, but its filled with garbage? Is there any way to get it, either from a built-in viml function or from the python interface? The executable name is in v:progname. If it is in $PATH, you should be set. -- --

Netrw shows directory structure wrong: always shows directory inside itself

Netrw shows the entry with the current directory name inside itself. For example: There are two directories /some/dir and /some/dir/other-dir Command 'cd /some/dir vim .' shows this: ../

Re: Support for termcap %e and %c

2014-03-14 17:58 UTC+01:00, LCD 47 lcd...@gmail.com: On 14 March 2014, celel...@gmail.com wrote: Le vendredi 14 mars 2014 07:49:31 UTC+1, LCD 47 a écrit : [...] Do you still have any questions after reading the first two sections in term.txt: :help startup-terminal :help

Re: dev: gvim auto copy selected text(visual) to + register

Hi Christian, Could you please tell me how to use your vim patch? I am new to vim. Many thanks. Li On Friday, April 27, 2012 5:19:07 PM UTC-4, Sergey Vakulenko wrote: The problem is solved ! Big thanks to Christian Brabandt for patch. First impression - its works like its should. Anyway,

Re: Support for termcap %e and %c

Le vendredi 14 mars 2014 21:13:09 UTC+1, LCD 47 a écrit : On 14 March 2014, Celelibi celel...@gmail.com wrote: 2014-03-14 17:58 UTC+01:00, LCD 47 lcd...@gmail.com: On 14 March 2014, celel...@gmail.com wrote: Le vendredi 14 mars 2014 07:49:31 UTC+1, LCD 47 a écrit : [...]