Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: conflict of "exec zsh" with scp
- X-seq: zsh-users 12435
- From: Andy Spiegl <zsh.Andy@xxxxxxxxx>
- To: ZSH User List <zsh-users@xxxxxxxxxx>
- Subject: Re: conflict of "exec zsh" with scp
- Date: Wed, 16 Jan 2008 13:00:05 +0100
- In-reply-to: <080110075200.ZM9269@xxxxxxxxxxxxxxxxxxxxxx>
- Kreccount: 1
- Mail-followup-to: ZSH User List <zsh-users@xxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20080108220102.GB20640@xxxxxxxxx> <080108210151.ZM6361@xxxxxxxxxxxxxxxxxxxxxx> <080108233407.ZM6480@xxxxxxxxxxxxxxxxxxxxxx> <47841108.4020903@xxxxxxxxxxxxx> <20080109170542.GC20640@xxxxxxxxx> <080109182144.ZM7912@xxxxxxxxxxxxxxxxxxxxxx> <20080110095128.GA13970@xxxxxxxxx> <080110075200.ZM9269@xxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer wrote:
> } Putting
> } exec zsh -$- "$@"
> } into .bashrc only leads to:
> }
> } lama:~>scp admin@otherhost:/etc/passwd .
> } zsh: string expected after -c
>
> That indicates that the command passed to "sh -c ..." is not available
> to be passed along to the new shell that's exec'd. Which makes sense
> now that I think about it, because "$@" will be any additional args
> that came after the command for -c.
Uhm, I can't follow you (yet). If $@ contains the additional args, why
isn't zsh -$- "$@" enough then?
Thx,
Andy.
--
You will find that the State is the kind of organization which, while it does
big things badly, does small things badly too.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author