unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Michael Albinus <michael.albinus@gmx.de>,
	45402@debbugs.gnu.org, rms@gnu.org
Subject: bug#45402: Rename Tramp method "media"
Date: Sat, 26 Dec 2020 00:38:11 +0100	[thread overview]
Message-ID: <87im8ph2xo.fsf@gmail.com> (raw)
In-Reply-To: <3b97680e-761a-4075-b64a-ad6d3a1004bf@default> (Drew Adams's message of "Fri, 25 Dec 2020 14:35:42 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> 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.

I might be missing something, but it seems to me like there is a rather
large design space for opt-in, backward-compatible ways to disambiguate
Tramp methods: off the top of my head, I could imagine e.g. a variable
(say "tramp-implicit-methods") which

- could default to t, meaning:

> always assume that /foo can actually mean /trampfoo for all foo's
> supported by Tramp

- could be set to a list of commonly used Tramp methods, e.g. '("ssh"
  "sudoedit"), meaning:

> when I type /ssh, assume that I can mean /trampssh; otherwise if I
> type /foo assume that I never mean /trampfoo

- could be set to nil, meaning:

> when I type /foo, I *never* mean /trampfoo for any foo supported by
> Tramp; I will always type out /trampfoo:

Or we could go the opposite route, with e.g. tramp-explicit-methods (nil
by default), which in the context of this report could be set to
'("media") so that /media can complete to /media/$USER, and users would
be required to type out /trampmedia: explicitly.





  reply	other threads:[~2020-12-25 23:38 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
2020-12-25 23:38             ` Kévin Le Gouguec [this message]
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=87im8ph2xo.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=45402@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    --cc=rms@gnu.org \
    /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).