Hello,
Tools such as tags, cscope, global, idutils etc. for spelunking code
essentially involve creating an index of the files in the project and using
this index. Tools like vim's :vimgrep work harder without the benefit of an
index. Some of the tools are restricted to C code only (with maybe
Yasuhiro Matsumoto wrote:
> helptags_one extract help tag like '*foo*'. it's used vim_strchr() to
> find second '*'. But vim_strchr() depend on current &encoding. Help
> file should be latin-1 or utf-8 encoding. So if DBCS is used for
> &encoding, it may not extract second '*'.
> Below is a patch
Dominique Pelle wrote:
> Attached patch adds @Spell to the runtime/syntax/awk.vim file
> so that Vim only highlights spelling mistakes in comments and
> strings when editing a awk source file with those settings:
>
> :syntax on
> :set spell
Thanks! Also for the ocaml.vim patch and others.
-
Ken Takata wrote:
> I wanted less.vim and less.sh to behave more like 'less'.
> The attached patch changes the following behavior:
>
> 1. Do not quit Vim automatically at the end of file. (less.vim)
>'more' quits at the end of file, but 'less' does not.
>
> 2. Do not wait the input of user,
Hello John,
Excerpt from John Beckett:
> Dominique Pellé wrote:
>> Yes. Maintainers were in CC of the emails. But perhaps I
>> should write to the maintainers only to avoid sending too many
>> emails to vim_dev (still more of those simple patches to
>> come...)
>
> There is no good way to do t
[forwarding to vim-dev]
On Fr, 11 Mai 2012, Richard wrote:
> The eval documentation says that col('$') returns
> "the number of characters ..."
> but it actually return the number of bytes.
You should mention this at the vim-dev mailinglist or even better,
prepare a patch and send it there or di
