Charles Campbell wrote:
So, a feature request: how about a p-args that breaks the input
arguments at whitespace (but otherwise leaves the arguments alone). The
p is to be vaguely reminescent of: pattern-arguments (as in regular
expression patterns)?
I think the last time
Patch 7.1.081
Problem:Command line completion for a shell command: cat /tmp/fileTab
doesn't work.
Solution: Start the file name at any character that can't be in a file name.
(Martin Toft)
Files: src/ex_docmd.c
*** ../vim-7.1.080/src/ex_docmd.c Tue Aug
Hi
Valgrind memory checker detects a bug when entering the command :cs find g.
(requires support for cscope in vim)
==19660== Conditional jump or move depends on uninitialised value(s)
==19660==at 0x80D27F4: cs_find (if_cscope.c:969)
==19660==by 0x80D13E6: do_cscope_general
I just noticed that there was a memory leak
in the patch I sent in my previous email.
So here it is again without the memory leak.
retrieving revision 1.22
diff -c -r1.22 if_cscope.c
*** if_cscope.c 11 Mar 2007 14:48:29 - 1.22
--- if_cscope.c 18 Aug 2007 17:48:54 -
***
All,
I just upgraded to version 1.8 of Yegappan Lakshmanan's convenient
grep.vim[1] plugin. As part of the fix in version 1.8 for handling
spaces in file and path names, the `--null` switch was added to xargs.
Unfortunately, the OS X version of xargs doesn't support the long
spelling of
Dominique Pelle wrote:
Valgrind memory checker detects a bug when entering the command :cs find g.
(requires support for cscope in vim)
==19660== Conditional jump or move depends on uninitialised value(s)
==19660==at 0x80D27F4: cs_find (if_cscope.c:969)
==19660==by 0x80D13E6:
All,
The mac port of gvim has a bug in the implementation of :winpos.
Version: 7.1.82 (mac only)
Symptom:
The following command, which should do nothing, causes gvim's window
to move up the screen on the mac:
exe winpos . getwinposx() . . getwinpoxy()
On Linux and Windows, the above
I don't think that skipping white space before the pattern is a problem.
I would rather call it an improvement. However, I think your solution
also has the effect that it's not possible to have a space in the
pattern. That is undesired.
I found another way to fix it, and preserve old
Hi,
On Aug 18, 2007, at 5:00 PM, Bram Moolenaar wrote:
Problem:Compiler warnings for using const char * for char *.
Solution: Add type casts. (Chris Sutcliffe)
at least in C++. this is a very dangerous patch. If you cast a const
char* to a char* and then modify the char*, you get
Ismo Puustinen mentioned:
I recently wrote an implementation of the optimal line breaking
algorithm (in Ruby). If you are interested, the file is located
here, with a small piece of test code at the end:
http://lissujaismo.net/rbpar/rbpar_engine.rb
You can run the test
Hello,
The following response to
:verbose set foo?
was set in error handler
is not informative. To be informative, the message
should mention something to indicate who/what/when/where
was trying to set the illegal value.
For example, I have been using a valid
Hi all,
It looks like filename completion in the command-line mode is broken
in Vim 7.1.82. I am running Vim 7.1.82 on Linux and see the following
issue.
$ cd vim7/src
$ vim
:edit *unix*Tab
When I press Tab to complete the name of files containing the string
unix in them, it
12 matches
Mail list logo
