-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
org-journal-carryover-items for items except "DONE" but deleted entries instead #393
Comments
Could you give an example of how things get "messed up"? |
It will delete the heading of the current date, e.g. Tuesday, 21/06/2022
and all of its subheadings (entries) under that date, and then create a new
entry in the previous date, not sure it will delete entries in previous
date as well.
…On Tue, 21 Jun 2022 at 16:15, Bastian Bechtold ***@***.***> wrote:
Could you give an example of how things get "messed up"?
—
Reply to this email directly, view it on GitHub
<#393 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFZFNH7QCX4O3PFNYD2CZTVQFQHNANCNFSM5YE2WXYA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Best regards,
*Bao*
|
Could you paste an example? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I tried with the config
(setq org-journal-carryover-items "-TODO=\"DONE\"")
to move all items except "DONE" to be carried to the new date. However if I config that way everytime I create new entry it will somehow mess up with the current-date entries and delete the headings of the current date.To Reproduce
Steps to reproduce the behavior:
Set this in the config:
(setq org-journal-carryover-items "-TODO=\"DONE\"")
and initiate
org-journal-new-entry
Expected behavior
All items except "DONE" will be carried to next date.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Your Emacs Configuration
The part relevant to org-journal.
The text was updated successfully, but these errors were encountered: