Start a new topic
Discussions beorg forum Feature Requests

Drawers support

Drawers are a standard feature of org mode described in the manual https://orgmode.org/manual/Drawers.html They look like: ** This is a headline Still outside the drawer :DRAWERNAME: This is inside the drawer. :END: After the drawer. They can be folded or unfolded with the usual visibility cycling. On Android orgzly they are supported, and I use them there to hide code that is emacs dependent. Presently beorg simply ignore them. Drawers are also used for PROPERTIES, which are also ignored by beorg. It would be nice to add them at least in visibility cycling to ensure compatibility with beorg and orgzly.
2 people like this idea
33 CommentsSorted by Newest First

Matthew, I'm a little confused about your reply your response to Stephen Walsh. To me it suggests that we can log state changes into a drawer by setting org-log-into-drawer to #t. I also use org-modes to track habits, and I log todo state changes into LOGBOOK. I'd like to replicate this functionality in Beorg. In my init.org file, I have (defvar org-log-into-drawer #t), but this doesn't alter the way Beorg logs todo state changes. Am I missing something here? I'm not too technically proficient, but I believe I can follow instructions relatively well. If it's relevant, I've purchased all extensions except the ones for Encryption and Properties. Any help would be greatly appreciated. 

Matthew, I'm a little confused about your reply to Stephen Walsh. To me it suggests that we can log state changes into a drawer by setting org-log-into-drawer to #t. I also use org-mode to track habits, and I log todo state changes into LOGBOOK. I'd like to replicate this functionality in Beorg. In my init.org file, I have  (defvar org-log-into-drawer #t), but this doesn't alter the way Beorg logs todo state changes. Am I missing something here? I'm not too technically proficient, but I believe I can follow instructions relatively well. If it's relevant, I've purchased all extensions except the ones for Encryption and Properties. Any help would be greatly appreciated. 

In beorg this is called org-log-into-drawer - setting that to something other than #f will log state changes and clock/timer entries. Note that clock/timer entries default to LOGBOOK so even if #f they get put into a drawer.

1 person likes this
I’d like to add in to this about drawers if I may. When marking repeating tasks as done, could we specify a drawer to contain these completions? Emacs has `log-to-drawer` that I use on my computer and it works very well for all the habits I keep track of, but I always end up manually shuffling the text around after a completion ticked in beorg.
Looking forward to folding drawer support.
Many thanks! Looking forward to full drawers support and much more! Thanks and good luck!
1 person likes this

beorg understands and parses drawers internally. This enables searching of properties and is used by the new task timers (clocking) feature. However for the moment that it is the limit of the support for drawers. Eventually I want to enable easy editing of drawer contents (particular properties drawers) and folding of drawers when displayed in the outline.

Last update enables search in drawers. Ares drawers supported? How to use them? Thanks!

I'll look at including this in the next release which has some support for drawers.

One feature for drawers that would be particularly nice for me would be logging repeated tasks into the :LOGGING: drawer as right now I do have the option logdrawer set in my orgmode files but when I mark repeating tasks off as done in beorg, it puts it outside of the logging drawer which also seems to lead to all sorts of other problems when working directly with orgmode. That said, this is less of a needed feature as a simple fix would just be to not log it into a drawer - but I do find this feature quite useful especially with tasks that use the "habit" style.

1 person likes this

I have started work on support for drawers, including special recognition of PROPERTIES and LOGBOOK drawers. Such drawers will be hidden by default when exporting files/items and in notifications. You'll certainly be able to search for items with specific properties - for example "t shopping r shop supermarket" will find times tagged with "Shopping" and where a property "SHOP" is set to "Supermarket" (note search will be case insensitive).


This is likely to be released at the end of July/beginning of August.

3 people like this

I would definitely like to support drawers in general and PROPERTIES specifcally... I'd love to be able to write scheme filters against things like "style: habit" or "effort: 0:05" or other common uses of properties.


I'm going to try toying around with scheme to see if I can come up with a way of capturing just the properties drawer, but it's a bit clunky to play in that sandbox now without even a console.log equivalent.


It would also probably be best if drawers were ignored when showing push notificatons of scheduled items


I often have todo items that are like...

* headline that i'd like to see
SCHEDULED: <2019-07-11 Thu>
:PROPERTIES:
stuff_i_care_about: 0
...
:END:
body text that would be better to show than the properties drawer


I believe that there are many people really need this feature just like me !

Thanks for the clarification on this request. I guess there are a number of things to implement:


1. Getting beorg to parse drawers and then update/read the property drawer programatically

2. In the outliner there should be a way of expanding/collapsing drawers

3. When HTML is rendered (for use when showing notes in the item editor and for document export) drawers should be hidden as it doesn't make sense to show them here

1 person likes this
I was looking for drawer open/close cycling too. I use drawers to stash stuff so it doesn’t interrupt the flow of the document. Beorg just dumps all that as text right where it is. That’s better than losing it but not an elegant solution.
Login or Signup to post a comment
More topics in Feature Requests
See all 179 topics