From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: Re: Strange prompting in new 3.1.5
Date: Wed, 4 Nov 1998 08:21:50 -0800 [thread overview]
Message-ID: <981104082150.ZM20973@candle.brasslantern.com> (raw)
In-Reply-To: <19981104124433.A9660@petzval.math.fu-berlin.de>
In-Reply-To: <vb1znju0kf.fsf@snake.isode.com>
In-Reply-To: <9811041226.AA32302@ibmth.df.unipi.it>
On Nov 4, 12:44pm, Stucki wrote:
} Subject: Strange prompting in new 3.1.5
}
} I installed the new Version 3.1.5 and since then my
} (unchanged) 'prompt' always showed '~PWD' where '%~'
} is expanded.
This changed because PWD was "special" before 3.1.5, but became an
ordinary parameter in 3.1.5. When it was "special" it never got
added to the named directory hash table.
On Nov 4, 1:26pm, Peter Stephenson wrote:
} Subject: PATCH: Re: Strange prompting in new 3.1.5
}
} "Zefram" wrote:
} > Basically, AUTO_NAME_DIRS is a really bad idea if you want to do
} > %~ expansion. Think about it: ~PWD is always a correct name for the
} > directory you're in. It's just not useful. Even if we make an exception
} > for PWD, there's nothing stopping other parameters being equally unhelpful
} > (OLDPWD, and anything the user uses in the chpwd function).
}
} But %~ doesn't use OLDPWD and users can make arrangments for their own
} variables, whereas PWD is set by the shell and it's up to the shell to
} make it useful. I don't think it's good enough simply saying %~ and
} autonamedirs are incompatible; that's the shell's fault, not the
} user's.
I have to agree with Peter here. The shell shouldn't be screwing up its
own features.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1998-11-04 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-04 11:44 Stucki
1998-11-04 12:03 ` Bruce Stephens
1998-11-04 12:27 ` Zefram
1998-11-04 12:26 ` PATCH: " Peter Stephenson
1998-11-04 16:21 ` Bart Schaefer [this message]
1998-11-10 10:19 ` PATCH: 3.1.5: alternative PWD patch Peter Stephenson
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=981104082150.ZM20973@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/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).