zsh-users
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh-users@sunsite.dk
Subject: Re: retrieving invocation arguments
Date: Tue, 18 Sep 2001 12:39:09 +0100	[thread overview]
Message-ID: <20010918123909.C6902@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1010917161307.ZM5925@candle.brasslantern.com>; from schaefer@brasslantern.com on Mon, Sep 17, 2001 at 04:13:07PM +0000

Bart Schaefer (schaefer@brasslantern.com) wrote:
> On Sep 17, 11:23am, Adam Spiers wrote:
> }
> } Currently I have
> } 
> }   restart () {
> }       exec $SHELL "$SHELL_ARGS" "$@"
> }   }
> } 
> } and I do
> } 
> }   export SHELL_ARGS="$@"
> } 
> } in my ~/.switch_shell (run from bash).
> 
> Ah.  Well, "$@" doesn't include the option switches even in bash

That's OK, that "$@" refers to the arguments passed to .switch_shell,
which are hard-coded in my .bashrc rather than being those bash was
invoked with.

> Also, "$SHELL_ARGS" is going to be one argument where the original "$@"
> may have had several.
> 
> And I should repeat the warning about `export SHELL_ARGS="$@"' -- "$@"
> is an array with each element quoted, so what you've really written is
> 
>     export SHELL_ARGS="$1" "$2" "$3" ...
> 
> which is probably not what you meant.  Using "$@" works in bash because it
> treats the arguments to `export' as if they were assignment expressions;
> but in zsh that requires `setopt kshtypeset' (4.0.2 and later).

Yes, I was aware of that problem, although I guess what I actually
meant to write was

  export SHELL_ARGS="$*"

which should be a bit better, but still not ideal.  Anyhow,
dissatisfaction with this whole approach was the main reason for
asking the original question.

> Anyway, it's very difficult to restart the shell exactly as it was invoked
> unless you stash the arguments very early in .zshenv and have a cooperative
> /etc/zshenv.

I don't (and won't) have a cooperative /etc/zshenv, which is why it
would be nice if zsh itself made the information easily retrievable,
if it wouldn't be hard to implement cleanly.

> And now that's probably more glorious detail than I should have included.

:-)


      reply	other threads:[~2001-09-18 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 20:42 Adam Spiers
2001-09-15 17:34 ` Bart Schaefer
2001-09-17 10:02   ` Sweth Chandramouli
2001-09-17 11:07     ` Peter Stephenson
2001-09-17 15:17       ` Bart Schaefer
2001-09-17 15:38         ` Peter Stephenson
2001-09-17 16:06           ` Bart Schaefer
2001-09-17 20:59           ` Adam Spiers
2001-09-17 20:25             ` Sweth Chandramouli
2001-09-18 10:53               ` Adam Spiers
2001-09-17 10:23   ` Adam Spiers
2001-09-17 16:13     ` Bart Schaefer
2001-09-18 11:39       ` Adam Spiers [this message]

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=20010918123909.C6902@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).