On 10/28/06, Fabien Meghazi <[EMAIL PROTECTED]> wrote:
> In your .vimrc, you could just add
> if $TERM == "screen"
> set term="rxvt-xpm"
> endif
> That might be better in order not to confuse other
> applications...
Yeah thanks ! This is a clean tip for my problem.
I had tried to :set t
In your .vimrc, you could just add
if $TERM == "screen"
set term="rxvt-xpm"
endif
That might be better in order not to confuse other
applications...
Yeah thanks ! This is a clean tip for my problem.
I had tried to :set term=rxvt when vim was started without success so
I gave up this way
Fabien Meghazi wrote:
> I should have figured that on my own. Sorry for loosing your time.
> Indeed the escape sequence is sent by screen.
> So I tried to export TERM=rxvt-xpm and indeed, that worked.
> So it's just vim handling escape sequence differently according to
> TERM's value, and indeed my
I just did some tests, and in both xterm and rxvt, screen passed the
escape codes for Shift-Up through without altering them. Try going to a
command line in screen, running something like 'cat > /dev/null' and
checking to make sure that Shift-Up is still working from there while in
screen. If it
* Fabien Meghazi <[EMAIL PROTECTED]> [2006-10-23 09:31 +0200]:
> I use screen under rxvt-unicode, in my .vimrc, I map the Shift-Up key
> combination like this:
>
> noremap ^[[a zc
>
> This works under rxvt without problem, I can fold using Shift+Up arrow
>
> But as soon as I'm under screen it do
Hi all,
I would like to know if by any chance, someone here have the same
screen problem (this is not a vim problem) :
I use screen under rxvt-unicode, in my .vimrc, I map the Shift-Up key
combination like this:
noremap ^[[a zc
This works under rxvt without problem, I can fold using Shift+Up a
