zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Cc: aaron@schrab.com
Subject: PATCH 1/2: _tmux: redirect error output when no server is running
Date: Mon, 26 Mar 2012 18:18:16 +0200	[thread overview]
Message-ID: <CAHYJk3REAR95fC67Jgfe7TdK-ch=EegXJynHMt_6kJNjvy3-6Q@mail.gmail.com> (raw)
In-Reply-To: <20120326161510.GA2115@pug.qqx.org>

---------- Forwarded message ----------
From: Aaron Schrab <aaron@schrab.com>
Date: 26 March 2012 18:15
Subject: Re: PATCH 1/2: _tmux: redirect error output when no server is running
To: Mikael Magnusson <mikachu@gmail.com>


At 11:18 +0100 24 Mar 2012, Mikael Magnusson <mikachu@gmail.com> wrote:
>
> -    buffers=( ${${(f)"$(command tmux list-buffers "${bopts[@]}")"}/:[ >$'\t']##/:} )
> +    buffers=( ${${(f)"$(command tmux 2> /dev/null list-buffers "${bopts[@]}")"}/:[ $'\t']##/:} )


Unfortunately this can cause problems.  In my experience directing
tmux's STDERR do /dev/null causes that invocation to hang on Linux
apparently due to a bug in the epoll implementation.  This can be
worked around by setting EVENT_NOEPOLL environment variable to 1
before starting the server, but if tmux is using a version of libevent
before 2.0 (which is quite common) that will occasionally cause the
tmux server to die.

There's a thread about this on the tmux-users mailing list:

http://sourceforge.net/mailarchive/message.php?msg_id=28004727


      parent reply	other threads:[~2012-03-26 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 10:18 Mikael Magnusson
2012-03-24 10:18 ` PATCH 2/2: _tmux: Complete also for unambiguous prefixes Mikael Magnusson
     [not found] ` <20120326161510.GA2115@pug.qqx.org>
2012-03-26 16:18   ` Mikael Magnusson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHYJk3REAR95fC67Jgfe7TdK-ch=EegXJynHMt_6kJNjvy3-6Q@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=aaron@schrab.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).