From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 33255@debbugs.gnu.org, immerrr again <immerrr@gmail.com>,
Noam Postavsky <npostavs@gmail.com>
Subject: bug#33255: 27.0.50; expand-file-name: default directory expanded twice if relative
Date: Tue, 20 Nov 2018 12:44:25 -0800 [thread overview]
Message-ID: <106aab5d-7910-3021-03a1-e4e5d910d831@cs.ucla.edu> (raw)
In-Reply-To: <kpmuq3musn.fsf@fencepost.gnu.org>
On 11/20/18 11:08 AM, Glenn Morris wrote:
>> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_01
> I had looked at that page before. Looking again, I still don't see
> anything as clear-cut as "POSIX says that sh treats ~/foo like $HOME/foo
> even when HOME is not absolute".
It needs to be read in context. Section 2.6.1 is about tilde expansion
in the shell, e.g., how to treat commands like this:
cd ~eggert/xxx
cd ~/yyy
2.6.1 says "If the login name is null (that is, the tilde-prefix
contains only the tilde), the tilde-prefix is replaced by the value of
the variable /HOME."/ This is talking about the second "echo" example
which uses a null login name, and it means that the second example is
treated like this:
cd "$HOME"/yyy/
/
(The quotes are because of the last sentence in that section of the
spec.) This occurs regardless of whether $HOME starts with /"/".//
/
next prev parent reply other threads:[~2018-11-20 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 10:54 bug#33255: 27.0.50; expand-file-name: default directory expanded twice if relative immerrr again
2018-11-04 12:27 ` Noam Postavsky
2018-11-05 0:58 ` Glenn Morris
2018-11-13 18:26 ` Paul Eggert
2018-11-13 20:12 ` Eli Zaretskii
2018-11-14 18:10 ` Glenn Morris
2018-11-14 18:17 ` Paul Eggert
2018-11-14 19:52 ` Eli Zaretskii
2018-11-20 19:11 ` Glenn Morris
2018-11-20 19:26 ` Eli Zaretskii
2018-11-20 19:08 ` Glenn Morris
2018-11-20 20:44 ` Paul Eggert [this message]
2018-11-22 18:25 ` Glenn Morris
2018-11-23 20:22 ` Paul Eggert
2018-11-27 5:42 ` Glenn Morris
2018-11-27 18:11 ` Paul Eggert
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=106aab5d-7910-3021-03a1-e4e5d910d831@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33255@debbugs.gnu.org \
--cc=immerrr@gmail.com \
--cc=npostavs@gmail.com \
--cc=rgm@gnu.org \
/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).