Closed xeruf closed 2 years ago
Also added copying css to get a functional page by default.
I'd accept one of those patches. So if you get rid of the other, I can merge. I don't know if Github allows me to merge one of your two patches while ignoring the other.
Ah, I was not aware that the datestamp is cut away. Well then we could change it to a fictional date to make that clear, like 0000-00-00
, hm?
You can add my repo as remote and cherry-pick it :)
Ah, I was not aware that the datestamp is cut away. Well then we could change it to a fictional date to make that clear, like
0000-00-00
, hm?
Yes, that is a possibility although I don't care to do so because the datestamp is cut in all IDs, not only persistent ones. So it really doesn't matter if and which date-stamp you're using there. That's not special for that particular heading, that's a generic behavior of lazyblorg to be able to work with unique IDs and sill get generic URLs.
You can add my repo as remote and cherry-pick it :)
Ah, I may play around with that idea some day.
Alternatively we could make the id more specific like about-this-blog
so there is no duplication.
Btw, do you have any reference how you generate org-ids? I always work with custom ids and org tends to be a bit reluctant about that ;)
Alternatively we could make the id more specific like
about-this-blog
so there is no duplication.
That would still potentially interfere with use-cases where one person does maintain two different lazyblorg setups in parallel. In general, you're right: the convention to name persistent default pages could be a different one.
Btw, do you have any reference how you generate org-ids? I always work with custom ids and org tends to be a bit reluctant about that ;)
You should read https://github.com/novoid/dot-emacs/blob/master/config.org and look for all occurrences of my-id-get-or-generate
which I'm using to generate IDs most of the time. For lazyblorg articles, I tend to write them manually in order to make the URL path as short as possible and as expressive as possible.
the timestamps in the id don't make sense for such persistent entries