Jared Yanovich wrote:
> Is this a bug, or are aliases supposed to work this way?
They're supposed to work this way. Documented to work that way,
too.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Live Strong. No day but today.
Chet Ramey, ITS, CWRU[E
Is this a bug, or are aliases supposed to work this way?
[EMAIL PROTECTED] bash -version
GNU bash, version 3.00.16(1)-release (i386-redhat-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.
[EMAIL PROTECTED] alias t=test
[EMAIL PROTECTED] echo t
t
[EMAIL PROTECTED] alias echo='echo '
[EM
nkÌsð²¶mÅ·©H
http://perfect-oneday.com/6001/37dm/
[EMAIL PROTECTED]
ß¾ÅÍ èܹñB»ñÈÞBÍ{ÉsªåèAXgXÌ
ͯûðtiÈÇÅüµÄ¢Ü·B
ÅßÍ«ªjðU¢zeÖ¼s·é±Æª½¢ÌªÀÅ·B
½ß³êésðü·½ßÉAnkBÍAêñ¾j«ðlÂ
Egmont Koblinger wrote:
> However, if bash is launched as "sh", the "pwd -P" command alters $PWD to
> the resolved canonical full path name, and if the prompt contains \w, it is
> also updated to the canonical value. Example:
[...]
> Either it's a bug, or the docs forget to mention that "p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Egmont Koblinger on 11/13/2006 7:26 AM:
> Hi,
>
> According to the bash manpage and to "help pwd", "pwd -P" should only print
> something but not change the state of bash.
Unfortunately, the current wording of POSIX 2001 requires 'pwd -P
Hi,
According to the bash manpage and to "help pwd", "pwd -P" should only print
something but not change the state of bash.
However, if bash is launched as "sh", the "pwd -P" command alters $PWD to
the resolved canonical full path name, and if the prompt contains \w, it is
also updated to the can
BASH PATCH REPORT
=
Bash-Release: 3.2
Patch-ID: bash32-005
Bug-Reported-by:Stuart Shelton <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bu
BASH PATCH REPORT
=
Bash-Release: 3.2
Patch-ID: bash32-004
Bug-Reported-by:Stuart Shelton <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
Bug-Description:
A bug in the para
