From: Drew Adams <drew.adams@oracle.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Michael Albinus" <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45402@debbugs.gnu.org
Subject: bug#45402: Rename Tramp method "media"
Date: Fri, 25 Dec 2020 14:35:42 -0800 (PST) [thread overview]
Message-ID: <3b97680e-761a-4075-b64a-ad6d3a1004bf@default> (raw)
In-Reply-To: <87o8ihh6xp.fsf_-_@gmail.com>
It's no doubt too late now, at least in general,
but maybe it would make sense to use a prefix
for Tramp, kind of like what we do for libraries.
Besides being too late, I imagine someone will
say that that would be too verbose for users to
type, which is true.
But even a prefix of "t" might be sufficient to
usually distinguish Tramp's protocol names. In
this case, ~//tmedia would mean Tramp's protocol
and ~//media would mean (change to) local
directory /media.
Yeah, it's ugly. But the Tramp syntax is
apparently inherently ambiguous here (i.e., can
conflict with a dir name).
next prev parent reply other threads:[~2020-12-25 22:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 5:53 bug#45402: 28.0.50; new completion inconvenience Richard Stallman
2020-12-24 5:58 ` Jean Louis
2020-12-24 8:53 ` Michael Albinus
2020-12-24 14:36 ` Eli Zaretskii
2020-12-24 17:02 ` Michael Albinus
2020-12-24 17:18 ` Eli Zaretskii
2020-12-25 4:42 ` Richard Stallman
2020-12-25 11:06 ` Michael Albinus
2020-12-26 10:22 ` Richard Stallman
2020-12-26 10:28 ` Michael Albinus
2020-12-27 5:34 ` Richard Stallman
2020-12-25 5:56 ` Lars Ingebrigtsen
2020-12-25 11:17 ` Michael Albinus
2020-12-25 11:20 ` Kévin Le Gouguec
2020-12-25 19:31 ` Lars Ingebrigtsen
2020-12-25 20:31 ` Michael Albinus
2020-12-25 22:11 ` bug#45402: Rename Tramp method "media" Kévin Le Gouguec
2020-12-25 22:35 ` Drew Adams [this message]
2020-12-25 23:38 ` Kévin Le Gouguec
2020-12-26 8:52 ` Michael Albinus
2020-12-26 8:44 ` Michael Albinus
2020-12-26 18:53 ` Drew Adams
2020-12-26 11:44 ` 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
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=3b97680e-761a-4075-b64a-ad6d3a1004bf@default \
--to=drew.adams@oracle.com \
--cc=45402@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.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 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).