Re: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Christophe Schockaert <R3vLibre@citadels.eu>]

Alan Tyree writes:

> [...]
>
> Here is a question: I see specialised snippet packages in the ELPA
> respositories. Is it possible to provide snippets that reproduce the
> existing "Easy Templates", maybe even keep the same key bindings so that
> the change is transparent to the users that are likely to have the troubles
> referred to by Bastien?

By chances, I spent some spare time reading this thread, and the
previous one.

Well, Org is my daily-life tool, I am a bit outdated, although. And I
would like to change that, by getting closer to Org upgrades.

I fully understand and can value the need for improving software design
and focusing towards consistent functions, as time passes by and
software grows and evolves.

Also, when there are breaking changes, the thing is that it's often
never the right time. I mean, however small it is, when you are in your
daily process, it does not necesserily fit your agenda. So, I try to
carefully select times for my upgrades, and I am glad to be aware of
this one.

So, I am ready to adapt myself. I will probably learn the new keys if
they are easy to work with. However, the existing shortcut seems so
natural to remember for whom is used to markup tags. And it's easy to
type.

If yasnippets is the way to go, I'll use them. I never took the time yet
to address them. Thus, I like Alan idea to prepare a set of shortcuts
that would match the existing ones. That way, we would have a common set
acting as a base for org users.

I will have a look at org-tempo, too, as it exists and easy to handle.

As for letting know the users, I think it's a very important part.
Could the ORG-NEWS clearly identify the expected breaking changes and
refer to a receipe for handling them ?

Also, would it be possible to add a link to the ORG-NEWS file in the
ELPA package description ? I don't think there is.

I know it exists, and that's where I went for my first breaking changes,
but if we can make it obvious for those would might not be long time
users, that would be great :-)


I any case, thank you for the awesome work you're all doing here.


Cheers,

Christophe


> It is a genuine question since I have no idea of the problems involved.
>
> I'll keep using org no matter what you decide!
>
> Cheers,
> Alan
>
>
> On 1 May 2018 at 08:49, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>> Hi all,
>>
>> I normally am all for adapting to changes, staying on bleeding edges of
>> emacs, Org, etc.
>>
>> But FWIW, for this particular change to the "<s" Easy Templates, I'm in
>> the camp of "It was working awesome, it was beautiful! Why change it?". For
>> record, I understand the "why", but it just doesn't seem worth it in this
>> case.
>>
>> But the good thing is that this is open source, and you can backport the
>> stuff you like from the original Easy Template code into your personal
>> Emacs config (and then later adapt to the new way of doing the similar when
>> you have time and motivation).
>>
>> Kaushal
>> --
>>
>> Kaushal Modi
>>


--
--------------->  https://www.citadels.earth
Once it's perfectly aimed, the flying arrow goes straight to its target.
Thus, don't worry when things go right.
There will be enough time to worry about if they go wrong.
Then, it's time to fire a new arrow towards another direction.
Don't sink.  Adapt yourself !  The archer has to shoot accurately and quickly.
[Words of Erenthar, the bowman ranger] <---------------<<<<