On Tuesday, January 10, 2017 at 4:11:47 PM UTC-5, Dominique Pelle wrote:
> Matthew Desjardins wrote:
>
> > With a littler more background on reproducing, I've only
> > gotten crashes to occur after opening the command-line
> > window with <c-f> on a command line that already has text.
> > The resulting window won't actually have that text on the
> > current line as it should, and attempting to insert text from
> > there will then cause a crash.
>
> I can't reproduce it so far. Perhaps you have a setting that
> triggers it. Can you try to see if it happens with: vim -u NONE?
> It it does not happen with vim -u NONE, can you narrow down
> your setting in .vimrc that triggers the bug?
>
> Regards
> Dominique
It does occur with vim -u NONE (as in OP)
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, January 10, 2017
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment