From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Michael Albinus <michael.albinus@gmx.de>
Cc: 70792@debbugs.gnu.org
Subject: bug#70792: 30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection
Date: Wed, 8 May 2024 11:57:19 -0700 [thread overview]
Message-ID: <9e2ced76-2eee-4d36-78e9-68695e018db8@gmail.com> (raw)
In-Reply-To: <86wmo4888l.fsf@gnu.org>
On 5/8/2024 11:32 AM, Eli Zaretskii wrote:
>> (As a note, Eshell already uses /:-quoting to mean "on the local host"
>> in one spot: for the command to run. However, I added that for Emacs 30,
>> so we can still change it without worrying about compatibility issues.
>> See the manual here for more info:
>> <https://git.savannah.gnu.org/cgit/emacs.git/tree/doc/misc/eshell.texi#n1534>.)
>
> I think we should remove that before we release Emacs 30. It's wrong
> to interpret quoting this way.
Ok, whatever we decide for this bug, I'll apply the same syntax over
there too.
>>> If the user wants to specify a local file name while default-directory
>>> is remote, the user can use the normal Tramp "/METHOD:..." notation.
>>
>> How about a new "local" method? Then users would type
>> "/local::~/some-file.txt". That's more typing, but it's also more clear,
>> and doesn't repurpose an existing syntax used elsewhere in Emacs.
>
> Don't we already have that with "/localhost:" or somesuch?
I don't see one like that. It shouldn't be too difficult to add though
(so long as Michael is ok with it).
next prev parent reply other threads:[~2024-05-08 18:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 20:58 bug#70792: 30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection Jim Porter
2024-05-06 11:14 ` Eli Zaretskii
2024-05-06 18:13 ` Jim Porter
2024-05-06 18:43 ` Eli Zaretskii
2024-05-06 20:05 ` Jim Porter
2024-05-07 2:01 ` Jim Porter
2024-05-07 11:55 ` Eli Zaretskii
2024-05-07 18:54 ` Jim Porter
2024-05-08 13:20 ` Eli Zaretskii
2024-05-08 16:13 ` Jim Porter
2024-05-08 18:32 ` Eli Zaretskii
2024-05-08 18:57 ` Jim Porter [this message]
2024-05-09 18:14 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 18:53 ` Eli Zaretskii
2024-05-09 19:10 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 20:30 ` Jim Porter
2024-05-09 22:15 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 22:28 ` Jim Porter
2024-05-10 5:45 ` Eli Zaretskii
2024-05-10 19:35 ` Jim Porter
2024-05-13 7:39 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 2:12 ` Jim Porter
2024-05-08 18:17 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-08 18:49 ` Eli Zaretskii
2024-05-09 18:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 19:02 ` Eli Zaretskii
2024-05-07 8:12 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 16:56 ` Sean Whitton via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 17:59 ` Eli Zaretskii
2024-05-06 18:28 ` Jim Porter
2024-05-06 18:37 ` Jim Porter
2024-05-07 8:50 ` Sean Whitton via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=9e2ced76-2eee-4d36-78e9-68695e018db8@gmail.com \
--to=jporterbugs@gmail.com \
--cc=70792@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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.