It seems my easy templates completion is being ignored. I'm 9.2
(9.2-41-g010a35-elpa ...). I've found a reference or two online but the
fix, i.e., running (require 'org-tempo) only produced error messages. The
"documentation" doesn't really say exactly what the new format is. Here's a
sample of
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> A gentle ping..
>
> I'm not sure "org-drill.el" is still actively maintained. I'm Cc'ing
> Paul Sexton. In the long run, I think this package could be packaged
> through ELPA instead.
It is indeed not actively maintained. But
Tim Cross writes:
> I totally agree that block delimiters should be case
> insensitive. However, I think the ability for a user to set their
> preference for either upper case or lower case is reasonable. It does
> not need to affect the syntactic interpretation, just whether the
> template
Jamie Forth writes:
> Of course, sorry to miss this first time around.
No problem. I applied you patch. Thank you.
Regards,
Hello,
Nicolas Goaziou writes:
> Thank you. Could you also add an entry in ORG-NEWS file?
Of course, sorry to miss this first time around.
Regards,
--
Jamie Forth
>From d2ab748302a72879a348748fbb9d021b32bc3b0a Mon Sep 17 00:00:00 2001
From: Jamie Forth
Date: Mon, 21 Jan 2019 18:01:13 +
Hello,
stardiviner writes:
> A gentle ping..
I'm not sure "org-drill.el" is still actively maintained. I'm Cc'ing
Paul Sexton. In the long run, I think this package could be packaged
through ELPA instead.
>> * etc/ORG-NEWS: mentioned this new feature.
Changes to "contrib/" directory are
Hello,
Jamie Forth writes:
> Hi,
>
> Sometime I find it useful to align Beamer notes with slide overlays, for
> example, when stepping through a worked example (see attachment).
>
> Beamer permits notes to have overlay specifications but presently these
> are not exported by org.
Thank you.
Hello,
Tim Cross writes:
> I totally agree that block delimiters should be case
> insensitive. However, I think the ability for a user to set their
> preference for either upper case or lower case is reasonable. It does
> not need to affect the syntactic interpretation, just whether the
>
I totally agree that block delimiters should be case
insensitive. However, I think the ability for a user to set their
preference for either upper case or lower case is reasonable. It does
not need to affect the syntactic interpretation, just whether the
template system does it in upper case or
Hello,
Amin Bandali writes:
[...]
> I think it would be nice to provide a defcusom to allow choosing between
> upper vs. lowercase.
that would make the exchange of Org files with colleagues and other Org
aficionados complicated, wouldn't it? As Nicolas said, blocks are
case-insensitive, meaning
10 matches
Mail list logo
