Oh! That's a "set!, not "setl" !
I'd been using init to set the tag column as Emacs and Beorg disagree, but I recently noticed it wasn't working and reset it in Emacs.
Check https://beorg.app/learning/excluding-tasks-from-specific-files-for-the-agenda-and-todo-lists/ for a guide on creating an init.org.
Thanks Matthew! Could you guide me to where init.org should be stored? Is it in the root org folder? I added it and the setting you posted, but the app doesn't seem to respect spacing still. Anything I'm missing?
There is a new setting to add blank lines between headers. Add...
(set! beorg-add-newline-between-headlines #t)
...to your init.org. Possibly still not quite what some of you are looking for so hope to continue to make improvements here.
+1 Still very much waiting for this feature. It's holding me back from using the app.
++
Another +1 for keeping blank lines
another +1 in favor of not removing blank lines. This creates all kinds of (apparently unnecessary?) churn for a workflow that syncs between my working org mode directory and iCloud.
Having a setting that only affects entries added in beorg, but not the entire file, sounds great to me.
thanks!
I have made some small improvements on this over the past few releases but still some work to do.
I would love to hear if the setting is implemented or not? Seems it cannot be found in beorg3 or it is somewhere hided? :)
Thanks. Glad to hear it.
I will take a look to see if a new setting can be introduced to stop beorg messing with blank lines. For most users they would probably keep this on - but if you do you want to be in control of spacing, etc then I'll see if beorg can be made to leave that alone.
Same issue here, after I modified some of my GTD items, some irrelevant parts of the the org file containing the items are also changed.
All I want is that, if I modified TODO item status only, only that *relevant* part will be changed, so that my original formatting will not be affected.
Good idea. By now I use beorg only with a dedicated org file because of the formatting, hope that you can put this idea into your wish list :)
David Masterson
Something you could discuss is the expectations that BeOrg has in the format of the Org files (if any).