Matt Kaniaris wrote:
> Ran into this guy using ctrl-p. I don't have a traceback, but the
> problem is that close_buffer sets win->w_buffer to NULL and
> set_last_cursor then explodes. Since w_buffer isn't guaranteed to
> exist, set_last_cursor should just check for it.
>
> more info:
>
>
> close_buffer(win, buf, action, abort_if_last)\
> {
> ...
> win->w_buffer = NULL; /* make sure we don't use the buffer now */
> ...
> }
>
>
> void
> set_last_cursor(win)
> win_T *win;
> {
> win->w_buffer->b_last_cursor = win->w_cursor;
> }
Do you know how to reproduce this? Where/how do you use CTRL-P?
It does not normally close a buffer.
--
The Law of VIM:
For each member b of the possible behaviour space B of program P, there exists
a finite time t before which at least one user u in the total user space U of
program P will request b becomes a member of the allowed behaviour space B'
(B' <= B).
In other words: Sooner or later everyone wants everything as an option.
-- Vince Negri
/// 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
