From: Eli Zaretskii <eliz@gnu.org>
To: Yilkal Argaw <yilkalargawworkneh@gmail.com>
Cc: rtt@dasyatidae.com, emacs-devel@gnu.org
Subject: Re: missing "/" in value of user-emacs-directory when using --init-directory flag
Date: Mon, 12 Dec 2022 14:23:55 +0200 [thread overview]
Message-ID: <83mt7sstd0.fsf@gnu.org> (raw)
In-Reply-To: <CAJddU=oBe7Z9JgHGM7YE0tf1rp95Pvua7+t2CKTo9-Ddz1JcUA@mail.gmail.com> (message from Yilkal Argaw on Mon, 12 Dec 2022 03:41:17 +0000)
> From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> Date: Mon, 12 Dec 2022 03:41:17 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> While that's as may be in general, the docstring for user-emacs-directory
> (in my Emacs 28.2) states "Note that this should end with a directory
> separator." specifically, which I take to be part of the variable contract.
> Doesn't that imply that it is Emacs's responsibility to handle that aspect
> if setting user-emacs-directory based on a file name that may not satisfy
> that predicate?
>
> -RTT
>
> Correct. consistency and standardization on such matters is better for overall user experience.
The issue was fixed more than a week ago, so I'm unsure what is the
purpose of this post. We are consistent.
next prev parent reply other threads:[~2022-12-12 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 17:55 missing "/" in value of user-emacs-directory when using --init-directory flag Yilkal Argaw
2022-11-29 18:11 ` Yilkal Argaw
2022-11-29 18:20 ` Eli Zaretskii
2022-11-29 18:56 ` [External] : " Drew Adams
2022-11-29 19:01 ` Greg Farough
2022-11-29 20:08 ` Stefan Monnier
2022-11-29 20:58 ` Greg Farough
2022-11-29 21:54 ` Juanma Barranquero
2022-11-29 23:04 ` Drew Adams
2022-11-29 23:02 ` Drew Adams
2022-12-02 22:47 ` Richard Stallman
2022-12-03 6:47 ` Yuri Khan
2022-12-02 13:20 ` Robin Tarsiger
2022-12-12 3:41 ` Yilkal Argaw
2022-12-12 12:23 ` Eli Zaretskii [this message]
2022-12-12 18:04 ` Yilkal Argaw
2022-12-12 18:13 ` 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
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=83mt7sstd0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rtt@dasyatidae.com \
--cc=yilkalargawworkneh@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).