>
> Well, I'm just not sure it's worth the extra code, it's a pretty rarely
> used feature.
Fair enough. Although it might be popular with people who are trying to
synchronize their Windows clipboards. But maybe there is another way to do it,
I did see some hint of that in the code but never fo
> Date: Sat, 11 Aug 2012 08:31:15 +0100
> From: nicholas.marri...@gmail.com
>
> Thanks for your work but can you explain why you want/need this? Does
> anything actually use it?
>
Hi Nicholas,
Use it for sending to a local printer when on the road, and
> Date: Sun, 5 Aug 2012 19:54:09 +0200
> From: deb...@jstimpfle.de
[...]
> Thank you Sean, I didn't know of %q (it actually isn't documented for my
> distribution). Can this be considered "safe"? (many shells out there,
> and I fear proper escaping is not
> Date: Fri, 3 Aug 2012 16:17:56 +0200
[...]
>
> The only way I could do this programmatically is something like
>
> $ tmux new-window -d -t mysession: -n window-remotehost "ssh remotehost
> \"my shellcommandline on the remote host\""
>
> I hope this already shows the problem: Both tmu
From: seanl...@sympatico.ca
> Ugh! What a mess this stuff is. The documentation is terse and ambiguous so
> I just went back to the kernel source.
Just wanted to be clear that this has nothing to do with Tmux or its
documentation. Tmux is doing the right thing(tm) and passing the values
Subject: Re: Changing cursor color in a Linux framebuffer console
>
> Hi Sean,
>
> Thanks for the helpful explanations & examples, this gets me a lot
> closer. I've a few more questions...
>
> * Sean Estabrooks [120727 23:25]:
> > ...
> > Here is a set
ve will select a red cursor for insert mode. Without
ranting about the reasons, here are the codes you'll have to choose from
for each of the 8 available colors:
Black = 224
Blue = 192
Green = 160
Cyan = 128
Red = 96
Magenta = 64
Orange = 32
Whi
Hi John,
Here's one example:
terminal-overrides ",*:Cc=\\E]12;%p1%s\\007:Cr=\\E]112\\007:"
and for vim the codes that tmux expects for setting cursor color,
let &t_SI="\]12;red\007"
let &t_EI="\]112\007"
Hope it helps,
Sean
> Date: Thu, 26 Jul 2012 10:14:50 -0700
> From: listm...@b79.net
> T
Pass data bracketed by printer start-stop codes through
to the client terminal or emulator. Am using this here
for "printing" to the Windows clipboard.
The first three patches add scaffolding for the fourth
patch which actually handles the control sequences.
The last two patches are just minor cl
Forward CSI "Media Copy" printer control sequences ESC[5i & ESC[4i
and the data they bracket to client for output on a local printer.
Once started, data is passed as unaltered binary bytes. All
control sequences other than Printer-Controller-Off, are ignored.
While not comprehensive, this facility
Both parameters are only used to access a single element
of their respective structures. So pass each desired
element directly instead of its parent.
This allows the function to be used elsewhere when the
parent structure isn't as readily available.
---
input.c | 16
1 file cha
---
cmd-if-shell.c |2 --
1 file changed, 2 deletions(-)
diff --git a/cmd-if-shell.c b/cmd-if-shell.c
index 3747447..636cf80 100644
--- a/cmd-if-shell.c
+++ b/cmd-if-shell.c
@@ -106,11 +106,9 @@ cmd_if_shell_free(void *data)
{
struct cmd_if_shell_data*cdata = data;
st
Prior to this change the since_buffer failed to include input
characters when the state handler returned non-zero.
With this change the current character is already in the
since_buffer when the state handler is invoked so it doesn't
matter if the handler suppresses a state transition.
---
input.c
Data is passed to client in bulk with no character set
or unicode conversion. This is meant to be used to pass
through data that wont be appearing on the client tty;
thus no change is made to screen memory.
The data is only passed to clients that are currently
displaying the sending window. A futu
---
tty.c | 25 +
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/tty.c b/tty.c
index c465fec..196b712 100644
--- a/tty.c
+++ b/tty.c
@@ -667,7 +667,6 @@ tty_write(
{
struct window_pane *wp = ctx->wp;
struct client *c;
-
Hi Nicholas,
>
> Hi
>
> Thanks for your work on this.
Was a nice diversion and the tmux source code is quite a pleasure
to read.
>
> Although, h. I'm really not wild about custom tmux escape sequences,
> although they have obvious advantages. I'll have to think about it. We
> need a better
Hi Nicholas,
> Does rxvt support these sequences? I don't think screen does. Probably
> best only to check for xterm.
Good catch. I really should have thought a bit more before just
copy-n-pasting from tty_set_title. Have changed the code to only
operate for an xterm by default now. Also fixe
> Date: Sun, 13 Mar 2011 21:28:54 +
> From: nicholas.marri...@gmail.com
>
> This looks good.
>
> You will have to use \033]112\007 to reset the cursor colour to default
> for panes where it hasn't been set. Personally I would use NULL for this
> rather than an empty string but it's not too i
> Date: Sun, 13 Mar 2011 12:45:52 +
> From: nicholas.marri...@gmail.com
>
> Hi
>
> I think the right way to do this is to add support for the xterm cursor
> sequences (preferably both the cursor shape and colour). This will mean
> saving the colour value as a string for each pane.
>
>
Of cour
> It is in the OpenBSD tree, it'll be in SF tree when they are
> synced up, probably not too long.
>
> revision 1.37
> date: 2011/03/07 23:46:27; author: nicm; state: Exp; lines: +49 -24
> Support passing through escape sequences to the underlying terminal by
> using DCS with a "tmux;" prefix.
20 matches
Mail list logo
