?
-Original Message-
From: Gary Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, August 28, 2006 1:14 PM
To: vim@vim.org
Subject: Re: Search all text files in a directory for text
FWIW, I just tried this on Windows using vim-7.0 without patches,
downloaded from vim.sf.net, and netrw 103g
Chuck Mason wrote:
Sorry to bring this up again. Was there every any solution to this? Do
I just need the latest netrw? I was trying to get :Explore **/pattern
working
But as I do see the Match n of N in the lower right, the cursor never
moves in the browse buffer (with S-Down/S-Up) and
On 2006-11-07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Chuck Mason wrote:
Sorry to bring this up again. Was there every any solution to this? Do
I just need the latest netrw? I was trying to get :Explore **/pattern
working
But as I do see the Match n of N in the lower right,
Gary Johnson wrote:
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
Thanks. That removes the error and gives me a list of files, but
included in that list are non-*.c names such as
INSTALL
Makefile
README.txt
:Explore **/*.c
Charles E Campbell Jr wrote:
Gary Johnson wrote:
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
Thanks. That removes the error and gives me a list of files, but
included in that list are non-*.c names such as
INSTALL
Makefile
README.txt
On 2006-08-24, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
I found another problem, though. Following my previous example and
proceeding from
$ vim -N -u NONE
I execute the following commands and the cursor moves to the file
indicated.
Gary Johnson wrote:
[...]
That's really weird. I see the same broken :Pexplore behavior with
both my SunOS and Linux versions. Maybe the problem has been fixed
with a patch.
--
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 8 2006 16:40:23)
Compiled by [EMAIL PROTECTED]
Normal
Bram Moolenaar wrote:
Charles E Campbell wrote:
Sigh -- I'm not sure what to do about this one. Turns out that:
com! ... -complete=dir Explore ...
causes the E77 with Too many file names. Simply removing the
-complete=dir
from the command fixes things.
You have -nargs=?
Charles E Campbell wrote:
Sigh -- I'm not sure what to do about this one. Turns out that:
com! ... -complete=dir Explore ...
causes the E77 with Too many file names. Simply removing the
-complete=dir
from the command fixes things.
You have -nargs=? which means only 0 or 1
On 8/18/06, Jerin Joy [EMAIL PROTECTED] wrote:
Hi,
I have a lot of source code distributed over a directory hierarchy
structure. I always need to find class declarations, instances where
variables are set etc. Usually I just go to command line and run
something like
find . -name *.vr -print |
Jerin Joy wrote:
Hi,
I have a lot of source code distributed over a directory hierarchy
structure. I always need to find class declarations, instances where
variables are set etc. Usually I just go to command line and run
something like
find . -name *.vr -print | xargs grep 'class foo'
Isn't
Jerin Joy wrote:
Hi,
I'll try the ctags. Both vera and verilog are supported. I'm running
vim 6.4 so no vimgrep. Can't change it since I work on a remote login.
thanks,
Jerin
You can still invoke grep from Vim 6.4 (since you have an external grep
program installed): see :help :grep. Tags
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Jerin Joy wrote:,
I have a lot of source code distributed over a directory hierarchy
structure. I always need to find class declarations, instances where
variables are set etc. Usually I just go to command line and run
Gary Johnson wrote:
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Read :help netrw-starstarpat :
:Explore **//class foo
for example. You'll be presented with an netrw browser display in each
subdirectory
with matching files and the cursor on the first file that
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Read :help netrw-starstarpat :
:Explore **//class foo
for example. You'll be presented with an netrw browser display in each
Gary Johnson wrote:
Thanks. That removes the error and gives me a list of files, but
included in that list are non-*.c names such as
INSTALL
Makefile
README.txt
:Explore **/*.c doesn't give a list of just *.c files. Instead, it
opens a browser listing of every directory
On 2006-08-18, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
Thanks. That removes the error and gives me a list of files, but
included in that list are non-*.c names such as
INSTALL
Makefile
README.txt
:Explore **/*.c doesn't give a list
17 matches
Mail list logo
