Re: Current mode command discovery

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 17 Feb 2021 18:49:42 +0100
> Cc: Óscar Fuentes <ofv@wanadoo.es>, emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Because whoever marked it "nonsensical" made a mistake?  Or because
> > time passed, things have changed, and what made no sense back then may
> > make sense now, and Emacs maintainers missed that or couldn't keep up?
> >
> > IOW, let's not assume that the marking is perfect.  It's done by us,
> > and we can make mistakes.
> 
> Any code can have bugs.  That doesn't stop us from writing code or
> designing systems.
> 
> If there's a bug, we fix the bug.

What do you tell a user who cannot invoke a command?  "Wait for the
next release"?

That's why "fire escapes" are useful: they are Plan B for when the
unexpected strikes.

> But it's extremely unlikely that the tagging of, say, `eww-readable'
> will change.

Unexpected problems are always unexpected, they cannot be known in
advance.  Therefore, examples don't help, because examples always talk
about something we considered and made a decision about.  Whereas
"fire escapes" are about risk management, not about design.