All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] tmux new does not take tw commands
Date: Tue, 11 Jun 2013 09:28:02 -0500	[thread overview]
Message-ID: <cover.1370960556.git.peter.seebach@windriver.com> (raw)

This got routed to me because the visible error message says
	Execution of "pseudo /bin/bash" failed

but actually it's nothing to do with pseudo. The real
problem is that the tmux class in terminal.py is producing
a string like:
	'tmux new <args> {command}'

This then gets .format called on it, substituting in a command. If
the comand is "pseudo /bin/bash", this is:
	'tmux new <args> pseudo /bin/bash'
which is a usage error. It would be okay if it were:
	'tmux new <args> "pseudo /bin/bash"'

So add double quotes. Of course, that assumes that <command> never has
double quotes in it... If it does, that may need a fancier solution.

The following changes since commit b4f208f418d18f2a4e78a56bebacef481061d917:
  Saul Wold (1):
        tar: don't mv tar for nativesdk

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib seebs/tmuxfix
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/tmuxfix

Peter Seebach (1):
  handle two-word commands with tmux

 meta/lib/oe/terminal.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)



             reply	other threads:[~2013-06-11 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 14:28 Peter Seebach [this message]
2013-06-11 14:28 ` [PATCH 1/1] handle two-word commands with tmux Peter Seebach
2013-06-11 14:59 ` [PATCH 0/1] tmux new does not take tw commands Chris Larson

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=cover.1370960556.git.peter.seebach@windriver.com \
    --to=peter.seebach@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.