Re: problem: redirection of global print to register

2012-06-15 Thread Jürgen Krämer
Hi, Nick Shyrokovskiy wrote: Say initially I have a buffer: --buffer-- a1 a2 - if i sequentially issue: :redir @c :g/a./ :redir END :put c I'll get and i'll see 2 matched lines in vim output as :g is not silent --buffer-- a1 a2 a1 a2 -- but if

Re: problem: redirection of global print to register

2012-06-15 Thread Christian Brabandt
On Fri, June 15, 2012 09:57, Nick Shyrokovskiy wrote: On Friday, June 15, 2012 8:32:44 AM UTC+3, Christian Brabandt wrote: Do you mean, you see something different, than what is redirected? I can't reproduce this. I'll give an example. Say initially I have a buffer: --buffer-- a1 a2

Re: problem: redirection of global print to register

2012-06-15 Thread Nick Shyrokovskiy
Thank you for explanation and suggestion. I really need to :h :bar -- You received this message from the vim_use 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: problem: redirection of global print to register

2012-06-15 Thread Nick Shyrokovskiy
On Friday, June 15, 2012 11:23:58 AM UTC+3, Christian Brabandt wrote: To prevent this, you can use :exe if you want to put this in one single line, e.g. :redir @c|exe g/a./|redir END I've learned a better way to make it one line from help: :redir @c | g/a./^@redir END where ^@ is one

Re: Selecting paragraphs

2012-06-15 Thread Eric Weir
On Jun 14, 2012, at 7:13 AM, Tim Chase wrote: This points to the 'tw'/'wm' issue I mentioned in my follow-up email. If you want to clean them up, it's usually pretty easy with :g/^\/,'}-j (you can insert a leading range before the g if you only want to touch a subset of your file; and

Re: VIM 7.2/7.3 on Win32: QuickFix does jump to line with error in C/C++/ASM, but not in Pascal

2012-06-15 Thread Frantisek Rysanek
On 14 Jun 2012 at 17:05, Ben Fritz wrote: set efm=%f\(%l\):\ Error\ %n:\ %m You shouldn't need to escape the parentheses, this isn't a regex. Probably you also need to tell it the type. Try this: set efm=%f(%l):\ %trror\ %n:\ %m ...etc lots of useful stuff snipped... Thanks a lot for

Re: VIM 7.2/7.3 on Win32: QuickFix does jump to line with error in C/C++/ASM, but not in Pascal

2012-06-15 Thread Frantisek Rysanek
On 15 Jun 2012 at 7:53, Jürgen Krämer wrote: VIM now says this: TEST.PAS(1)^MTEST.PAS(1)^MTEST.PAS [access denied] (3/5) error 36: BEGIN expected. while compiling Borland's command-line compiler outputs the current file and the number of source lines already processed as status

Re: VIM 7.2/7.3 on Win32: QuickFix does jump to line with error in C/C++/ASM, but not in Pascal

2012-06-15 Thread Frantisek Rysanek
TEST.PAS(1)^MTEST.PAS(1)^MTEST.PAS [access denied] (3/5) error 36: BEGIN expected. [ Jürgen schrieb: ] For parsing the output for Vim you should first get rid of everything up to the last carriage return on a line or -- if the last carriage return is part of the line ending --

Re: vim: problem when searching and displaying certain lines with :global

2012-06-15 Thread ping
On 06/15/2012 12:34 AM, Ben Fritz wrote: so the right logic here looks is: :g/.../ find some matched line(S), no matter how many lines got matched, take only 1st line, trash all others use that as the start of the range use another offset (here +1) based on original text (not matched

Determining which plugin is catching a command?

2012-06-15 Thread steen
Hi folks, I have a deceptively simple and overly broad question. Is there any reasonably way within vim to determine what plugin is attempting to respond to a given command? The use case I have here is that I have installed Tim Pope's excellent surround plugin, which I haven't used for a while,

Re: problem: redirection of global print to register

2012-06-15 Thread Ben Fritz
On Friday, June 15, 2012 5:00:27 AM UTC-5, Nick Shyrokovskiy wrote: On Friday, June 15, 2012 11:23:58 AM UTC+3, Christian Brabandt wrote: To prevent this, you can use :exe if you want to put this in one single line, e.g. :redir @c|exe g/a./|redir END I've learned a better way to make

Re: Determining which plugin is catching a command?

2012-06-15 Thread Ben Fritz
On Friday, June 15, 2012 4:15:04 AM UTC-5, steen wrote: Hi folks, I have a deceptively simple and overly broad question. Is there any reasonably way within vim to determine what plugin is attempting to respond to a given command? The use case I have here is that I have installed Tim Pope's

Re: Determining which plugin is catching a command?

2012-06-15 Thread Taylor Hedberg
Sort of. You can see which script last mapped a given key sequence with `:verbose map`. For instance, if you want to find out where the `ys` mapping from surround.vim was last set, you could do :verbose map ys which for me, prints: n yss PlugYssurround Last set

pass full path into title bar

2012-06-15 Thread andy richer
Hi All, I opened a file tmp under directory /a/b/c/d in unix environment. gvim opened it with title bar read tmp ( /a/b/c/d) - GVIM3 I then opened above file thru a utility called SOS(a check in check out management software) and gvim opened it with title bar read tmp (~/c/d) - GVIM.

Re: pass full path into title bar

2012-06-15 Thread Tony Mechelynck
On 16/06/12 01:39, andy richer wrote: Hi All, I opened a file tmp under directory /a/b/c/d in unix environment. gvim opened it with title bar read tmp ( /a/b/c/d) - GVIM3 I then opened above file thru a utility called SOS(a check in check out management software) and gvim opened it with