[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: Re: Convert README.org to plain text README while installing package
Date: Wed, 15 Jun 2022 15:49:06 +0300

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: theophilusx@gmail.com,  acm@muc.de,  emacs-devel@gnu.org
> Date: Wed, 15 Jun 2022 13:13:17 +0800
> 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.

This is a tangent, entirely unrelated to what I said.  My point was
that, unlike TeX source, which can only be submitted to TeX, and
therefore must follow TeX syntax and is written by people who are
familiar with TeX, Org is being advertised as a mode for editing
mostly-plain text.  And in plain text, what Org decided to take as an
indication of a table could very well be something else, because the
user just typed plain text, and was oblivious to its meaning in Org.

So Org is _unlike_ TeX mode, in that the assumption that every
environment or markup are only used where their Org meaning is
intended -- that assumption is not necessarily true, while it is in

> > 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]*|

That's what I remembered, and that is exactly what bothers me in the
context of this discussion: seemingly innocent text sequences are
interpreted by Org in some very special way, and the user doesn't
always have good means to disable that interpretation when it is not

> 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.

Imagine a user who has no idea that a space and a | at the beginning
of a line means it's an Org table, and thus won't realize that this
magically changes how commands behave in that chunk of text.  That is
the problem that was in my mind when I said that the special
table-related behavior should be better controllable and perhaps off
by default.

> >> 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.

If some instances of the same sequence of characters are indeed meant
to be a table, and other instances in the same file aren't, or if I
need to edit a file where they have this meaning and soon after a file
where they don't, I'd need to flip the option on and off very often.

> >> 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?

Majority of Org users or majority of Emacs users?

If we want to promote Org to be used more widely and frequently, that
would inevitably mean it will be used by Emacs users who use Org only
infrequently, and those are the ones I'm thinking about.  We should
make it easier to use Org infrequently, by people who don't do
everything in Org.

> >> > 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 can, because I'm talking about what the Emacs core developers did
(or, rather, did not do).  If you somehow interpreted that to allude
to the developers of the respective packages, that was not the intent.

IOW, I'm saying that when you compare the ELPA packages to Org in
these aspects, the comparison is not really valid, because Org gets
much more attention from the core developers than the ELPA packages,
especially since there's a tendency to use Org in more situations.

> If you have an ideas about any better way to deal with editing
> complex markups, please share it.

As I said before, these issues should be discussed one by one.
There's no reason to believe there will be a single solution for all
of them.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]