From: Bart Schaefer <schaefer@brasslantern.com>
To: Vincent Lefevre <vincent@vinc17.org>, zsh-users@sunsite.dk
Subject: Re: named directory bug
Date: Thu, 1 Nov 2001 15:14:39 +0000 [thread overview]
Message-ID: <1011101151440.ZM32669@candle.brasslantern.com> (raw)
In-Reply-To: <20011031202104.A11550@greux.loria.fr>
On Oct 31, 8:21pm, Vincent Lefevre wrote:
} Subject: Re: named directory bug
}
} On Wed, Oct 31, 2001 at 15:31:24 +0000, Bart Schaefer wrote:
} > Here's a possible fix. At the least it's a workaround that you can apply in
} > the meantime.
}
} It fixes the problem, but completion with named directories no longer
} works.
Ah. Well, then, there's always this:
zmodload -i zsh/parameter &&
eval "local +h nameddirs; nameddirs=(${(@kvq)nameddirs})"
That's simulating in shell code what we'd have to write in C in order to
make saving and restoring of the nameddir table possible.
I've thought using parameters for named directories was a bad idea for a
very long time, ever since my csh-junkie hack of `chpwd () { cwd=$PWD }'
started causing `~cwd' to show up in my prompt. (Guess when autonamedirs
became an option rather than the default behavior.) At the very least I
think there should be a parameter flag for "this parameter is a nameddir"
checked by unsetparam_pm() and strsetfn() before calling adduserdir().
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-11-01 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 14:30 Vincent Lefevre
2001-10-31 15:31 ` Bart Schaefer
2001-10-31 19:21 ` Vincent Lefevre
2001-11-01 15:14 ` Bart Schaefer [this message]
2001-11-01 16:39 ` Vincent Lefevre
2001-11-01 17:43 ` Bart Schaefer
2001-11-01 18:35 ` Vincent Lefevre
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=1011101151440.ZM32669@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=vincent@vinc17.org \
--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).