I don’t need to record logs for my daily routine tasks, so I’m currently deleting them manually.
Timetracking is turned off, but logs are recorded.
OS: Sonoma 14.6.1
Logseq: 0.10.9
## Daily Task
- LATER Exercise 1
SCHEDULED: <2024-09-12 Fri .+1d>
:LOGBOOK:
....
* State "DONE" from "LATER" [2024-09-10 Tue 17:11]
* State "DONE" from "LATER" [2024-09-11 Wed 17:53]
:END:
Try turning on the timetracking feature and then turning it off again. Those options can be a bit quirky sometimes and turning the option off and on resets the state of the feature.
I’ve tried turning Timetracking on and off and restarting several times, but I still can’t seem to disable the LOGBOOK. I wonder why that is - is it just me?
Manually deleting it isn’t too much trouble.
I’ll check again when a new version comes out.
Logbook data that was created when the timetracking option was enabled will not be removed from the Markdown file on disk. But the time info should disappear from the UI in Logseq when disabling the feature.
Is this the case for you? Meaning: is the time gone from the Logseq UI but it’s still in the Markdown file(s)? If so, I’m afraid you indeed need to remove it manually if you don’t want the data to be in the Markdown file.
I have noticed something after doing various tests myself.
There are two types of LOGBOOK information written to Markdown files.
(Image attached)
The part surrounded by a blue line is the Timetracking log.
The part surrounded by a red line is the log written when the checkbox for the repeat task is clicked.
The repeat task log is what concerns my question.
This has nothing to do with the Timetracking settings.
A large amount of LOGBOOK is recorded for daily tasks.
So, the intention of my question is, is it possible to stop this log from being output?
If the file format is org-mode, I think you can set the following property at the beginning of the file or in a block to prevent LOGBOOK from being output (I can’t quite remember), but it seems there is no way to set it in Markdown.
:PROPERTIES:
:LOGGING: nil
:END:
- I’m using machine translation, so please forgive me if the English is strange.
Did a quick test to confirm, even with timetracking disabled it will still give me this log entry for my scheduled tasks. Even though it won’t show up in the frontend
Both with hourly and daily in Logseq 0.10.9
@Marmia - I think it’s part of the scheduled set to keep track on how often it’s clicked. Since this feature will be removed in the DB version as far as I know I don’t think this will be resolved before the full release of that.
I think it’s part of the scheduled set to keep track on how often it’s clicked.
I see.
Since this feature will be removed in the DB version as far as I know I don’t think this will be resolved before the full release of that.
Thanks for letting me know.
Looking forward to the DB version being released.
Thanks to all who replied.