Re: Tracing Vim into a log file.

On Wed, 26 Oct 2011, Eddine wrote:

> Hey Ben
>  
>  
> I think you give me the right hint I have this autocmd in my _vimrc
>  
>  
> autocmd BufReadPost *
> \ if line("'\"") > 0 && line("'\"") <= line("$") |
> \ exe "normal g`\"" |
> \ endif
>
>  
> so is it replacable by the autocmd you gave
>  
>  au BufReadPost * normal g`"
>

No, that's not what I meant at all. I thought something simpler might
be making things worse, though in hindsight, I think it'd be about the
same.

I think the problem is something else that causes that autocmd to be
fired at the wrong time. I mentioned the 'autoread' option (which I
don't think will ever fire when you're in insert mode, but comes into
play with files that change on disk while you're editing). It seems
more likely to me that some other autocmd (possibly on the CursorMovedI
event?) might do something that would trigger a reload of changed files.

What plugins have you installed, or what other autocmds do you have?

--
Best,
Ben

--
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