From: "Drew Adams" <drew.adams@oracle.com>
To: <herring@lanl.gov>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: file-truename, convert-standard-filename
Date: Fri, 26 Feb 2010 12:25:46 -0800 [thread overview]
Message-ID: <09E64B6E926E4DE4A43455E1E94EBFCF@us.oracle.com> (raw)
In-Reply-To: <50265.130.55.132.103.1267212903.squirrel@webmail.lanl.gov>
> > If my code gets a file name from the user, and I can't depend on it
> > being valid for the given platform... Seems to me this would be
> > similar to the literal-file-name-string-in-code situation.
>
> ...
> The error message that Emacs receives from the system in case of an
> invalid file name might be unhelpful (not tell the user what was wrong
> with their filename). Nonetheless, transparently changing
> (on Windows) a user's value of "really?" to "really_" (or whatever)
> is Not The Right Thing.
;-)
I was thinking more of a defcustom value entered by a user (not a default
defcustom value). Seems like that could be problematic in the same way a literal
string might be.
But the bottom line in practical terms wrt `c-s-f' still seems to be: YAGNI.
As Stefan said, `c-s-f' is needed "where it would be a bug if that file name
turned out to be invalid on the current system", as opposed to situations where
an error will be raised if the name is invalid.
next prev parent reply other threads:[~2010-02-26 20:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 17:31 file-truename, convert-standard-filename Drew Adams
2010-02-05 18:15 ` Andreas Schwab
2010-02-05 18:33 ` Lennart Borgman
2010-02-05 19:45 ` Andreas Schwab
2010-02-05 19:49 ` Lennart Borgman
2010-02-05 20:14 ` Stefan Monnier
2010-02-05 20:18 ` Lennart Borgman
2010-02-06 1:10 ` Miles Bader
2010-02-05 23:51 ` Drew Adams
2010-02-05 19:04 ` Eli Zaretskii
2010-02-05 23:51 ` Drew Adams
2010-02-06 0:17 ` Lennart Borgman
2010-02-06 8:45 ` Eli Zaretskii
2010-02-06 16:55 ` Lennart Borgman
2010-02-06 19:12 ` Eli Zaretskii
2010-02-06 19:20 ` Lennart Borgman
2010-02-06 9:01 ` Eli Zaretskii
2010-02-06 15:33 ` Drew Adams
2010-02-06 19:33 ` Eli Zaretskii
2010-02-06 20:46 ` Drew Adams
2010-02-06 21:58 ` Eli Zaretskii
2010-02-06 23:12 ` Drew Adams
2010-02-07 4:01 ` Eli Zaretskii
2010-02-08 1:38 ` Stefan Monnier
2010-02-08 2:46 ` Drew Adams
2010-02-26 18:33 ` Davis Herring
2010-02-26 19:12 ` Drew Adams
2010-02-26 19:35 ` Davis Herring
2010-02-26 20:25 ` Drew Adams [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-06 3:52 MON KEY
2010-02-06 8:28 ` Eli Zaretskii
[not found] ` <d2afcfda1002061814nc3e178fl5d93e21ea6bae7b5@mail.gmail.com>
2010-02-07 2:16 ` MON KEY
[not found] ` <83wrypelms.fsf@gnu.org>
2010-02-07 23:26 ` MON KEY
2010-02-08 0:28 ` Andreas Schwab
2010-02-08 4:10 ` Eli Zaretskii
[not found] ` <d2afcfda1002091330y53017b24w5e6bdf3c3d131a97@mail.gmail.com>
2010-02-09 21:32 ` MON KEY
2010-02-09 21:59 ` Andreas Schwab
2010-02-09 22:32 ` 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=09E64B6E926E4DE4A43455E1E94EBFCF@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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).