what version of vim are you using?
Also, what is the output of:
infocmp screen
I have an older machine that has different output than my usual dev pc.
I have not tested anything over there... it would require installing tmux,
libevent, and probably a few other things.
But I was wondering if perhaps your terminfo is different or older or
something.
I don't know how else to determine the "version" of your terminfo
database...
just trying to figure out what else might be "different".
On Wed, May 18, 2011 at 4:21 PM, Robin Lee Powell <
rlpow...@digitalkingdom.org> wrote:
> Yes.
>
> -Robin
>
> On Thu, May 19, 2011 at 12:18:52AM +0100, Nicholas Marriott wrote:
> > I don't think it is the theme itself, looks just to be full of colours
> > and a way to calculate colours from strings.
> >
> > Maybe is vim is doing its own stuff when you run a 256-colour theme on a
> > non-256-colour terminal which somehow wrongly depends on bce.
> >
> > Do you see this with TERM=screen-256color?
> >
> >
> >
> > On Wed, May 18, 2011 at 04:11:06PM -0700, Robin Lee Powell wrote:
> > > Ah, you're right; vim is doing something weird.
> > >
> > > If I comment out my vimrc, everything works fine with HEAD.
> > >
> > > Yeh, it's "colorscheme desert256" that's doing it; in HEAD it's fine
> > > without that.
> > >
> > > I suppose I should report this to the desert256 author?, but I don't
> > > really understand the issue well enough; what should I say?
> > >
> > > -Robin
> > >
> > > On Thu, May 19, 2011 at 12:04:49AM +0100, Nicholas Marriott wrote:
> > > > i think vim is doing something wrong here
> > > >
> > > > bce should not make this difference and it is the only difference
> > > > between these two:
> > > >
> > > > $ infocmp -x screen screen-bce
> > > > comparing screen to screen-bce.
> > > > comparing booleans.
> > > > bce: F:T.
> > > > comparing numbers.
> > > > comparing strings.
> > > >
> > > > so sounds like vim is redrawing differently without bce and not
> > > > scrolling
> > > >
> > > > bce is background-colour-erase and just means the terminal can erase
> > > > using the background colour rather than black
> > > >
> > > > does changing vim theme make any difference? is your theme 256 or 16
> > > > colour?
> > > >
> > > >
> > > > On Wed, May 18, 2011 at 03:55:28PM -0700, Robin Lee Powell wrote:
> > > > > On Wed, May 18, 2011 at 03:27:20PM -0700, Micah Cowan wrote:
> > > > > >
> > > > > > A workaround should be to alias vim to 'clear; vim' or something.
> > > > >
> > > > > Ah. Yes, that works; with older tmux I had tested clear and it
> > > > > broke in the same way vim does, but with HEAD this works fine.
> > > > >
> > > > > > What I don't understand is: what made vim change what it's
> sending
> > > > > > in terminal codes? TERM was set to screen in both cases, right?
> > > > > > ...or do you have TERM set inappropriately within tmux? And why
> > > > > > isn't it doing the exact same thing when you're running it under
> > > > > > screen? It looks like vim _is_ still sending the clear-screen
> > > > > > codes in screen_new_1.txt (which is why it's still working)...
> > > > > > what's different?
> > > > >
> > > > > *Interesting*.
> > > > >
> > > > > Under screen, the terminal is "screen-bce". Under tmux, it's
> > > > > "screen".
> > > > >
> > > > > If I set the terminal to "screen-bce" under tmux HEAD, the problem
> > > > > goes away. It doesn't appear help on 1.3 on the same machine, or
> > > > > 1.4 on the other machine, only HEAD.
> > > > >
> > > > > My suspicion, therefore, is that the screen terminal on your
> machine
> > > > > is like the screen-bce terminal on mine, somehow. I don't really
> > > > > know much about terminal definitions; if you tell me how to dump
> it,
> > > > > I will.
> > > > >
> > > > > I don't know if that actually answers your question it terms of
> > > > > vim's behaviour, although I suspect it does.
> > > > >
> > > > > This fully qualifies as a workaround from my perspective, and I'm
> > > > > more than happy to stop now, although if you want any further help
> > > > > nailing down the details, I'm *more* than happy to give it.
> > > > >
> > > > > I really *really* appreciate all your help.
> > > > >
> > > > > -Robin
> > > > >
> > > > > --
> > > > > http://singinst.org/ : Our last, best hope for a fantastic
> future.
> > > > > Lojban (http://www.lojban.org/): The language in which "this
> parrot
> > > > > is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
> > > > > is "na nei". My personal page:
> http://www.digitalkingdom.org/rlp/
> > > > >
> > > > >
> ------------------------------------------------------------------------------
> > > > > What Every C/C++ and Fortran developer Should Know!
> > > > > Read this article and learn how Intel has extended the reach of its
> > > > > next-generation tools to help Windows* and Linux* C/C++ and Fortran
> > > > > developers boost performance applications - including clusters.
> > > > > http://p.sf.net/sfu/intel-dev2devmay
> > > > > _______________________________________________
> > > > > tmux-users mailing list
> > > > > tmux-users@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/tmux-users
> > >
> > > --
> > > http://singinst.org/ : Our last, best hope for a fantastic future.
> > > Lojban (http://www.lojban.org/): The language in which "this parrot
> > > is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
> > > is "na nei". My personal page: http://www.digitalkingdom.org/rlp/
>
> --
> http://singinst.org/ : Our last, best hope for a fantastic future.
> Lojban (http://www.lojban.org/): The language in which "this parrot
> is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
> is "na nei". My personal page: http://www.digitalkingdom.org/rlp/
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users
>
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
