Robin Lee Powell wrote:
> On Wed, May 18, 2011 at 12:06:28PM -0700, Micah Cowan wrote:
>> If your .tmux.conf is not even being read, then that's usually a
>> sign that your tmux server was already running (.tmux.conf is only
>> read at server startup, not at the start of every new session) -
>> so
On Wed, May 18, 2011 at 05:18:13PM -0700, Randy Stauner wrote:
> what version of vim are you using?
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 7 2011 15:02:28)
Included patches: 1-154
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by bui...@brahms.debian.org
Huge version w
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 perha
Well you can try talk to the theme maintainer but my guess would be this
is a vim problem, but really it is hard to guess exactly what without
knowing or going to look at the vim code.
On Wed, May 18, 2011 at 04:21:16PM -0700, Robin Lee Powell wrote:
> Yes.
>
> -Robin
>
> On Thu, May 19, 2011
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 ter
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?
That still makes me wonder why it was working under screen, or tmux
with screen-bce, but like I said if you can tell me what to say :),
I'll talk to the desert256 people.
I should have tried vim-with-no-vimrc on HEAD ealier; sorry about
that.
-Robin
On Wed, May 18, 2011 at 04:11:06PM -0700, Robi
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 eno
(05/18/2011 04:07 PM), Micah Cowan wrote:
> (05/18/2011 03:55 PM), 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
(05/18/2011 03:55 PM), 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
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
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 mad
(05/18/2011 02:56 PM), Robin Lee Powell wrote:
> Terminal size is 80x25, because I believe that to actually be
> relevant to the behaviour one gets on catting them back out.
Well, what I meant (and should have said) was, provided that the lines
all start where they're meant to.
> http://teddyb.or
On Wed, May 18, 2011 at 02:04:21PM -0700, Micah Cowan wrote:
> (05/18/2011 01:47 PM), Robin Lee Powell wrote:
> >> I'm using the tmux from CVS HEAD. Perhaps you can try that out?
> >
> > Certainly.
>
> Okay, good news: I grabbed a copy of tmux 1.4 from sourceforge,
> built and tested with it. I c
On Wed, May 18, 2011 at 01:53:05PM -0700, Micah Cowan wrote:
> (05/18/2011 01:47 PM), Robin Lee Powell wrote:
> > On Wed, May 18, 2011 at 01:43:38PM -0700, Micah Cowan wrote:
> >> (05/18/2011 01:28 PM), Micah Cowan wrote:
> >>> (05/18/2011 01:19 AM), Robin Lee Powell wrote:
> It's vim, not les
(05/18/2011 01:47 PM), Robin Lee Powell wrote:
>> I'm using the tmux from CVS HEAD. Perhaps you can try that out?
>
> Certainly.
Okay, good news: I grabbed a copy of tmux 1.4 from sourceforge, built
and tested with it. I can reproduce. So it sounds like it's a problem
that has since been fixed, s
(05/18/2011 01:47 PM), Robin Lee Powell wrote:
> On Wed, May 18, 2011 at 01:43:38PM -0700, Micah Cowan wrote:
>> (05/18/2011 01:28 PM), Micah Cowan wrote:
>>> (05/18/2011 01:19 AM), Robin Lee Powell wrote:
It's vim, not less, and yes, it appears to be overwriting.
The issue is that I
On Wed, May 18, 2011 at 01:43:38PM -0700, Micah Cowan wrote:
> (05/18/2011 01:28 PM), Micah Cowan wrote:
> > (05/18/2011 01:19 AM), Robin Lee Powell wrote:
> >> It's vim, not less, and yes, it appears to be overwriting.
> >>
> >> The issue is that I don't have this problem in screen.
> >>
> >> OK,
On Wed, May 18, 2011 at 01:39:35PM -0700, Robin Lee Powell wrote:
> On Wed, May 18, 2011 at 01:28:32PM -0700, Micah Cowan wrote:
> > (05/18/2011 01:19 AM), Robin Lee Powell wrote:
> > > It's vim, not less, and yes, it appears to be overwriting.
> > >
> > > The issue is that I don't have this probl
(05/18/2011 01:28 PM), Micah Cowan wrote:
> (05/18/2011 01:19 AM), Robin Lee Powell wrote:
>> It's vim, not less, and yes, it appears to be overwriting.
>>
>> The issue is that I don't have this problem in screen.
>>
>> OK, screenshots of screen and tmux (in alternate-screen off mode).
>> Process i
On Wed, May 18, 2011 at 01:28:32PM -0700, Micah Cowan wrote:
> (05/18/2011 01:19 AM), Robin Lee Powell wrote:
> > It's vim, not less, and yes, it appears to be overwriting.
> >
> > The issue is that I don't have this problem in screen.
> >
> > OK, screenshots of screen and tmux (in alternate-scre
(05/18/2011 01:19 AM), Robin Lee Powell wrote:
> It's vim, not less, and yes, it appears to be overwriting.
>
> The issue is that I don't have this problem in screen.
>
> OK, screenshots of screen and tmux (in alternate-screen off mode).
> Process is:
>
> [new window]
> # seq 1 100
> # vim
> [ty
On Wed, May 18, 2011 at 12:33:11PM -0700, Micah Cowan wrote:
> (05/18/2011 11:18 AM), Robin Lee Powell wrote:
>
> > http://teddyb.org/~rlpowell/media/public/tmp/screen.txt
> >
> > http://teddyb.org/~rlpowell/media/public/tmp/tmux.txt
>
> Do you still get the same effect if you set your prompt to
(05/18/2011 11:18 AM), Robin Lee Powell wrote:
> http://teddyb.org/~rlpowell/media/public/tmp/screen.txt
>
> http://teddyb.org/~rlpowell/media/public/tmp/tmux.txt
Do you still get the same effect if you set your prompt to something
that doesn't contain any "special" character sequences? I don't
On Wed, May 18, 2011 at 12:06:28PM -0700, Micah Cowan wrote:
> (05/18/2011 11:18 AM), Robin Lee Powell wrote:
> > Huh. My tmux.conf doesn't seem to actually *work*; I have to
> > manually do a ":set-window-option alternate-screen" when I
> > launch tmux for it to actually be set correctly. That's
(05/18/2011 11:18 AM), Robin Lee Powell wrote:
> Huh. My tmux.conf doesn't seem to actually *work*; I have to
> manually do a ":set-window-option alternate-screen" when I launch
> tmux for it to actually be set correctly. That's a bit odd, isn't
> it? So in the tmux case there's a step for that,
On Wed, May 18, 2011 at 11:18:57AM -0700, Robin Lee Powell wrote:
> On Wed, May 18, 2011 at 09:56:49AM -0700, Micah Cowan wrote:
> > (05/18/2011 08:01 AM), Randy Stauner wrote:
> > > I have tried to recreate this according to your steps and it
> > > does not happen to me, things look as you would e
On Wed, May 18, 2011 at 09:56:49AM -0700, Micah Cowan wrote:
> (05/18/2011 08:01 AM), Randy Stauner wrote:
> > I have tried to recreate this according to your steps and it
> > does not happen to me, things look as you would expect them. I
> > tried zsh as well--no change.
> >
> > It does seem odd
Since I'm using the same vim config in both places, I wouldn't
expect that to change anything, and indeed it did not.
-Robin
On Wed, May 18, 2011 at 08:01:15AM -0700, Randy Stauner wrote:
> I have tried to recreate this according to your steps and it does not happen
> to me,
> things look as you
(05/18/2011 08:01 AM), Randy Stauner wrote:
> I have tried to recreate this according to your steps and it does not
> happen to me,
> things look as you would expect them.
> I tried zsh as well--no change.
>
> It does seem odd that even the prompt disappears in your example.
>
> This probably won
I have tried to recreate this according to your steps and it does not happen
to me,
things look as you would expect them.
I tried zsh as well--no change.
It does seem odd that even the prompt disappears in your example.
This probably won't help, but might be worth a try:
Try putting this line in
It's vim, not less, and yes, it appears to be overwriting.
The issue is that I don't have this problem in screen.
OK, screenshots of screen and tmux (in alternate-screen off mode).
Process is:
[new window]
# seq 1 100
# vim
[type some crap]
:q!
[backscroll mode, up 10 lines, screenshot]
http://
yeh just did, i don't follow what the 2nd problem is, can you send a
screenshot?
note the history will only ever include what less actually scrolled into
it, even with alternate-screen off. if less redraws by overwriting or
otherwise does not scroll the screen, the history won't be changed
On W
Nope; see rest of thread.
-Robin
On Wed, May 18, 2011 at 08:34:23AM +0100, Nicholas Marriott wrote:
> Turn off the alternate-screen option and it should change both of these.
>
>
>
> On Tue, May 17, 2011 at 06:10:58PM -0700, Robin Lee Powell wrote:
> >
> > I came, over the years, to rely very
Turn off the alternate-screen option and it should change both of these.
On Tue, May 17, 2011 at 06:10:58PM -0700, Robin Lee Powell wrote:
>
> I came, over the years, to rely very much on screen's backscroll
> behaviour[1], so certain aspects of tmux's behaviour have surprised
> me, and I'm won
On Tue, May 17, 2011 at 11:37:52PM -0700, Micah Cowan wrote:
> On 05/17/2011 10:46 PM, Robin Lee Powell wrote:
> >>"Replaces"? No, it'll scroll it off, I'd think. Which is what
> >>you said you wanted - all the backscroll intact.
> >
> >No, that is absolutely not what happens.
>
>
>
> Okay, well
On 05/17/2011 10:46 PM, Robin Lee Powell wrote:
>> "Replaces"? No, it'll scroll it off, I'd think. Which is what you
>> said you wanted - all the backscroll intact.
>
> No, that is absolutely not what happens.
Okay, well, I don't know what to tell you, because when _I_ do it (with
alternate-scr
On Tue, May 17, 2011 at 10:26:33PM -0700, Micah Cowan wrote:
> On 05/17/2011 10:21 PM, Robin Lee Powell wrote:
> >On Tue, May 17, 2011 at 09:16:16PM -0700, Micah Cowan wrote:
> >>On 05/17/2011 06:10 PM, Robin Lee Powell wrote:
> >>>
> >>>I came, over the years, to rely very much on screen's
> >>>ba
On 05/17/2011 10:21 PM, Robin Lee Powell wrote:
> On Tue, May 17, 2011 at 09:16:16PM -0700, Micah Cowan wrote:
>> On 05/17/2011 06:10 PM, Robin Lee Powell wrote:
>>>
>>> I came, over the years, to rely very much on screen's backscroll
>>> behaviour[1], so certain aspects of tmux's behaviour have
>>
On Tue, May 17, 2011 at 09:16:16PM -0700, Micah Cowan wrote:
> On 05/17/2011 06:10 PM, Robin Lee Powell wrote:
> >
> >I came, over the years, to rely very much on screen's backscroll
> >behaviour[1], so certain aspects of tmux's behaviour have
> >surprised me, and I'm wondering if they can be chang
On 05/17/2011 06:10 PM, Robin Lee Powell wrote:
>
> I came, over the years, to rely very much on screen's backscroll
> behaviour[1], so certain aspects of tmux's behaviour have surprised
> me, and I'm wondering if they can be changed.
>
> 1. When I quit "less", it goes away. I'm used to the outpu
I came, over the years, to rely very much on screen's backscroll
behaviour[1], so certain aspects of tmux's behaviour have surprised
me, and I'm wondering if they can be changed.
1. When I quit "less", it goes away. I'm used to the output of
less staying in the shell window/the terminal backscr
42 matches
Mail list logo
