On 9/19/21 6:22 PM, william wrote:
Do you know why command is necessary for it to recognize the option?
Without 'command', you're using the builtin shell command rather than
coreutils pwd.
Closing the bug report, as this isn't a coreutils bug.
That does the trick. Do you know why command is necessary for it to recognize
the option?
On 21/09/19 06:05PM, L A Walsh wrote:
> Try 'command pwd --version'
>
> On 2021/09/19 16:09, william wrote:
> > coreutils version 8.32
> >
> > The commands
> >
> > pwd --version
> >
> > and
> >
> >
Try 'command pwd --version'
On 2021/09/19 16:09, william wrote:
coreutils version 8.32
The commands
pwd --version
and
pwd --help
return
pwd: bad option: -v
pwd: bad option: -h
coreutils version 8.32
The commands
pwd --version
and
pwd --help
return
pwd: bad option: -v
pwd: bad option: -h
tag 34447 + notabug
close 34447
thanks
Hello Chris,
Chris Wright wrote:
> I found that if a session's working directory is renamed or moved,
> `pwd` doesn't show the real working directory.
Thank you for your bug report. However I think the shell's built-in
pwd is being confused with the
Hi,
I found that if a session's working directory is renamed or moved, `pwd`
doesn't show the real working directory.
Example:
Session 1:
```
~/ $ mkdir test
~/ $ cd test
~/test $ touch file
```
Session 2:
```
~/ $ mv test test_2
~/ $ mkdir test
~/ $ cd test
~/ $ touch file2
~/ $ ls
file2
On 05/31/2015 04:35 AM, Bob Proulx wrote:
Bernhard Voelker wrote:
First of all, I want to mention that the invoked 'pwd' is a builtin
in most shells, which means you have to e.g. specify the path like
/bin/pwd to be sure to invoke the coreutils version of it.
A very, very small comment.
Bernhard Voelker wrote:
First of all, I want to mention that the invoked 'pwd' is a builtin
in most shells, which means you have to e.g. specify the path like
/bin/pwd to be sure to invoke the coreutils version of it.
A very, very small comment. This is all true but the wording makes it
sound
tag 20679 notabug
close 20679
stop
On 05/28/2015 06:08 AM, 徐兴旺 wrote:
If the name of current diretory including blank, pwd return raw blank istead of escaping
character, \ .
When used with cp command, the directory name will be recognized two params.
If I understand correctly, then you have
If the name of current diretory including blank, pwd return raw blank
istead of escaping character, \ .
When used with cp command, the directory name will be recognized two params.
-coreutils@gnu.org
Sent: Friday, April 28, 2006 11:54 PM
Subject: Re: Some bug in 'pwd' command
Hello,
When the parent directory name contains {} pwd fails to detect
location.
For example:
[EMAIL PROTECTED] ~/tmp]$ cd /home/olgag/tmp/test\ bug\ [EMAIL PROTECTED
Hello,
When the parent directory name contains {} pwd fails to detect location.
For example:
[EMAIL PROTECTED] ~/tmp]$ cd /home/olgag/tmp/test\ bug\ [EMAIL PROTECTED]
#\$%^\\*\(\)_+\|}\{\[]\ \:\?\\/conserver-8.1.14
[EMAIL PROTECTED] conserver-8.1.14]$ pwd
Missing }.
Best Regards,
Olga
Hello,
When the parent directory name contains {} pwd fails to detect location.
For example:
[EMAIL PROTECTED] ~/tmp]$ cd /home/olgag/tmp/test\ bug\ [EMAIL PROTECTED]
#\$%^\\*\(\)_+\|}\{\[]\ \:\?\\/conserver-8.1.14
[EMAIL PROTECTED] conserver-8.1.14]$ pwd
Missing }.
Thanks for the
here. Please refer to your shell's documentation
for details about the options it supports.
Basically just a pointer. But what else is there to say?
Re your question: I got the version number from the man page for pwd. It
said it was GNU pwd and gave bug-coreutils@gnu.org as the contact
Hi,
I am running Mandrake Linux 9.2, the version of pwd is
pwd 5.0 March 2003
I found the following behaviour (running as root at the command line)
[EMAIL PROTECTED] linux32]# pwd
/usr/local/lindoapi/bin/linux32
[EMAIL PROTECTED] linux32]# mv ../../../lindoapi ../../../lindoapi3.0
[EMAIL
On Wed, Feb 16, 2005 at 06:47:26AM -0700, Eric Blake wrote:
Furthermore, POSIX requires that when -P is specified, that $PWD be
updated in the calling environment to scrub all symlinks from the
environment variable that were previously set by a `cd -L' command. I see
no possible way to
Eric Blake [EMAIL PROTECTED] wrote:
POSIX now requires pwd(1) to support -L and -P, that -L is the default,
and that -L reads $PWD to verify that it is a name (possibly with symbolic
links) of the current directory. Coreutils pwd currently implements none
of this, and behaves as though -P is
17 matches
Mail list logo
