unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
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 14:08:08 -0500	[thread overview]
Message-ID: <kpmuq3musn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <0c2e43c3-82ec-5783-391d-e79549c5c1db@cs.ucla.edu> (Paul Eggert's message of "Wed, 14 Nov 2018 10:17:59 -0800")

Paul Eggert wrote:

> On 11/14/18 10:10 AM, Glenn Morris wrote:
>> Can you point me to the citation for that please
>
> 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".

There are no matches for "relative" on that page.
There are three for "absolute". One is for ENV, and says that the
results are unspecified if it is not absolute. The other two are for
PWD, and say that it must be absolute.

What am I missing?
Just that the section on ~ expansion says nothing one way or the other?
I was really looking for a reference about HOME.






  parent reply	other threads:[~2018-11-20 19:08 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 [this message]
2018-11-20 20:44         ` Paul Eggert
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=kpmuq3musn.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33255@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=immerrr@gmail.com \
    --cc=npostavs@gmail.com \
    /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).