Richard Brown wrote:
> Hi, 7.3.449 fixed an issue where this autocommand and the following
> sequence would cause a segfault:
>
> :autocmd BufWinLeave * if empty(&bt) | lclose | endif
> :call setloclist(1, [{'bufnr': 1, 'lnum': 1, 'text': 'testing'}])
> :lopen
> ^wk
> :q
>
> according to hg bisect it was 7.3.545 that reintroduced the issue.
>
> I think the following threads already discuss this
>
> https://groups.google.com/forum/#!msg/vim_dev/BsSUkBUCtjo/DerUD60MOFoJ
> https://groups.google.com/d/msg/vim_dev/lNY4xnUgz8g/svvYavPx-lIJ
Considering that 7.3.545 fixes a problem with autocommands, it's
unlikely that it introduced the problem, but rather uncovered another
problem.
Does that sequence of commands segfault also for "vim -u NONE"?
--
"Time flies like an arrow". So I put an arrow on my desk, now
awaiting one of these time flies showing up.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" 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
