Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRead :LOGBOOK: drawer for metadata and modification timestamps #203
Comments
kaushalmodi
added
the
enhancement
label
Sep 6, 2018
This comment has been minimized.
This comment has been minimized.
I like the LOGBOOK feature, and probably something that I would use too. A long time back, I tried using the log book but it never worked for me.. I couldn't get the TODO/DONE state changes to log in the LOGBOOK drawer. And as it wasn't a pressing matter, I didn't did into what I should need to set in my config to make that work. In addition to changelog recording, I would also like to get the TODO state transitions recorded in there.
Yes, sort of. You can have posts without DONE state to not get published by Hugo (but they still will be exported with the draft front-matter set to true. Hugo doesn't publish such posts by default.) Just mark all posts to be drafts by default by putting |
This comment has been minimized.
This comment has been minimized.
@alphapapa I need to may be set some defcustoms to get notes going into LOGBOOK drawer? In a plain heading, doing
So I need to put a hack to interpret a list item beginning with "Note taken on " as something special? (which is not something I'd want to do). |
This comment has been minimized.
This comment has been minimized.
Hmm.. |
This comment has been minimized.
This comment has been minimized.
OK, I needed
Also finally the mystery clears on why I wasn't able to see state changes in LOGBOOK:
|
kaushalmodi
changed the title
Suggestion: Read :LOGBOOK: drawer for metadata and modification timestamps
Read :LOGBOOK: drawer for metadata and modification timestamps
Sep 6, 2018
This comment has been minimized.
This comment has been minimized.
Additionally, if you set |
This comment has been minimized.
This comment has been minimized.
@takaxp Thanks. I read about PS: |
added a commit
that referenced
this issue
Sep 6, 2018
This comment has been minimized.
This comment has been minimized.
@alphapapa Would you like to make this a reality? I have just added tests marked as |
added a commit
that referenced
this issue
Sep 6, 2018
added a commit
that referenced
this issue
Sep 6, 2018
This comment has been minimized.
This comment has been minimized.
Some initial work in https://github.com/kaushalmodi/ox-hugo/tree/logbook. Exporting the "Parsing notes from LOGBOOK" tests prints this:
|
This comment has been minimized.
This comment has been minimized.
Hi Kaushal,
Well, I don't actually use Hugo (yet?), and I don't have much experience with org-export code, so I probably won't be contributing any patches--at least, not unless I actually start using this. :) I just wanted to toss the idea out there in case you thought it was worth doing, because it's a feature I would like to use myself. Thanks. |
This comment has been minimized.
This comment has been minimized.
Got it. :) I thought you would be a good candidate as I was stumbling through this initial commit for parsing logbook: 7872a01 .. In any case, thanks for suggesting logbook notes.. I think I can use those to replace my "update" Org macros: |
This comment has been minimized.
This comment has been minimized.
Maybe so! I actually found that code very interesting, how you used 4 lambdas nested with
Yep, that's exactly what I was thinking it would be useful for! |
alphapapa commentedSep 6, 2018
Hi Kaushal,
Reading about ox-hugo again, and thinking about giving it a try, I thought I would post this idea that I was thinking about last night, which I'd like to have in my "ideal" Org blogging engine:
I'd like the
:LOGBOOK:
drawer to act as a log of changes for each post. e.g. if I updated a post that was already published, I could useorg-add-log-note
(C-c C-z
) to make a note, like "Updated link and corrected typos." Then when I republished or reexported the blog, the note from the logbook would be put in the HTML in the appropriate place, and the last-modified timestamp would be taken from the most recent logbook entry.Also, quick question: Is it possible to set up ox-hugo so that only posts with a certain to-do keyword are published? The workflow I was thinking of was to have
TODO
entries be ideas for posts, another keyword for drafts, and aPUBLISHED
keyword (configured as a "done" keyword in Org) for posts I want to be published.Thanks.