>
>
> >As far as parsing command output, I'll need your help on that. I don't
> >think I'll be able to tell from the man page which commands generate
> which
> >errors. I will need to know if a command's output is normal or an
> error.
> >If the result is an error then I need two th
On Mon, Dec 06, 2010 at 05:44:29PM -0800, George Nachman wrote:
>- I added a %noop unsolicited message.
>- I changed the terminator from ^D to ^D NEWLINE to make it more
>human-friendly.
>- I'll keep ping because I do have a "send something every x seconds to
>keep the connectio
- I added a %noop unsolicited message.
- I changed the terminator from ^D to ^D NEWLINE to make it more
human-friendly.
- I'll keep ping because I do have a "send something every x seconds to keep
the connection alive" feature and ping will do the job.
As far as parsing command output, I'll need y
Do you want to differentiate error, info and normal ("print") output
from commands? If so, how?
On Tue, Dec 07, 2010 at 01:20:09AM +, Nicholas Marriott wrote:
> I want a %noop from tmux->terminal, I don't really care about a ping
> command, but if you need it then that's fine.
>
>
> On Mon,
I want a %noop from tmux->terminal, I don't really care about a ping
command, but if you need it then that's fine.
On Mon, Dec 06, 2010 at 04:47:18PM -0800, George Nachman wrote:
>Keeping ^D as the terminator. Not in love with the asymmetry, but ^D would
>be unnecessary in commands, and a
Keeping ^D as the terminator. Not in love with the asymmetry, but ^D would
be unnecessary in commands, and appears to be necessary in responses (with
the alternative being lengths, but that is hard on humans).
On Mon, Dec 6, 2010 at 4:24 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
actually scratch this, other commands can generate newlines and i don't
want to play substitution games
^D will be fine
On Tue, Dec 07, 2010 at 12:30:08AM +, Nicholas Marriott wrote:
> Since we give the length for "output" command and a pane target can't
> contain newlines, why not make EOF
Since we give the length for "output" command and a pane target can't
contain newlines, why not make EOF a newline? Using newline instead of
^D will make this usable by humans as well.
On Mon, Dec 06, 2010 at 04:01:05PM -0800, George Nachman wrote:
>Oh, I see the issue - when you give ssh a c
Two other things:
- We should have a "noop" command as well.
- I think the protocol commands (in both directions) should be clearly
different from normal tmux commands. I'd say prefix them with a % or
something or even make them capital letters (tmux commands will never
use caps).
On Mon,
Oh, I see the issue - when you give ssh a command to run that isn't your
shell then environment vars aren't passed through. I don't want to make it
difficult to be more flexible in the future, so I'll add a new command for
this. I could imagine one day supporting different settings for character
en
On Mon, Dec 06, 2010 at 03:36:56PM -0800, George Nachman wrote:
> > - There needs to be a mechanism to specify the client "identify"
> > information, particularly the terminfo description tmux should use but
> > also the terminal flags (if is UTF-8, 256 colours, 88
> > colours).
>
>
> > - There needs to be a mechanism to specify the client "identify"
> > information, particularly the terminfo description tmux should use
> but
> > also the terminal flags (if is UTF-8, 256 colours, 88
> > colours). Easiest probably to have that as an argument to -C.
> >
>
On Mon, Dec 06, 2010 at 03:25:51PM -0800, George Nachman wrote:
>On Mon, Dec 6, 2010 at 3:09 PM, Nicholas Marriott
><[1]nicholas.marri...@gmail.com> wrote:
>
> Actually I had a quick look now,
>
> Looks good, and the idea of using APC is a good one.
>
> A few things:
>
>
On Mon, Dec 6, 2010 at 3:09 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> Actually I had a quick look now,
>
> Looks good, and the idea of using APC is a good one.
>
> A few things:
>
> - I think the handshake should have the tmux version or a protocol
> version. I think the latter
Actually I had a quick look now,
Looks good, and the idea of using APC is a good one.
A few things:
- I think the handshake should have the tmux version or a protocol
version. I think the latter because the OpenBSD tmux doesn't have a
version number.
- Your list of options has some things that
Sorry, I didn't have time to look at this yet, I'll do it tomorrow
evening probably.
Cheers
On Mon, Dec 06, 2010 at 02:43:52PM -0800, George Nachman wrote:
>As a follow-up, here is the design doc:
>
> [1]https://docs.google.com/document/d/1ABI0kqUUxoAjxhWW3AsWFis6bgvMoEbcTcA2N21ncmU/edit
As a follow-up, here is the design doc:
https://docs.google.com/document/d/1ABI0kqUUxoAjxhWW3AsWFis6bgvMoEbcTcA2N21ncmU/edit?hl=en&pli=1#
Comments are welcome. I'll keep working on the second part, but I'd like to
make sure the big picture looks OK before getting into the details.
On Mon, Nov 22,
On Mon, Dec 06, 2010 at 10:05:21PM +, Nicholas Marriott wrote:
> Basically newline after every period.
OK. I *hope* I've cleaned that up enough. Patch attached.
> It means that you don't end up with a gigantic diff reflowing entire
> paragraphs if someone changes one word in a sentence.
Ma
Sure :-).
On Tue, Dec 07, 2010 at 09:12:59AM +1100, David Goodlad wrote:
>Hi all
>I use a layout similar to the built-in even-horizontal layout for the
>majority of my work: vim in the main pane on the left, and 2-3 small panes
>on the right for source control, logs, etc. Generall
Hi all
I use a layout similar to the built-in even-horizontal layout for the
majority of my work: vim in the main pane on the left, and 2-3 small panes
on the right for source control, logs, etc. Generally, I don't care about
the specific width of the main pane, only that it's as wide as possible
On Mon, Dec 06, 2010 at 09:50:23PM +, Thomas Adam wrote:
> Hi --
>
> On Mon, Dec 06, 2010 at 09:39:33PM +, Nicholas Marriott wrote:
> > I like it and looks fine apart from a couple of man page nits:
>
> OK. I am sure I can iron those out. ;)
>
> > - Each new sentence gets a new line (
Hi --
On Mon, Dec 06, 2010 at 09:39:33PM +, Nicholas Marriott wrote:
> I like it and looks fine apart from a couple of man page nits:
OK. I am sure I can iron those out. ;)
> - Each new sentence gets a new line (reduces diff size for minor
> fixes).
I don't understand what you mean here.
I like it and looks fine apart from a couple of man page nits:
- Each new sentence gets a new line (reduces diff size for minor
fixes).
- We document what * and + etc mean (look for "Denotes") so you need to
add ~.
It's dependent on another event waking us up, but that's fine because
the second
Hi all,
Please see the patch attahed which should implement "monitor-silence" and
other options, along the same lines as the monitor-activity options. I've
also included man page updates.
Feedback welcome. Any questions, just shout.
The patch is applied on top of the sourceforge CVS repository
Can I put on my style Nazi hat and have spaces around the - in "n-1"?
Otherwise looks fine. I didn't test it but I assume you did :-).
On Thu, Dec 02, 2010 at 08:52:13PM -0800, Micah Cowan wrote:
> Currently, "even-horizontal" will split a 161-column terminal into 79
> and 81, rather than 80/80
cheers, i'll try to have a look at this this week
On Sat, Dec 04, 2010 at 09:53:48AM -0500, Peter John Hartman wrote:
> Oops. What generates the crash is rather this:
>
> bind F1 join-pane -d -t 0: \; select-layout main-vertical \; display-pane
>
>
>
> On Sat, Dec 04, 2010 at 09:50:52AM -05
26 matches
Mail list logo
