On Sun, May 15, 2016, Mario D wrote:
>
> > You might try with a different terminal or trying, if any of those settings
> > circumvents this problem
> >
> > :set term=builtin_ansi
> > :set t_RV=
> > :set t_u7=
> >
>
> Yes: the first setting seems to do the job.
> I added the line
>
> autocmd BufReadPre,FileReadPre *.asc,*.gpg set term=builtin_ansi
>
> in my .vimrc and everything seems to work nicely. Sure, this way I am stick to a somewhat primitive set of colors for syntax highlighting while editing encrypted files, but I can cope with this.... :)
As a workaround (without forcing term=builtin_ansi), do you have any
success if you hit backspace a bunch of times at the password prompt,
before you start typing the password?
--
Eric Christopherson
--
--
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.
Sunday, May 15, 2016
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment