Cool. Applied to OpeNBSD, thanks, should be in SF soonish.
On Wed, Aug 24, 2011 at 12:33:45PM +0200, Julius Plenz wrote:
> Hi, Nicholas!
>
> * Nicholas Marriott [2011-08-24 11:54]:
> > problem: if we have a blank line then len will be 0 (after trimming
> > the \n) so the continuation check wil
Hi, Nicholas!
* Nicholas Marriott [2011-08-24 11:54]:
> problem: if we have a blank line then len will be 0 (after trimming
> the \n) so the continuation check will read before the start of the
> buffer.
True.
> I've tweaked this a bit and hopefully fixed that, please look at this:
Yes, the am
Ok problem: if we have a blank line then len will be 0 (after trimming
the \n) so the continuation check will read before the start of the
buffer.
I've tweaked this a bit and hopefully fixed that, please look at this:
Index: cfg.c
==
Hi, Nicholas!
* Nicholas Marriott [2011-08-20 22:51]:
> I think if possible the unfinished command thing should not be
> log_warnx but should an error and be added to the causes.
Right. Also, I fixed a small memory leak.
> Also this needs to go somewhere in the manpage.
I added two examples in
Hi
I think if possible the unfinished command thing should not be log_warnx
but should an error and be added to the causes.
Also this needs to go somewhere in the manpage.
Cheers
On Fri, Aug 12, 2011 at 04:00:17PM +0200, Julius Plenz wrote:
> Hi!
>
> Since tmux supports chaining commands via
Hi!
Since tmux supports chaining commands via \; already, I find it a pity
tmux cannot handle any sort of line continuation as far as I can see.
The patch below implements this feature: lines ending with a single
backslash will trigger the next line to be read in also. Thus, it's
possible to spli
