On Tue, Apr 16, 2013 at 2:36 AM, Nicholas Marriott
wrote:
>Can you show the code you changed rather than making me guess? :-)
That would have been a sensible detail to include! Here is what I changed.
I don't know what this change might break.
--- ../temp/tmux-1.8/screen.c 2013-02-24 04:
Hi,
I have observed an occasional crash in tmux 1.8 when I change the font size
of
the terminal window. I haven't been able to determine a good set of
reproduce
steps yet, but I'll try some more later. In the meantime, here is a stack
trace:
#0 0x00430ca0 in screen_write_linefeed (ctx=
Thanks guys for looking into it. It is nothing more than a minor nuisance,
so I will happily continue using tmux.
Chris
On Tue, Feb 12, 2013 at 7:25 PM, Ben Boeckel wrote:
> On Tue, 12 Feb, 2013 at 09:48:38 GMT, Nicholas Marriott wrote:
> > Hmm. We can't change next-word-end because it is use
2013 at 09:52:05AM -0800, Christopher Collins wrote:
> >I have noticed an inconsistency among tmux copy mode and vim.* In
> >particular,
> >the 'e' key behaves slightly differently.
> >
> >Here are the behaviors of 'e' that I have observ
I have noticed an inconsistency among tmux copy mode and vim. In
particular,
the 'e' key behaves slightly differently.
Here are the behaviors of 'e' that I have observed:
* tmux copy mode: repositions cursor to end of current word + 1.
* vim:repositions cursor to end of curren
