all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33255@debbugs.gnu.org, immerrr again <immerrr@gmail.com>
Subject: bug#33255: 27.0.50; expand-file-name: default directory expanded twice if relative
Date: Sun, 04 Nov 2018 19:58:01 -0500	[thread overview]
Message-ID: <3336sg2vdy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <878t29hvta.fsf@gmail.com> (Noam Postavsky's message of "Sun, 04 Nov 2018 07:27:29 -0500")

Noam Postavsky wrote:

> immerrr again <immerrr@gmail.com> writes:
>
>> I have recently tried to play with a clean .emacs.d directory by setting
>> HOME=clean/home/dir,

I think a non-absolute HOME is a user error.
Eg cd $HOME may then not be idempotent.
I would use $PWD/clean/home/dir.

> I think it would make sense for Emacs to expand HOME against the current
> directory when it starts up, if HOME is relative.  

I would rather see Emacs abort with an error.
Otherwise you have to eg fix up process-environment too, else child
processes may behave oddly.





  reply	other threads:[~2018-11-05  0:58 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 [this message]
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
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=3336sg2vdy.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33255@debbugs.gnu.org \
    --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 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.