Re: Convert README.org to plain text README while installing package

[Eli Zaretskii]

> From: Tim Cross <theophilusx@gmail.com>
> Cc: acm@muc.de, emacs-devel@gnu.org
> Date: Thu, 09 Jun 2022 05:34:09 +1000
> 
> > ??? How is remapping "not new"?  It takes some very common Emacs
> > commands and redirects them to different commands.  E.g., 'open-line'
> > now does something quite different.  This means the user should either
> > go learn what the Org commands do, or be prepared to be surprised.
> 
> This are not new key bindings, they are redefinitions of existing key
> bindings to make them work in an org mode context in a wayu which is
> consistent with user expectations.

That's exactly my point: suddenly commands that I'm familiar with are
working in ways that are different, even if slightly different.  A
conscientious Emacs user will want/need to study the differences,
before using those remapped commands.

> They are not new in the sense of them being a key binding which did
> not exist prior to loading org mode.

This completely misses the point I explain above.  The _commands_
behave differently, and that is all that counts.

> >> Any bindings relating to babel, todo management, time management,
> >> agendas etc have no relevance when reading a readme.org file.
> >
> > Then why does Org define them in that case?
> 
> because standard org mode is not typically used in read only buffers.

Which is one more argument towards more modularity in Org, so that
only the relevant bindings and commands are defined for each use case.

> As to whether defining 200 key bindings is too many - well I don't think
> you can possibly say either way without significantly more analysis.

Which is why I suggested you do this kind of analysis.

> It also isn't at all given that adding 200 new key bindings in a new
> mode is of itself problematic. There could be very good reasons to
> add that many bindings.

You have just explained that many of them are not relevant, even for
editing simple enough Org files.  For example, everything related to
org-babel -- why do these bindings have to be available by default?
Many Org files have no code blocks at all.

> Besides, I'm not sure it even is a problem. Emacs has lots of key
> bindings - the vast majority of which I never use. I don't find this
> a problem and I'm not convinced just citing absolute binding numbers
> in itself is evidence of a problem.

Well, I _am_ convinced, looking at this from the POV of the Emacs
maintainer.  I also think almost everyone agrees that too many
unneeded keybindings are a problem in general -- witness the removal
of some veteran global bindings in recent Emacs version, which is
evidence that we consider even half a dozen less-then-useful bindings
not a good thing.