all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 33255@debbugs.gnu.org, eggert@cs.ucla.edu, immerrr@gmail.com,
	npostavs@gmail.com
Subject: bug#33255: 27.0.50; expand-file-name: default directory expanded twice if relative
Date: Tue, 20 Nov 2018 21:26:32 +0200	[thread overview]
Message-ID: <83d0qzim8n.fsf@gnu.org> (raw)
In-Reply-To: <crin0rmunv.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 20 Nov 2018 14:11:00 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>,  33255@debbugs.gnu.org,  immerrr@gmail.com,  npostavs@gmail.com
> Date: Tue, 20 Nov 2018 14:11:00 -0500
> 
> Eli Zaretskii wrote:
> 
> > I agree that we should discourage relative $HOME, so I added text to
> > the documentation to that effect.
> 
> I really think it would be better not to mention it at all.

Sorry, I disagree.  We should not hide from the users what Emacs does
in such corner cases.  Hiding won't work anyway, because someone
determined enough will find out by reading the code.  We just punish
those who aren't determined enough.





  reply	other threads:[~2018-11-20 19:26 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83d0qzim8n.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 \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.