Hi Nicolas,

Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Bastien <b...@gnu.org> writes:
>
>> Again, I may be wrong in thinking disabling this will cause trouble to
>> many users.  Let's just take a moment to see what users think.
>
> It will case trouble during the time necessary to read ORG-NEWS
> incompatible changes section or ask the mailing list, and then adding
> (require 'org-tempo) to their configuration file.

I wish I'd be as optimistic as you are and assume every user reads
ORG-NEWS!  I seriously doubt a majority of users do.  Those installing
Org from ELPA cannot possibly know where to find ORG-NEWS, Org gives
no indication where it lives: IOW, it's not even because users are
lazy or what.

> It seems nonsensical to let Org handle expansion templates. Dedicated
> packages do it way better than what we provide, and the task is really
> out of our scope.

I can't remember anybody complaining Org's expansion mechanism.

> Worse, we would provide two different ways to expand blocks /by
> default/.

I see it differently.  You and Rasmus (and those participating to the
discussion) cleanly separated two functionalities: one is to *insert*
templates the other one is to *expand* them.

M-x org-insert-structure-template RET is good for discovery as it lets
users see what templates are availables and <[KEY][TAB] is good for
fast inline expansion.

Both complete each other IMO, and both deserve to be in Org's core.

But again, I might be wrong, I just don't want this to be a discussion
between us two :)

-- 
 Bastien

Reply via email to