From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: emacs-devel@gnu.org
Subject: Re: Patch for user-emacs-directory
Date: Sun, 03 Jun 2007 01:08:44 -0400 [thread overview]
Message-ID: <E1HuiKa-0003YC-HY@fencepost.gnu.org> (raw)
In-Reply-To: <m3ira5iuqu.fsf@fleche.redhat.com> (message from Tom Tromey on Sat, 02 Jun 2007 21:26:17 -0600)
> Cc: emacs-devel@gnu.org
> From: Tom Tromey <tromey@redhat.com>
> Reply-To: tromey@redhat.com
> Date: Sat, 02 Jun 2007 21:26:17 -0600
>
> - ((file-directory-p (convert-standard-filename "~/.emacs.d/"))
> - (convert-standard-filename
> - (expand-file-name "completions" "~/.emacs.d/")))
> + ((file-directory-p user-emacs-directory)
> + (expand-file-name "completions" user-emacs-directory))
>
> I'm happy to reword this, but can you explain how this change can
> cause failures?
convert-standard-filename has a non-trivial definition on more systems
than just MS-DOS. I don't think it's right to remove it, because
doing so have a potential of letting invalid file names creep into
Emacs on those systems.
IOW, I think leaving convert-standard-filename is good engineering,
not something for which I have specific failure scenarios. In
general, we should run _all_ file names hard-wired into Emacs through
this function.
(I apologize for saying ``quite a few'' where evidently there's only
one instance of removal; in my defence I can only say that a quick
reading of the patch did somehow seem to remove
convert-standard-filename in more instances.)
next prev parent reply other threads:[~2007-06-03 5:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 21:24 Patch for user-emacs-directory Tom Tromey
2007-05-27 22:47 ` Leo
2007-05-28 14:37 ` Richard Stallman
2007-06-02 21:53 ` Tom Tromey
2007-06-03 3:09 ` Eli Zaretskii
2007-06-03 3:26 ` Tom Tromey
2007-06-03 5:08 ` Eli Zaretskii [this message]
2007-06-03 15:37 ` Tom Tromey
2007-06-03 16:47 ` Eli Zaretskii
2007-06-13 0:13 ` Chong Yidong
2007-06-13 0:02 ` Tom Tromey
2007-06-03 21:27 ` Richard Stallman
2007-06-03 22:20 ` Tom Tromey
2007-06-04 5:01 ` Richard Stallman
2007-05-30 1:32 ` Michael Olson
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=E1HuiKa-0003YC-HY@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tromey@redhat.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).