From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7617@debbugs.gnu.org
Subject: bug#7617: 24.0.50; `expand-file-name': removal of slashes
Date: Sun, 12 Dec 2010 21:33:32 +0200 [thread overview]
Message-ID: <83k4jeu6pf.fsf@gnu.org> (raw)
In-Reply-To: <022D0B344DB64B2A9E1B771B0695237E@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <7617@debbugs.gnu.org>
> Date: Sun, 12 Dec 2010 10:03:08 -0800
>
> > Please explain why you consider this a bug. foo//bar is at best
> > equivalent to foo/bar,
>
> In what way is that _ever_ equivalent? Please show the equivalence for any of
> the OS's that Emacs supports.
On Unix and GNU/Linux -- always, in the sense that file-related system
calls will treat them the same. On Windows -- sometimes, depending on
the implementation of the standard C library.
> In interactive use, `...//abc...' is treated as just `/abc...' by Emacs. The
> prefix `.../' is ignored until you hit `RET'. And then the prefix is dropped
> when you enter the file name (`RET') - but only then. And that's appropriate.
> Other than when you actually hit `RET', the prefix should not be removed but
> simply ignored.
That's right, but I was talking about non-interactive uses. I believe
in interactive use, Emacs still does what you (and I) expect.
> Then please create a separate primitive the does just that.
Feel free to file a separate feature request for that.
> Currently, there is no way to maintain the integrity of the user's input if that
> input is passed through `expand-file-name' to do what the doc says `expand*'
> does.
If all you need is ignore everything before the double slash, there
are easier ways than asking to change a primitive.
next prev parent reply other threads:[~2010-12-12 19:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 21:53 bug#7617: 24.0.50; `expand-file-name': removal of slashes Drew Adams
2010-12-12 15:58 ` Eli Zaretskii
2010-12-12 18:03 ` Drew Adams
2010-12-12 19:33 ` Eli Zaretskii [this message]
2010-12-12 20:21 ` Drew Adams
2010-12-12 20:32 ` Eli Zaretskii
2010-12-12 20:36 ` Drew Adams
2010-12-12 20:42 ` Andreas Schwab
2010-12-13 3:53 ` Stefan Monnier
2010-12-13 4:32 ` Drew Adams
2010-12-13 5:23 ` Eli Zaretskii
2010-12-13 14:51 ` Drew Adams
2010-12-13 15:17 ` Eli Zaretskii
2010-12-13 15:47 ` Drew Adams
2010-12-13 16:17 ` Eli Zaretskii
2010-12-13 20:40 ` Stefan Monnier
2010-12-12 22:35 ` Drew Adams
2010-12-12 23:40 ` Andreas Schwab
2010-12-13 5:17 ` Eli Zaretskii
2010-12-13 14:51 ` Drew Adams
2010-12-12 20:15 ` Andreas Schwab
2010-12-12 20:25 ` Drew Adams
2010-12-12 20:36 ` Andreas Schwab
2010-12-12 20:42 ` Drew Adams
2010-12-12 21:00 ` Andreas Schwab
2010-12-13 0:49 ` Jason Rumney
2010-12-12 20:39 ` Eli Zaretskii
2010-12-12 21:04 ` Andreas Schwab
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=83k4jeu6pf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7617@debbugs.gnu.org \
--cc=drew.adams@oracle.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).