On Sat, Feb 9, 2013 at 11:27 AM, Carsten Mattner <carstenmattner@gmail.com> wrote:
> I'm not exactly sure what you're asking, but shellPrompt uses "spawn" so
> should not have issues with extra arguments.  I do see an issue where
> completion would break if an executable has a space in its name, but that
> shouldn't affect running it if you have your quoting correct.

Unsuccessfully tried the following
"xterm -e mc"
"/usr/bin/xterm -e mc"
'xterm -e mc'
'/usr/bin/xterm -e mc'

That wasn't what I was talking about, and you should probably forget I mentioned it since you're only likely to see the case I was talking about on OS X.  All of the above *will* fail:  there is no executable called "/usr/bin/xterm -e mc" with spaces in the actual filename, hopefully.

Could you show your actual code?

--
brandon s allbery kf8nh                               sine nomine associates
allbery.b@gmail.com                                  ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net