Re: master 695f679: Remove ; ; ; ###tramp-autoload cookie from Tramp defcustoms (Bug#47063)

[Michael Albinus]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> So I don't oppose catching errors here, really -- I'm just wondering why
>> we're designing for allowing broken code in this particular
>> circumstance.  Do we expect these code snippets to break for some
>> reason?
>
> I think it's because such errors have already occurred, and not being
> able to `M-x` just because of a silly mistake in a "secondary" feature
> is rather frustrating.
> Also, this feature runs code from "all" packages, so it is inherently
> exposed to a lot of potential messups.
>
> IOW, I agree that there's no hard-and-fast reason to do that, but
> I think it can make a substantial difference to the end users because
> it protects them from very minor but potentially common bugs.

IIUC, such errors can happen only, if command completion happens while
`read-extended-command-predicate' is a non-nil predicate. So we could give
the user an error message, which recommends

- to set `read-extended-command-predicate' to nil, and
- to write a bug report.

>         Stefan

Best regards, Michael.