I reckon we always set PATH and yes pass it into the func. Behaviour will only
change if someone sets PATH in global or session environment themselves.
-------- Original message --------
From: J Raynor <jxray...@gmail.com>
Date: 13/02/2014 16:20 (GMT+00:00)
To: Nicholas Marriott <nicholas.marri...@gmail.com>
Cc: tmux-users@lists.sourceforge.net
Subject: Re: use "--" to mark start of command w/ neww etc to avoid quoting
> - If we are going to call execvp we should control PATH, I think we
> should probably get it from the client if it's a command line client
> else from the session environ. In any case you'll need to pass it in
> from the caller as yet another argument.
Tmux currently runs commands by calling 'shell -c "command -arg1
-arg2"', and this ends up calling some form of exec which pays
attention to PATH. But tmux doesn't change the PATH depending on
whether it's a command line client. So doing that now would be a
change in behavior. Also, if tmux only alters PATH when execvp is
called directly, then these 2 commands could behave differently:
tmux neww "command -arg1 -arg2"
tmux neww command -arg1 -arg2
With that in mind:
1. Should PATH still be passed into window_pane_spawn?
2. If so, should it only apply when execvp is called directly? Or
should it also apply when "shell -c" is forked off?
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
