From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: immerrr@gmail.com, npostavs@gmail.com, 33255@debbugs.gnu.org
Subject: bug#33255: 27.0.50; expand-file-name: default directory expanded twice if relative
Date: Wed, 14 Nov 2018 21:52:23 +0200 [thread overview]
Message-ID: <83va4z77yg.fsf@gnu.org> (raw)
In-Reply-To: <0c2e43c3-82ec-5783-391d-e79549c5c1db@cs.ucla.edu> (message from Paul Eggert on Wed, 14 Nov 2018 10:17:59 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 14 Nov 2018 10:17:59 -0800
> Cc: 33255@debbugs.gnu.org, immerrr again <immerrr@gmail.com>,
> Noam Postavsky <npostavs@gmail.com>
>
> > I'm a bit disappointed to see that a relative HOME is now documented
> > in the Emacs manuals, since IMO it lends legitimacy to a questionable
> > usage. I don't see it mentioned in eg the bash manual.
> > I also don't see why it is in NEWS since it is described as
> > a bug fix, and those aren't normally mentioned.
>
> My initial reaction was the same as yours, which is why my original fix
> didn't document the change in the manual or in NEWS. Eli felt otherwise,
> though.
I agree that we should discourage relative $HOME, so I added text to
the documentation to that effect.
next prev parent reply other threads:[~2018-11-14 19:52 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 [this message]
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
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=83va4z77yg.fsf@gnu.org \
--to=eliz@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).