Greetings:
I use grep and :cw to open up a quickfix window that contains all the
matches, I "ENTER" and the cursor jumps to the match in the file.
Could I have the cursor stay in the quick fix window when I "ENTER"?
Thank you!
Jim
--
You received this message from the "vim_use" maillist.
Do not
Hi,
Jim Green schrieb:
>
>
> I use grep and :cw to open up a quickfix window that contains all the
> matches, I "ENTER" and the cursor jumps to the match in the file.
> Could I have the cursor stay in the quick fix window when I "ENTER"?
put the following line in your ~/.vimrc
au FileType Q
Thank you Jurgen, somehow it doesn't work for me, hmmm, how do we
debug in this case?
JIm
On Oct 15, 2:09 am, Jürgen Krämer wrote:
> Hi,
>
> Jim Green schrieb:
>
>
>
> > I use grep and :cw to open up a quickfix window that contains all the
> > matches, I "ENTER" and the cursor jumps to the match
Also I searched the list and tried a recipe by Tony Mechelynck
if has('autocmd') && has('quickfix')
au BufWinEnter if &l:buftype == 'quickfix'
\ | exe 'map p'
\ | endif
endif
Unfortunately it does not work either, appreciate any help here.
On Oct 15, 8:4
Ответ на сообщение «Re: grep quickfix window question»,
присланное в 16:47:25 15 октября 2010, Пятница.
Отправитель: Jim Green:
First (``au Filetype'') solution has one error: quickfix filetype is `qf', not
`QF'. If you use
autocmd Filetype qf nnoremap p
everything
On 2010-10-15, ZyX wrote:
> Jim Green:
> > On Oct 15, 8:45 am, Jim Green wrote:
> > > On Oct 15, 2:09 am, Jürgen Krämer wrote:
> > > > Hi,
> > > >
> > > > Jim Green schrieb:
> > > > > I use grep and :cw to open up a quickfix window that contains all the
> > > > > matches, I "ENTER" and the cu
Ответ на сообщение «Re: grep quickfix window question»,
присланное в 17:31:36 15 октября 2010, Пятница.
Отправитель: Gary Johnson:
> This is what I did.
>
> $ vim -N -u NONE
>
> :set cursorline
> :au FileType QF nmap
> :grep PATTERN *
> :cw
<.
ZyX's both fixes work. Thank you!
Jim
--
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
Hi ZyX!
On Fr, 15 Okt 2010, ZyX wrote:
> > Also, please don't top post to this list.
> You like to scroll down those very long quotes? I copy quotes at the top when
> I
> think it is useful, but you will not convince me to move the whole message
> there.
And what is preventing you from deleti
On Oct 15, 9:31 am, Gary Johnson wrote:
> This is what I did.
>
> $ vim -N -u NONE
> :set cursorline
> :au FileType QF nmap
> :grep PATTERN *
> :cw
>
> where PATTERN is a string I knew would be found in some files in the
> current directory, and 'cursorline' is set to more easily see the
> cu
Hi
ZyX wrote:
> Ответ на сообщение «Re: grep quickfix window question»,
> присланное в 17:31:36 15 октября 2010, Пятница.
> Отправитель: Gary Johnson:
>
>> Also, please don't top post to this list.
> You like to scroll down those very long quotes? I copy quotes at the
Ответ на сообщение «Re: grep quickfix window question»,
присланное в 18:21:38 15 октября 2010, Пятница.
Отправитель: Christian Brabandt:
> And what is preventing you from deleting the old text in the mail, if it
> isn't needed?
It requires more work then moving needed text up.
Текс
On Fri, Oct 15, 2010 at 15:56, ZyX wrote:
>> Also, please don't top post to this list.
> You like to scroll down those very long quotes? I copy quotes at the top when
> I
> think it is useful, but you will not convince me to move the whole message
> there.
I think the suggestion was to just remo
On 2010-10-15, ZyX wrote:
> ?? ?? «Re: grep quickfix window question»,
> ?? 17:31:36 15 ?? 2010, ??.
> ??: Gary Johnson:
>
> > This is what I did.
> >
> > $ vi
> Interesting. I was testing it using vim-7.3 compiled by me on a
> Cygwin system. I tried the experiment again but using gvim-7.3.2
> from the Cream site but without Cream. The results were the same:
> works fine for me despite the flaws in the autocommand.
I was using vim7.2 on linux QF doesn
Reply to message
with subject «Re: grep quickfix window question»,
sent 18:24:10 15 October 2010, Friday
by Jim Green:
> This works well, but looks like set cursorline is global, could I have
> a
> cursorline just when I do :grep and :cw ?
It is not global, just use `setlocal' i
On 2010-10-15, Jim Green wrote:
> On Oct 15, 9:31 am, Gary Johnson wrote:
> > This is what I did.
> >
> > $ vim -N -u NONE
> > :set cursorline
> > :au FileType QF nmap
> > :grep PATTERN *
> > :cw
> >
> > where PATTERN is a string I knew would be found in some files in the
> > current directory,
Reply to message «Re: grep quickfix window question»,
sent 19:04:54 15 October 2010, Friday
by Gary Johnson:
> It looked to me like it was global, too, but ":help cursorline" says
> that it's local to the window. What's happening is that new windows
> inherit at
On 2010-10-15, ZyX wrote:
> Reply to message «Re: grep quickfix window question»,
> sent 19:04:54 15 October 2010, Friday
> by Gary Johnson:
>
> > It looked to me like it was global, too, but ":help cursorline" says
> > that it's local to the window
Reply to message «Re: grep quickfix window question»,
sent 19:39:41 15 October 2010, Friday
by Gary Johnson:
> Note that the upper two windows show a cursor line while the lower
> two windows do not. If ":set cursorline" was setting a global
> value, I would expect a curso
Hi,
Gary Johnson wrote:
>
> Despite those issues, Jürgen's original version of that autocommand
> worked fine for me, so I think Jim's problem with it lies elsewhere.
>
> This is what I did.
>
> $ vim -N -u NONE
> :set cursorline
> :au FileType QF nmap
> :grep PATTERN *
>
Reply to message «Re: grep quickfix window question»,
sent 18:04:40 15 October 2010, Friday
by Jürgen Krämer:
> I tested this on Windows, and I seem to rembember (now) that the case of
> the file type is not relevant here.
On windows the case of the filename is ignored, on *nix it does n
On Oct 15, 10:55 am, ZyX wrote:
> Reply to message
>
> with subject «Re: grep quickfix window question»,
> sent 18:24:10 15 October 2010, Friday
> by Jim Green:
>
> > This works well, but looks like set cursorline is global, could I have
> > a
> > cur
On Oct 15, 10:55 am, ZyX wrote:
> Reply to message
>
> with subject «Re: grep quickfix window question»,
> sent 18:24:10 15 October 2010, Friday
> by Jim Green:
>
> > This works well, but looks like set cursorline is global, could I have
> > a
> > cur
Reply to message «Re: grep quickfix window question»,
sent 21:14:06 15 October 2010, Friday
by Jim Green:
> the cursorline only shows in the lower quickfix window. I would like a
> cursorline remains on the match in the upper file window when the w>p
> jumps back to quickfix window
On 2010-10-15, Jim Green wrote:
> On Oct 15, 10:55 am, ZyX wrote:
> > Reply to message
> >
> > with subject «Re: grep quickfix window question»,
> > sent 18:24:10 15 October 2010, Friday
> > by Jim Green:
> >
> > > This works well, but looks lik
Works! Thanks a lot!
Jim
--
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
On Oct 15, 2:03 pm, Gary Johnson wrote:
> On 2010-10-15, Jim Green wrote:
>
>
>
> > On Oct 15, 10:55 am, ZyX wrote:
> > > Reply to message
> > >
> > > with subject Re: grep quickfix window question ,
> > > sent 18:24:10 15 October 2010
On Fri, Oct 15, 2010 at 06:34:55PM +0400, ZyX wrote:
>> And what is preventing you from deleting the old text in the mail, if it
>> isn't needed?
> It requires more work then moving needed text up.
Then please use an editor which makes handling text simple, like
Vim. d} doesn't take very long.
An
Reply to message «Re: grep quickfix window question»,
sent 23:31:39 16 October 2010, Saturday
by Simon Ruderich:
> Then please use an editor which makes handling text simple, like
> Vim. d} doesn't take very long.
But copy-pasting from/to vim does. And `more work' means that
ZyX wrote:
> Original message:
> ...
Please stop quoting the full message.
This mailing list has debated the issue too often, and we have
no interest in convincing anyone of whether we are right or
wrong. It's just a request when using this mailing list (if you
like, call it a condition).
See th
On 2010-10-16, ZyX wrote:
> Reply to message «Re: grep quickfix window question»,
> sent 23:31:39 16 October 2010, Saturday
> by Simon Ruderich:
>
> > Then please use an editor which makes handling text simple, like
> > Vim. d} doesn't take very long.
> But co
Hi,
ZyX wrote:
> Reply to message «Re: grep quickfix window question»,
> sent 18:04:40 15 October 2010, Friday
> by Jürgen Krämer:
>
>> I tested this on Windows, and I seem to rembember (now) that the case of
>> the file type is not relevant here.
> On windows
> I don't think so. When case in filenames is ignored, it must not be
> relevant in filetypes either. Otherwise you could not create filetype
> plugins or syntax files for two filetypes that differ in case only.
You can't (reliably do so) when using a file system that has case
insensitive filename
Hi,
Tom Link wrote:
>> I don't think so. When case in filenames is ignored, it must not be
>> relevant in filetypes either. Otherwise you could not create filetype
>> plugins or syntax files for two filetypes that differ in case only.
>
> You can't (reliably do so) when using a file system that
> >> I don't think so. When case in filenames is ignored, it must not be
> >> relevant in filetypes either. Otherwise you could not create filetype
> >> plugins or syntax files for two filetypes that differ in case only.
>
> > You can't (reliably do so) when using a file system that has case
> > in
Hi,
Tom Link wrote:
I don't think so. When case in filenames is ignored, it must not be
relevant in filetypes either. Otherwise you could not create filetype
plugins or syntax files for two filetypes that differ in case only.
>>
>>> You can't (reliably do so) when using a file syst
Reply to message «Re: grep quickfix window question»,
sent 15:34:37 18 October 2010, Monday
by Jürgen Krämer:
> My conclusion: leave it as it is, i.e., handle filetype names case
> sensitively where the typical file system support case sensitivity and
> make them case insensitive other
ZyX schrieb:
> Reply to message «Re: grep quickfix window question»,
> sent 15:34:37 18 October 2010, Monday
> by Jürgen Krämer:
>
>> My conclusion: leave it as it is, i.e., handle filetype names case
>> sensitively where the typical file system support case sensitivi
Reply to message «Re: grep quickfix window question»,
sent 16:17:37 18 October 2010, Monday
by Jürgen Krämer:
> > Case insensitiviness of filetypes is not related to case insensitiviness of
> > filenames:
> of course it is: setting a filetype leads to sourceing files with the
>
Hi,
ZyX wrote:
> Reply to message «Re: grep quickfix window question»,
> sent 16:17:37 18 October 2010, Monday
> by Jürgen Krämer:
>>> Case insensitiviness of filetypes is not related to case insensitiviness of
>>> filenames:
>> of course it is: setting a filet
Reply to message «Re: grep quickfix window question»,
sent 17:31:43 18 October 2010, Monday
by Jürgen Krämer:
> So when Vim has its run-time directories on a file system that
> distinguishes between lower and upper case letters, the filetype name
> must match exactly in case.
I know
Hi,
ZyX wrote:
> Reply to message «Re: grep quickfix window question»,
> sent 17:31:43 18 October 2010, Monday
> by Jürgen Krämer:
>
>> So when Vim has its run-time directories on a file system that
>> distinguishes between lower and upper case letters, the filetype na
On Oct 15, 12:52 am, Jim Green wrote:
> Greetings:
>
> I use grep and :cw to open up a quickfix window that contains all the
> matches, I "ENTER" and the cursor jumps to the match in the file.
> Could I have the cursor stay in the quick fix window when I "ENTER"?
>
Hi,
In the library VxLib (scrip
44 matches
Mail list logo
