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

[Ihor Radchenko]

Eli Zaretskii <eliz@gnu.org> writes:

> The syntax of TeX is dictated by an external tool.  By contrast, the
> syntax of Org is determined by Org itself.

Not exactly. We have to keep backwards compatibility and keep in mind 
external packages. So, syntax changes in Org must be avoided unless
strictly necessary. And they should be backwards compatible even if the
changes are necessary.

> Is an Org table always preceded by some directive that makes it
> impossible to interpret innocent text as a table?  If so, perhaps the
> problems that were bothering me don't actually exist.
>
> But if Org interprets some text patterns as meaning that there's a
> table here, that could be contrary to user expectations.

Org tables are always preceded by ^[ \t]*|
I am not sure what is the problem here. One can just not start lines
with | or put zero-width space if starting lines from | is absolutely
necessary.

>> We do not assume that users always expect specific behavior. That's wy
>> org-special-ctrl-o is customization.
>
> Relying on a user option for something that can need frequent
> adjustment is not the best UX.  defcustom is only a good solution when
> it expresses a more-or-less constant user preference that change only
> very rarely.  If I may need to change the value before invoking a
> command, that's inconvenient.

I am not sure why you need a frequent adjustment of org-special-ctrl-o.
This is the first time I hear about such a need.

>> It's default value has been agreed upon and has not been questioned
>> by many.
>
> Maybe because most Org users are frequent Org users and always know
> what they want well enough?  As mentioned, I have other kind of users
> in mind.

I understand, but we have to consider the needs to majority of users,
right? Customizations are there for other kind of users. Almost any kind
of default behavior, be it Org or Emacs, will suffer from some users not
liking it.

>> > I'm not arguing with the need, I'm arguing with the particular
>> > implementation that caters to that need.
>> 
>> Sorry, but I do not understand what you mean here, except that you are
>> dissatisfied with the existing implementation. AFAIU, you objected the
>> number of Org bindings. That many of them are not needed. I think my
>> reply was targeting your objection. I did not recognize any kind of
>> reference to implementation specifics.
>
> Adding keybindings is a solution to a problem.  I'm saying that
> alternatives to that solution were not seriously explored fro those
> unbundled packages.

How can you tell it with confidence? I, personally, cannot come up with
any better solution and haven't seen any alternative to the existing
numerous key bindings, except context-depended dwim bindings (which are
also frown upon). If you have an ideas about any better way to deal with
editing complex markups, please share it.

Best,
Ihor