From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58080@debbugs.gnu.org, Jonas Bernoulli <jonas@bernoul.li>
Subject: bug#58080: 29.0.50; Don't hard-code path to pwd
Date: Mon, 26 Sep 2022 08:19:52 +0000 [thread overview]
Message-ID: <0f4ca4f331889b63bc26@heytings.org> (raw)
In-Reply-To: <83fsgelg2v.fsf@gnu.org>
>
> I don't see anything like PWDCMD in any of the GNU projects I have here,
> but they do use just "pwd", not "/bin/pwd". So maybe so should we, and
> that would solve this particular problem as well?
>
The difference is that /bin/pwd gives, unlike pwd, the "true" path
(without symlinks). Not sure if it's important enough to justify the use
of /bin/pwd, though. The use of /bin/pwd instead of pwd dates from
8672a560f6 by RMS in 1994.
next prev parent reply other threads:[~2022-09-26 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 19:09 bug#58080: 29.0.50; Don't hard-code path to pwd Jonas Bernoulli
2022-09-26 8:01 ` Eli Zaretskii
2022-09-26 8:19 ` Gregory Heytings [this message]
2022-09-26 8:34 ` Andreas Schwab
2022-09-26 10:59 ` Gregory Heytings
2022-09-26 13:02 ` Gregory Heytings
2022-09-26 20:10 ` Jonas Bernoulli
2022-09-26 20:33 ` Gregory Heytings
2022-09-28 14:31 ` Gregory Heytings
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f4ca4f331889b63bc26@heytings.org \
--to=gregory@heytings.org \
--cc=58080@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jonas@bernoul.li \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).