On Fri, Nov 29, 2013 at 21:25:39 -0500, Ben Boeckel wrote:
> I don't think block-until-there's-a-reader is possible (I think SIGPIPE
> is tossed into the mix right away).
Actually, the comment in uzbl is:
/* We don't really need to write to the file, but if we open the file as
* 'r' we w
On Fri, Nov 29, 2013 at 21:21:41 -0500, Timothy Brown wrote:
> You have it right. Perhaps the current behavior is the intended
> behavior; but what i’d like is for save-buffer to write to the fifo
> but either show an error message (“no readers” or the like) or block,
> in the worst case, until I
You have it right. Perhaps the current behavior is the intended behavior; but
what i’d like is for save-buffer to write to the fifo but either show an error
message (“no readers” or the like) or block, in the worst case, until I read
from the fifo. I haven’t taken a deep look yet, but i’m gue
On Thu, 28 Nov, 2013 at 14:23:39 GMT, Nicholas Marriott wrote:
> I don't know why it doesn't work, give me a set of commands to test?
Would it fail if the pipe has no readers when tmux writes to it?
--Ben
--
Rapidly tro
start-server does not create any sessions and servers do not stay around
without sessions. It has always been this way. If you want to use
start-server, create a session in .tmux.conf.
On Fri, Nov 29, 2013 at 03:29:57AM +, Von Welch wrote:
>---
Just found a problem: sourcing the tmux configuration expands the
environment variables, too, and I don't see any way that allows
escaping. That means ':new-window -c "$PWD"' on the prompt works but
binding the same will resolve $PWD when parsing the config, not when
pressing the keys. Any recommen
---
** [tickets:#84] start-server broken in 1.8?**
**Status:** open
**Created:** Fri Nov 29, 2013 03:29 AM UTC by Von Welch
**Last Updated:** Fri Nov 29, 2013 03:29 AM UTC
**Owner:** nobody
Seems like a tmux server started with 'tmux start-server' immediately exits. (I
thought this worked in
