On Wed, Dec 15, 2010 at 03:19:45PM -0500, Lars Kellogg-Stedman wrote:
> > Someone suggested treating the rest of the command line as one argument
> > if -- is encountered, I'd be happy with that.
>
> Why require "--"? Looking at the man page:
>
> new-window [-adk] [-n window-name] [-t target-w
> Someone suggested treating the rest of the command line as one argument
> if -- is encountered, I'd be happy with that.
Why require "--"? Looking at the man page:
new-window [-adk] [-n window-name] [-t target-window] [shell-command]
...why is it necessary to terminate the arguments with "--
On Wed, Dec 15, 2010 at 02:44:56PM -0500, Lars Kellogg-Stedman wrote:
> > What shell are you using?
>
> Bash.
>
> > In ksh, if I type:
> >
> > tmux neww 'emacs /usr/s
>
> That's questionable behavior, because how would it handle filenames
> containing spaces?
You have to intervene and ed
> What shell are you using?
Bash.
> In ksh, if I type:
>
> tmux neww 'emacs /usr/s
That's questionable behavior, because how would it handle filenames
containing spaces?
> An alternative would be to write a little shell function to translate:
>
> tmux_neww() {
> tmux neww "$*"
> }
Hi
What shell are you using?
In ksh, if I type:
tmux neww 'emacs /usr/s
It completes it just fine.
An alternative would be to write a little shell function to translate:
tmux_neww() {
tmux neww "$*"
}
On Wed, Dec 15, 2010 at 11:57:36AM -0500, Lars Kellogg-Stedman wrote:
> Af
