From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, emacs-devel@gnu.org
Subject: Re: master 695f679: Remove ; ; ; ###tramp-autoload cookie from Tramp defcustoms (Bug#47063)
Date: Sun, 14 Mar 2021 10:57:01 -0400 [thread overview]
Message-ID: <jwv1rch3hwh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sg4ygmd9.fsf@gmx.de> (Michael Albinus's message of "Sun, 14 Mar 2021 09:39:30 +0100")
>>> My question is, which combination of the following should happen:
>>> - The completion-predicate properties are not autoloaded.
>> This means that autoloaded functions will always be listed in `M-x`
>> (except after loading the corresponding package), which is undesirable.
> Calling `tramp-crypt-add-directory' interactively is the only way to
> activate package tramp-crypt.el. As long as the package isn't loaded
> yet, this command must be visible.
Presumably, if there's a `completion-predicate` it's because there are
circumstances where it makes no sense to use `M-x
tramp-crypt-add-directory`. Is it really the case that such situations
can only happen once `tramp-crypto` is loaded? If so, I'd tend to think
that they are sufficiently marginal that it's not worth having
a `completion-predicate`.
Stefan
next prev parent reply other threads:[~2021-03-14 14:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210313133546.6042.78482@vcs0.savannah.gnu.org>
[not found] ` <20210313133547.AA06C20B2E@vcs0.savannah.gnu.org>
2021-03-13 22:27 ` master 695f679: Remove ; ; ; ###tramp-autoload cookie from Tramp defcustoms (Bug#47063) Basil L. Contovounesios
2021-03-13 23:20 ` Stefan Monnier
2021-03-14 8:39 ` Michael Albinus
2021-03-14 12:59 ` Basil L. Contovounesios
2021-03-14 14:57 ` Stefan Monnier
2021-03-24 22:19 ` Basil L. Contovounesios
2021-03-25 8:25 ` Michael Albinus
2021-03-26 15:18 ` Basil L. Contovounesios
2021-03-26 15:24 ` Michael Albinus
2021-03-25 9:12 ` Lars Ingebrigtsen
2021-03-25 14:05 ` Stefan Monnier
2021-03-26 11:28 ` Lars Ingebrigtsen
2021-03-26 13:39 ` Stefan Monnier
2021-03-26 14:42 ` Michael Albinus
2021-03-26 18:39 ` Basil L. Contovounesios
2021-03-26 15:36 ` Basil L. Contovounesios
2021-03-26 16:37 ` Stefan Monnier
2021-03-26 18:18 ` Basil L. Contovounesios
2021-03-26 22:12 ` Lars Ingebrigtsen
2021-03-26 15:57 ` Basil L. Contovounesios
2021-03-26 15:33 ` Basil L. Contovounesios
2021-03-26 16:32 ` Stefan Monnier
2021-03-26 18:18 ` Basil L. Contovounesios
2021-03-26 15:27 ` Basil L. Contovounesios
2021-03-26 22:11 ` Lars Ingebrigtsen
2021-03-27 1:18 ` Basil L. Contovounesios
2021-03-27 12:33 ` Lars Ingebrigtsen
2021-03-27 20:29 ` Basil L. Contovounesios
2021-03-14 14:57 ` Stefan Monnier [this message]
2021-03-14 18:42 ` Michael Albinus
2021-03-14 20:30 ` Stefan Monnier
2021-03-15 9:00 ` 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=jwv1rch3hwh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=contovob@tcd.ie \
--cc=emacs-devel@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 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).