From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26911@debbugs.gnu.org, mattiase@acm.org, michael.albinus@gmx.de,
yegortimoshenko@gmail.com
Subject: bug#26911: 25.2; eshell "cd .." doesn't work correctly with TRAMP
Date: Mon, 31 Aug 2020 16:36:41 -0700 [thread overview]
Message-ID: <42b50db9-dba8-b6d0-8373-3d13089bbce6@cs.ucla.edu> (raw)
In-Reply-To: <83imcywso2.fsf@gnu.org>
On 8/31/20 11:56 AM, Eli Zaretskii wrote:
>>> expand-file-name deals only with the syntax of file names.
>> Yes, but it does so under constraints imposed by semantics. This is why
>> expand-file-name can't simply remove*all* slashes from file names (which would
>> be just a "syntax" thing, no? :-).
> No, because a valid syntax of an absolute file name is to start with a
> slash.
Ending with a slash is just as much syntax as starting with a slash is. The
meaning (absolute versus relative for starting slash, or directory versus file
for ending slash) is a consequence of the syntax in both cases. In neither case
should expand-file-name remove the slash, unless it can determine that removing
the slash does not change the meaning of the name (which it can do in some cases
but not in all).
> We disagree. So any further argument is fruitless
That's not a good way to resolve the disagreement. A better way is for me to see
what changes you make or plan to make to expand-file-name. If these changes
handle file names on GNU and POSIX platforms consistently with other GNU
applications, everything will be OK. It's possible we are simply
misunderstanding each other, after all.
next prev parent reply other threads:[~2020-08-31 23:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 16:15 bug#26911: 25.2; eshell "cd .." doesn't work correctly with TRAMP Yegor Timoshenko
2017-05-13 18:25 ` Michael Albinus
2017-05-13 18:30 ` Yegor Timoshenko
2017-05-15 15:53 ` Michael Albinus
2020-08-26 20:39 ` Paul Eggert
2020-08-27 11:46 ` Michael Albinus
2020-08-27 18:31 ` Mattias Engdegård
2020-08-27 18:38 ` Eli Zaretskii
2020-08-27 18:54 ` Stephen Berman
2020-08-27 21:53 ` Paul Eggert
2020-08-28 6:39 ` Eli Zaretskii
2020-08-28 7:01 ` Eli Zaretskii
2020-08-28 10:48 ` Eli Zaretskii
2020-08-29 5:52 ` Paul Eggert
2020-08-29 6:31 ` Eli Zaretskii
2020-08-29 16:46 ` Paul Eggert
2020-08-29 16:59 ` Michael Albinus
2020-08-29 18:29 ` Eli Zaretskii
2020-08-29 19:12 ` Michael Albinus
2020-08-29 19:31 ` Eli Zaretskii
2020-08-30 9:46 ` Michael Albinus
2020-08-30 14:14 ` Eli Zaretskii
2020-08-29 18:26 ` Eli Zaretskii
2020-08-29 20:42 ` Paul Eggert
2020-08-30 14:09 ` Eli Zaretskii
2020-08-30 21:39 ` Paul Eggert
2020-08-31 14:58 ` Eli Zaretskii
2020-08-31 18:15 ` Paul Eggert
2020-08-31 18:56 ` Eli Zaretskii
2020-08-31 23:36 ` Paul Eggert [this message]
2020-09-01 2:33 ` Eli Zaretskii
2020-09-03 17:27 ` Eli Zaretskii
2020-09-03 17:42 ` Michael Albinus
2020-09-04 11:55 ` Michael Albinus
2020-09-04 12:25 ` Eli Zaretskii
2020-09-04 13:53 ` Michael Albinus
2020-09-04 14:40 ` Eli Zaretskii
2020-09-04 15:20 ` Eli Zaretskii
2020-09-04 15:59 ` Michael Albinus
2020-09-04 17:42 ` Eli Zaretskii
2020-09-05 8:34 ` Michael Albinus
2020-09-05 11:18 ` Eli Zaretskii
2020-09-05 11:32 ` Eli Zaretskii
2020-09-05 15:57 ` Michael Albinus
2020-09-05 16:33 ` Eli Zaretskii
2020-09-05 17:08 ` Eli Zaretskii
2020-09-05 17:36 ` Michael Albinus
2020-09-05 17:56 ` Eli Zaretskii
2020-09-04 16:09 ` Michael Albinus
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=42b50db9-dba8-b6d0-8373-3d13089bbce6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=26911@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=michael.albinus@gmx.de \
--cc=yegortimoshenko@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 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.