From: "João Távora" <joaotavora@gmail.com>
To: emacs-devel@gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: 900276502f..: Paul Eggert 2018-11-13 Act like POSIX sh if $HOME is relative
Date: Wed, 12 Dec 2018 12:42:30 +0000 [thread overview]
Message-ID: <jjb4lbivrux.fsf@siscog.pt> (raw)
Hi,
I've only now caught up with the discussion of bug#33255. Are the
consequences of interpreting the string "c:" on Windows as a relative
file name understood?
With HOME="z:", it used to be that (expand-file-name "~/blabla")
returned "z:/blabla" but now it returns
"z:/source/emacs/emacs/src/z:/blabla", which is not a valid Windows
pathname.
With HOME set thusly, this breaks a recent master build immediately (and
misteriously), since it can't find/create user-emacs-directory.
Notice however that (expand-file-name "z:") does return "z:/". So I
think there is an inconsistency here, even if it is true that
(file-name-absolute-p "z:") has always returned nil.
All of this can be fixed by me by setting HOME to "z:/", but
unfortunately I am breaking other applications that expected it
slash-less.
An alternative would be:
* for this part of the change to be reverted in Emacs;
* for me to set the correct environment var from the Windows shortcut
that points to runemacs.exe. Can it be done easily?
Anyway, maybe a tiny edit to the NEWS to mention this particular (and
presumably common) case could be worth it.
João Távora
next reply other threads:[~2018-12-12 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 12:42 João Távora [this message]
2018-12-12 13:19 ` 900276502f..: Paul Eggert 2018-11-13 Act like POSIX sh if $HOME is relative Yuri Khan
2018-12-12 14:54 ` João Távora
2018-12-12 15:22 ` Eli Zaretskii
2018-12-12 15:29 ` Drew Adams
2018-12-12 16:35 ` Eli Zaretskii
2018-12-12 13:28 ` Óscar Fuentes
2018-12-12 14:53 ` João Távora
2018-12-12 15:14 ` Óscar Fuentes
2018-12-12 15:28 ` João Távora
2018-12-12 16:55 ` Óscar Fuentes
2018-12-12 17:19 ` João Távora
2018-12-12 17:20 ` Eli Zaretskii
2018-12-12 15:16 ` Stefan Monnier
2018-12-12 16:30 ` Eli Zaretskii
2018-12-12 15:20 ` Eli Zaretskii
2018-12-12 15:30 ` João Távora
2018-12-12 16:35 ` Eli Zaretskii
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=jjb4lbivrux.fsf@siscog.pt \
--to=joaotavora@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.