On Thu, Jun 23, 2011 at 5:03 AM, Nicholas Marriott
wrote:
> I've applied this to OpenBSD, thanks.
>
> tcunha is currently too busy to sync up with SF but I'm going to try and
> do it this weekend if I've got time.
Likewise, I have added that patch to Ubuntu's tmux package.
Thanks for your respon
I've applied this to OpenBSD, thanks.
tcunha is currently too busy to sync up with SF but I'm going to try and
do it this weekend if I've got time.
On Mon, Jun 20, 2011 at 05:29:35PM -0500, Dustin Kirkland wrote:
> On Mon, Jun 20, 2011 at 5:14 PM, Nicholas Marriott
> wrote:
> > TERM=gnome is nc
On Mon, Jun 20, 2011 at 05:29:35PM -0500, Dustin Kirkland wrote:
> On Mon, Jun 20, 2011 at 5:14 PM, Nicholas Marriott
> wrote:
> > TERM=gnome is ncurses not tmux
>
> Forgive, I'm sorry, I don't understand what this means. I'd like to
> use gnome-terminal to either create or connect to a tmux ses
On Mon, Jun 20, 2011 at 5:14 PM, Nicholas Marriott
wrote:
> TERM=gnome is ncurses not tmux
Forgive, I'm sorry, I don't understand what this means. I'd like to
use gnome-terminal to either create or connect to a tmux session,
wherein I bind-key -n S-F1..S-F4 to some functionality. It's not
immed
TERM=gnome is ncurses not tmux
i'll look at the patch again tomorrow
On Mon, Jun 20, 2011 at 04:55:18PM -0500, Dustin Kirkland wrote:
> On Mon, Jun 20, 2011 at 4:26 PM, Nicholas Marriott
> wrote:
> > What's wrong with using TERM=gnome outside tmux? Doesn't it have these
> > set correctly? Or is
On Mon, Jun 20, 2011 at 4:26 PM, Nicholas Marriott
wrote:
> What's wrong with using TERM=gnome outside tmux? Doesn't it have these
> set correctly? Or is tmux not correctly picking them up?
kirkland@x201:~$ export TERM=gnome
kirkland@x201:~$ tmux
open terminal failed: missing or unsuitable termin
email is better, cheers
On Mon, Jun 20, 2011 at 12:49:46PM -0500, Dustin Kirkland wrote:
> On Mon, Jun 20, 2011 at 10:46 AM, Randy Stauner
> wrote:
> > that's strange... i tried something similar but i think i had the key combo
> > wrong... oops.
> > I also didn't realize that it was only F1-F4
What's wrong with using TERM=gnome outside tmux? Doesn't it have these
set correctly? Or is tmux not correctly picking them up?
On Sat, Jun 18, 2011 at 11:30:29PM -0500, Dustin Kirkland wrote:
> On Fri, Jun 17, 2011 at 8:13 PM, Dustin Kirkland
> wrote:
> > Howdy!
> >
> > I'm trying to bind some
On Mon, Jun 20, 2011 at 10:46 AM, Randy Stauner
wrote:
> that's strange... i tried something similar but i think i had the key combo
> wrong... oops.
> I also didn't realize that it was only F1-F4 that have these "other" codes.
> weird.
> Anyway, this patch works for me.
> Thanks!
Great! Thanks
that's strange... i tried something similar but i think i had the key combo
wrong... oops.
I also didn't realize that it was only F1-F4 that have these "other" codes.
weird.
Anyway, this patch works for me.
Thanks!
On Sat, Jun 18, 2011 at 9:30 PM, Dustin Kirkland
wrote:
> On Fri, Jun 17, 2011 at
On Fri, Jun 17, 2011 at 8:13 PM, Dustin Kirkland
wrote:
> Howdy!
>
> I'm trying to bind some Shift- and Alt- keys using the bind-key command.
>
> I've found the helpful S- and M- prefixes, which is quite handy and nice.
>
> It seems, though, that my terminal (gnome-terminal) sets TERM=xterm,
> but
Using xfce4-terminal (TERM=xterm-265color)
I see the same sequence when pressing shift-F2.
The man page does not suggest that tmux supports "S-" as the shift modifier,
and if it did I wouldn't know how to test it... you don't bind S-w, you just
bind W...
tmux does support the F2 key,
but for me (
Howdy!
I'm trying to bind some Shift- and Alt- keys using the bind-key command.
I've found the helpful S- and M- prefixes, which is quite handy and nice.
It seems, though, that my terminal (gnome-terminal) sets TERM=xterm,
but some key sequences (such as Shift-F2) differ slightly between
gnome-t
13 matches
Mail list logo
