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 doesn't give a list of just *.c files. Instead, it
opens a browser listing of every directory
with *.c files in it. The cursor will be on the first such .c file; you
may edit it if you wish.
If its not the one you want, <shift>-down will move the cursor to the
next .c file, repeat at will.
One may go back with <shift>up . Directory displays will change as
necessary.
OH! Got it.
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.
+-----------------+-----------------+
| Command | Resulting |
| | Cursor Location |
+=================+=================+
| :Explore **/*.c | arabic.c |
| | |
| :Nexplore | auto/pathdef.c |
| :Nexplore | buffer.c |
| :Nexplore | charset.c |
| :Nexplore | diff.c |
| | |
| :Pexplore | diff.c |
| :Pexplore | diff.c |
| :Pexplore | auto/pathdef.c |
| :Pexplore | arabic.c |
+-----------------+-----------------+
So there seems to be a "pointer" traversing an internal list of
files that is moved by the :Nexplore and :Pexplore commands. The
:Nexplore and :Pexplore commands both control this pointer
correctly, but only the :Nexplore command updates the cursor
location correctly, unless the directory is changed.
I'm seeing the cursor move to the next/previous matching file for both
:Nexplore and :Pexplore.
I do see one odd behavior, however: :Nex doesn't move the cursor,
instead a vim error gets
issued: "E163: There is only one file to edit". :Nexp (and longer)
works. There are two commands
that also begin with :Ne... (:NetUserPass and :NetrwSettings) which I
assume are causing this
behavior. Perhaps its a vim bug?
Regards,
Chip Campbell
