Monday, June 24, 2013

Re: Vim 7.3 - Odd behaviour with Log file ESC sequences

On Monday, June 24, 2013 5:29:15 AM UTC-5, Philip Rhoades wrote:
>
> John Little <John.B.Little <at> gmail.com> writes:
> > The output of
> >
> > :scriptnames
> >
> > can aid understanding in these situations. "normal" behaviour of vim
> > is to display escape sequences like
> > your second case, not the first; in that first case there must be a
> > script, or commands in a .vimrc, causing
> > the sequences to be interpreted; the one I know about is AnsiEsc.vim,
> > http://www.vim.org/scripts/script.php?script_id=302.
>
>
> The output of :scriptnames hereunder but I still don't understand - does
> it mean that one of those scripts is recognising the directory that the
> log file is in and causing Vim to change it's display of the log file?
>

No. :scriptnames shows you every script that Vim has loaded since startup.

I notice your posted scriptnames output did NOT include a plugin like AnsiEsc. Would I be right to assume that your posted output applied to the case where escape sequences were shown as literal escape characters instead of being hidden?

In this case scriptnames is most useful if you can compare the output of the working case to the non-working case to see what differs.

As for the 1G command not working (to go to the top line), see the output of:

:verbose map G

--
--
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/groups/opt_out.

No comments:

Post a Comment