>>> I think we can leave these methods untouched for compatibility but
>>> introduce some consistent aliases?
>>>
>>> | Action | How to reverse filing order |
>>> |-+---|
>>> | Refile | Introduce org-refile-prepend |
>>> | Capture | Introduce org-capture-pre
Ihor Radchenko writes:
>> I think we can leave these methods untouched for compatibility but
>> introduce some consistent aliases?
>>
>> | Action | How to reverse filing order |
>> |-+---|
>> | Refile | Introduce org-refile-prepend |
>> | Capture | Introdu
Karthik Chikmagalur writes:
> So for the record, this is the current state of things:
>
> | Action | How to reverse filing order |
> |-+--|
> | Refile | org-reverse-note-order |
> | Capture | :prepend key in org-capture template
> Currently, `org-add-note' ordering is controlled by
> `org-log-states-order-reversed'.
>
> I am afraid that changing the current status quo may create confusion.
> We might introduce a new variable `org-log-note-order-reversed' just for
> interactive notes. WDYT?
So for the record, this is the c
Karthik Chikmagalur writes:
> It's not clear from the documentation of `org-reverse-note-order' what
> "note" means:
>
> --8<---cut here---start->8---
> Non-nil means store new notes at the beginning of a file or entry.
> When nil, new notes will be filed to th
It's not clear from the documentation of `org-reverse-note-order' what
"note" means:
--8<---cut here---start->8---
Non-nil means store new notes at the beginning of a file or entry.
When nil, new notes will be filed to the end of a file or entry.
This can also b
