Mike Gauland writes:
> I'd like to be able to be able to get the text associated with a given
> heading (based on the current point, for example).
>
> Can anyone point me to an example for doing this in the approved manner
> (assuming there is one), or to functions to help with this?
Don't
I'd like to be able to be able to get the text associated with a given
heading (based on the current point, for example).
Can anyone point me to an example for doing this in the approved manner
(assuming there is one), or to functions to help with this?
Kind regards,
Mike
I have a radio group of 3 tags defined in org-tag-alist: now. next, later.
This tag group works correctly when editing the tags directly in the
original org files or when the tags are edited individually in the agenda
using ':'.
When editing tags via the agenda's bulk editing command, however,
Hello,
Felix Wiemuth writes:
> In some situations, org-list-make-subtree does not create the tree at
> the desired level. For example, in the following case, when executing
> the command on the first list element, the resulting level is 3 instead
> of 2:
>
> * L1
> - List Item
> ** L2
>
> The
Nicolas Floquet writes:
> Le jeudi 16 mai 2019 à 17:16 +0200, Nicolas Floquet a écrit :
>> The problem is not solved on emacs 26.2.
>
> I have just humbly made a little commit wich is not the best solution,
> take in consideration that I am not a programmer… I can not currently
> do better ! :-)
Hi,
I'm surprised that noone answered yet.
This package is great! You're addressing one of the large shortcomings of
org-mode's planning features: org has information about several planning
details (estimation, duration, holidays, start date, deadline, …) and still
doesn't use any of that to
On Fri, 7 Jun 2019 at 22:31, Nicolas Goaziou wrote:
> Hello,
>
> Neil Jerram writes:
>
> > Nicolas, I hope you don't mind me sending a 'ping' for this, as it looks
> > like it might have got lost. Please do let me know what you think.
>
> I'm not sure this is a right fix. Doesn't it force
