if the question is properties and settings, and not anything else,
then perhaps a solution could be to put them on a dedicated header,
and then the user can move them to top or bottom as desired. the name
of this meta or level 0 header could be set in a variable.
perhaps alraedy considered or
Nicolas Goaziou writes:
> Hello,
>
> phillip.l...@russet.org.uk (Phillip Lord) writes:
>
>> I've launched an fork of org-drill. I have tried to reach Paul Sexton,
>> the original author, and had some feedback (he was happy for my take
>> over), but not managed to get the repository moved.
>>
>>
Hello,
phillip.l...@russet.org.uk (Phillip Lord) writes:
> I've launched an fork of org-drill. I have tried to reach Paul Sexton,
> the original author, and had some feedback (he was happy for my take
> over), but not managed to get the repository moved.
>
>
I've launched an fork of org-drill. I have tried to reach Paul Sexton,
the original author, and had some feedback (he was happy for my take
over), but not managed to get the repository moved.
https://gitlab.com/phillord/org-drill/
I'd like to have this be the version that ends up in contrib.
Hello,
Stefan Huchler writes:
> I wrote this template to capture my bills from mostly one shop, but it
> has support for multiple shops and the important feature is that it
> suggests previous item names and remembers last prices, that gives you
> lot's of autocompletion if you repetetivly buy
Dear Ihor,
> Regarding the question about buffer-lens interaction. Let's take even
> more complicated example: To run the command, the user hits some key
> combination, which happens to be bound to different commands in the main
> buffer and in the lense buffer (i.e. the main buffer is in
Gustav Wikström writes:
> I propose a "document" element in org-element, a property-drawer on
> document-level, a setting-drawer on document-level and
> property-keywords (slightly different than what already exist). And
> would like your comments regarding that!
When I started searching
