bastibe
Journal into org datetree file (like capture mode does)
I would like to be able to use datetree's for journaling, rather than per day note files. Or at least support datetrees generation from a note file folder.
They are note very well documented, but they are a part of a capture process. In the org manual they are mentioned as a capture type: http://orgmode.org/org.html#Template-elements
In essence they generate a 'tree of dates':
* 2017
** December
*** Friday December 1st
Captured text.
This and subtree hiding is what i was using for journaling into a single document before. I am getting more used to your scheme though.
It would be relatively easy to implement this structure in every daily file by modifying org-journal-date-format. But I guess this structure makes more sense if you have one big file instead of many daily files. I guess you could modify org-journal-file-format to always refer to the same file, but that would kind of defeat the purpose of org-journal.
I have a requirement, i want to be able to journal into a date tree file as a way of tracking the contents of regular meetings, as a form of meeting minutes or log. The advantage of a single file, is that the meeting history is in one buffer i can also embed a separate todo_seq workflow and publishing strategy. Nice too if i can have a journal entry with a link!
Honestly, I am not sure if org-journal is the right tool for the job. As I said before, you can probably make it do what you want, but it would probably be much easier to write a short function that inserts a new header in your date tree file.
@akirak Thanks for pointing that out. Your package requires Emacs 26.1 but org-journal supports Emacs 25.2+. Anyway, I'll have a look at this.
This is an old issue but I would like to add my support for having a datetree as an option for the journaling structure. It would make it much easier to navigate the journal file(s) manually which I sometimes like to do. In org-roam-dailies, you can also choose to organize the tree by year-weeknumber-weekday which is nice, but I want the carryover function of org-journal. Datetrees are neat and nice and don't give me panic attacks from overwhelm because of long lists.
If anyone wants to contribute a pull request, we'll be happy to review and merge it!
If anyone wants to contribute a pull request, we'll be happy to review and merge it!
came here for requesting the feature but sadly, donot have expertise in emacs lisp to do it any hopes ?
If anyone wants to contribute a pull request, we'll be happy to review and merge it!
came here for requesting the feature but sadly, donot have expertise in emacs lisp to do it any hopes ?
I'll have a call with @bastibe tomorrow about the future of org-journal. Adding new features, however, is currently not a high priority. We need to put some effort into improving CI first and then do a little cleanup before adding new features.
Best regards,
Christian
If anyone wants to contribute a pull request, we'll be happy to review and merge it! came here for requesting the feature but sadly, donot have expertise in emacs lisp to do it any hopes ? I'll have a call with @bastibe tomorrow about the future of org-journal. Adding new features, however, is currently not a high priority. We need to put some effort into improving CI first and then do a little cleanup before adding new features. Best regards, Christian
thanks for response. I will try to do some hacky attempt for this and get back to you with results for integrating datetree with org-journal. But my elisp is really miserable i doubt i can do the task of integrating it. writting a small function for such carry over in datetree seems like a possibility for me. But if you guz ever add the datetree support in org-journal it would be really awesome
Aneeq Asif @.***> writes:
If anyone wants to contribute a pull request, we'll be happy to review and merge it! came here for requesting the feature but sadly, donot have expertise in emacs lisp to do it any hopes ? I'll have a call with @bastibe tomorrow about the future of org-journal. Adding new features, however, is currently not a high priority. We need to put some effort into improving CI first and then do a little cleanup before adding new features. Best regards, Christian
thanks for response. I will try to do some hacky attempt for this and get back to you with results for integrating datetree with org-journal. But my elisp is really miserable i doubt i can do the task of integrating it. writting a small function for such carry over in datetree seems like a possibility for me. But if you guz ever add the datetree support in org-journal it would be really awesome
Go ahead, if you need help, do not hesitate to ask. Haven't looked into the org source code for a while, therefore I can't give you any great advice right now.