On 2010-06-09, Xavier Dectot wrote:
> Le 09/Jun - 18:56, Xavier Dectot a écrit
> > Le 09/Jun - 07:55, Gary Johnson a écrit
> > > On 2010-06-09, Xavier Dectot wrote:
> > > > Hello, and sorry if this has been asked a hundred times, but I can't
> > > > seem to find the answer. I'm using vim 7.2 on FreeBSD 8.0 and
> > > > vim-latex suite, and some keymappings are definitely not working when
> > > > I use "normal" vim, while they do work in gvim. Up to now, I've at
> > > > least encountered the problem with F9, which capitalises the first
> > > > letter of the line instead of launching TeX_Completion, and /rf, which
> > > > does nothing at all. Any hint on what might be the problem or how to
> > > > work it around ?
> > > You can see what kind of terminal vim thinks you're using by
> > > executing
> > >
> > > :set term?
> > >
> > > Does that match what you're really using?
> >
> > Well, yes and no. In urxvt, I :set term returns xterm, so something is wrong
> > here, but in screen, which is where I am indeed typing, :set term returns
> > screen, which is correct. Anyhow, in urxvt as in screen as in xterm, Ctrl-V
> > F9
> > returns ^[[20~, so this should not be the problem. I even tried :set termcap
> > tk_9=^[[20~ with no better result.
> > :(
> Oh, and FWIW, I tried
> export TERM=rxvt-unicode
> vim
> and got the same results...
First of all, to set the escape sequence for F9, the command is
:set t_k9=^[[20~
where ^[ is a literal escape. You wrote that you set tk_9, which
won't work.
What does
:set termcap
show for the "t_k9 <F9>" entry?
I have tried three configurations:
1. Cygwin rxvt running a Cygwin vim on Windows XP;
2. Cygwin rxvt running screen, then a Cygwin vim, again on Windows
XP; and
3. Cygwin mintty on a different Windows XP box running rlogin
across a VPN to a box running RHEL4, and on that box running
screen and vim.
In all cases, ":set termcap" shows an escape sequence defined for
t_k9. Both rxvt and mintty cause 'term' to be "xterm" and screen
causes 'term' to be "screen". I don't think I've done anything
special to make that all work, so I think we should be able to find
some simple fix for your environment.
> Thanks for your help, BTW
You're welcome. I'm sorry it hasn't done any good so far.
Regards,
Gary
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Vim-latex-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
