I have been encountering an intermittent coredump using vim 7.1 under
Hardy, see the subject for the exact version. Please let me know if
this is not the correct forum for this message.
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case today. The backtrace
On Oct 14, 12:13 pm, frankjas [EMAIL PROTECTED] wrote:
I have been encountering an intermittent coredump ...
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case today...
Brilliant.
follows. It looks like the field uh_next_alt is being corrupted. Often
in
On Mon, Oct 13, 2008 at 8:37 PM, John Little wrote:
On Oct 14, 12:13 pm, frankjas wrote:
I have been encountering an intermittent coredump ...
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case today...
Brilliant.
follows. It looks like the field
On Oct 13, 6:41 pm, Matt Wozniski [EMAIL PROTECTED] wrote:
On Mon, Oct 13, 2008 at 8:37 PM, John Little wrote:
On Oct 14, 12:13 pm, frankjas wrote:
I have been encountering an intermittent coredump ...
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case
I've been playing around with a plugin
(http://www.vim.org/scripts/script.php?script_id=2378), trying to
specify a path to the _command_ that is passed to system(). Since this
command may have spaces in it, it needs to be wrapped in quotes.
However, if it is wrapped in quotes, the default
