On 31-01-2009 Dominique Pelle <[email protected]> wrote:
> 
> Lech Lorens wrote:
> 
> > The attached patch makes it possible for the last argument in the
> > :cscope find [sgdctefi0-8] ...
> > command to be preceded by multiple spaces.
> 
> But isn't being able to search for something beginning with a space a feature?
> 
> For example:
> 
> :cs find e  foo
> :cs find e foo
> 
> The first one searches for " foo"
> The second one searches for "foo"
> 
> There is another old thread in vim_dev where this was discussed:
> 
> http://groups.google.com/group/vim_dev/browse_thread/thread/cafcb4b1fc5fdb90

Agreed. It seems to me a little bit inconsistent with the other Vim
commands that need to have spaces in their arguments escaped, though.

Anyway, the behaviour I corrected is listed in todo.txt under "Known
bugs" (the patch deletes it from the list). The list is quite long and
I'm trying to make it shorter. This is the second time today that I got
to fixing something listed as a bug, that is a feature in fact. The
other one was:

> When entering a C /* comment, after typing <Enter> for 70 times the indent
> disappears. (Vincent Beffara, 2008 Jul 3)

It's a feature actually - the code responsible for indenting code is
limited to search only the last 70 lines for a comment beginning
(probably so that it doesn't take too long).

It might be a good idea to clean up todo.txt so that people don't
concentrate too much on fixing things that aren't broken.

-- 
Cheers,
Lech

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui