From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: [zsh 4.0.1-pre-2 bug] named directories disappear
Date: Tue, 3 Apr 2001 10:16:36 +0200 (MET DST) [thread overview]
Message-ID: <200104030816.KAA12908@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 2 Apr 2001 17:01:53 +0000
[ moved to -workers ]
Bart Schaefer wrote:
> On Apr 2, 4:48pm, Vincent Lefevre wrote:
> } Subject: [zsh 4.0.1-pre-2 bug] named directories disappear
> }
> } The named directory ~out was defined, but it has disappeared:
> }
> } greux:~> echo ~out
> } zsh: no such user or named directory: out
>
> bug () {
> hash -d out=$HOME
> echo ~out
> local out
> out=(oops)
> ( echo ~out )
> : Without the subshell above, this line is never reached
> }
>
> The local variable "out" is used by _pids, so that named directory will be
> stomped whenever you complete process IDs.
>
> On the other hand, if you actually set the global variable "out":
>
> unbug () {
> out=$HOME
> bug
> echo ~out
> }
>
> The named directory still gets stomped, but is automatically restored any
> time you refer to it.
That's caused by adduserdir() in utils.c. The test in utils.c:533
succeeds when the local variable is set and then the namedir-entry is
removed.
I'm not sure how we should solve this. Maybe just make `hash -d x=...'
set the parameter `x', too? Once one has done the above, one can't
set $x anymore anyway.
Or maybe the other way round? Use a flag in nameddirtab entries that
says that the entry was added with `hash -d ...' and don't change or
remove such entries when the corresponding parameter is modified?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2001-04-03 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 8:16 Sven Wischnowsky [this message]
2001-04-04 5:11 ` Bart Schaefer
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=200104030816.KAA12908@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@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).