Start a new topic

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

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.

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

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. 

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. 

Currently beorg only logs state changes for repeating entries. I hope to look at adding support for logging all state changes at some point in the near future.

Thank you for your reply, Matthew. I was imprecise in my original post. My aim is to log repeating tasks in Beorg into the same LOGBOOK drawer Emacs uses. TODO state changes logged in Beorg are currently logged directly beneath TODO headings. I assumed I could use  (defvar org-log-into-drawer #t)--similar to the way I use 'log-to-drawer' in Emacs-- but that doesn't achieve the desired functionality. I find myself in the same position as Stephen Walsh; I have to move 'text around after a completion ticked in Beorg.' If the functionality I'm seeking isn't available in Beorg, that's okay, but if it is, could you point me in the direction of a solution? And sorry for hijacking this thread. 

In your init.org you should be able to do (for example):


(set! org-log-into-drawer "LOGBOOK")


or similar. The default for this is #f which tells beorg not to log entries into a drawer.


Check out https://www.beorg.app/manual/library-org/ for the default org file beorg loads which sets up the variables you can modify.

Login or Signup to post a comment