vimdev at Yahoo! Groups

Re: Crash with completefunc mapping followed by text

Dominique Pellé — Sat, 04 Jul 2009 07:00:34 GMT

... Hi I can still reproduce the bug with latest Vim-7.2.222. However, I have not found the way to fix it. I can see that function ins_compl_free() frees

Re: path completion case sensitivity on unix

Matt Wozniski — Fri, 03 Jul 2009 18:53:49 GMT

... Vim couldn't possibly obey settings in .inputrc, since it doesn't use readline. As for case-insensitive completion, see this:

path completion case sensitivity on unix

Thomas Rowe — Fri, 03 Jul 2009 18:33:29 GMT

Path completion on Windows and Unix are different regarding case sensitivity. Given file './Blah' on Windows, vim command ':e b' will expand out to ':e

Re: Reason why dict_unref(-1) is called?

björn — Fri, 03 Jul 2009 18:23:52 GMT

... VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Apr 13 2009 18:52:48) MacOS X (unix) version Included patches: 1-148 From what I can tell it may be hard to

Re: Reason why dict_unref(-1) is called?

Bram Moolenaar — Fri, 03 Jul 2009 18:16:12 GMT

... There was a patch to the garbage collecor in 7.2.192. Were the patches up to that number included? -- "I can't complain, but sometimes I still do." (Joe

Re: Patch to try out: ":unsilent"

Bram Moolenaar — Fri, 03 Jul 2009 18:11:34 GMT

... Look at the stuff that Charles Campbell made. I don't think that "uniform logging" will help, really. I mean, what's simpler than: let g:mylog = [] ...

Re: Patch to try out: ":unsilent"

Ingo Karkat — Thu, 02 Jul 2009 21:02:40 GMT

... I guessed you would want this for debugging / logging, though one has to differentiate: If the plugin really needs to inform the user about something, ...

Re: Patch to try out: ":unsilent"

Matt Wozniski — Thu, 02 Jul 2009 20:53:41 GMT

Oops, accidentally sent this to Bram off-list. ... It just seems that it would be nicer if each plugin didn't need to roll its own ad-hoc logging solution.

Reason why dict_unref(-1) is called?

björn — Thu, 02 Jul 2009 19:33:13 GMT

Hi, I received the following report of a crash inside Vim on the MacVim project page: http://code.google.com/p/macvim/issues/detail?id=191 From the stack trace

Re: Patch to try out: ":unsilent"

Bram Moolenaar — Thu, 02 Jul 2009 18:08:13 GMT

... The message history is to store displayed messages. If a message isn't displayed then it should not be in the history. If you want to log some things to

Re: Patch to try out: ":unsilent"

Matt Wozniski — Thu, 02 Jul 2009 00:45:33 GMT

... It seems like a good idea, if only for the symmetry. Any chance for another change to how :silent works, though, while we're at it? I'd find it very

Re: Patch to try out: ":unsilent"

Tony Mechelynck — Thu, 02 Jul 2009 00:16:07 GMT

... [...] Looks interesting. Assuming that Vim's behaviour won't change if it isn't used, and considering, as Raúl said, the small cost in terms of code, why

Re: vim qt on embedded devices

Markus Heidelberg — Wed, 01 Jul 2009 21:38:10 GMT

... This might be interesting for you, it tells about various different ways of creating a GUI around Vim, some active, others not:

Patch 7.2.222

Bram Moolenaar — Wed, 01 Jul 2009 18:19:51 GMT

Patch 7.2.222 Problem: ":mksession" doesn't work properly with 'acd' set. Solution: Make it work. (Yakov Lerner) Files: src/ex_docmd.c ...

Re: Patch to try out: ":unsilent"

Raúl Núñez de Arenas Coronado — Wed, 01 Jul 2009 17:09:42 GMT

Saluton Bram :) ... I would find it very useful, specially for the example you use in the help text. Moreover, it is a very "cheap" command in code terms.