From: TEC <firstname.lastname@example.org> To: org-mode-email <email@example.com> Subject: [Interest] Determanistic Org IDs Date: Sun, 19 Jul 2020 22:27:31 +0800 [thread overview] Message-ID: <E1jxAjq-0004Dk-LH@lists.gnu.org> (raw) :PROPERTIES: :ID: 1161308a-ef0c-4490-bb36-13634f8de727 :END: User-agent: mu4e 1.4.10; emacs 26.3 Message-ID: <firstname.lastname@example.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Received-SPF: pass client-ip=2607:f8b0:4864:20::102b; email@example.com; helo=mail-pj1-x102b.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -7 X-Spam_score: -0.8 X-Spam_bar: / X-Spam_report: (-0.8 / 5.0 requ) BAYES_00=-1.9,DKIM_ADSP_CUSTOM_MED=0.001,DKIM_INVALID=0.1,DKIM_SIGNED=0.1,FREEMAIL_FROM=0.001,NML_ADSP_CUSTOM_MED=0.9,RCVD_IN_DNSWL_NONE=-0.0001,SPF_HELO_NONE=0.001,SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action Hello everyone, I have an html export of an org file checked into VCS. To try to reduce the 'noise' created by commiting the random org IDs changing each time, I took @alphapapa's unpackaged.el org-export-html-with-useful-ids-mode, tweaked it, and extended it to cover other elements. The end result it that the resulting html export is fully determanistic. While I'm quite pleased with the result, it occured to me that others might be interested in having their exports behave like this. From my usage, these are the percieved pros/cons. Pros: - Reduced 'noise' if exported files are commited - (With HTML) links to particular elements in a file keep working across multiple versions, most of the time - (With HTML) links become more descriptive Cons: - Inceased chance of ID collisions across files Longer IDs I - think this could make a nice option for export settings. I'm - aware of the 9.5 feature freeze, but thought I'd mention the - idea to see if there's any interest in it. If you want to see what I've got happening, see https://tecosaur.github.io/emacs-config/config.html#nicer-generated-heading. Please let me know if this idea seems promising! Timothy.
next reply other threads:[~2020-07-19 14:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-19 14:27 TEC [this message] [not found] <E1jxAkG-00052l-OS@lists.gnu.org> 2020-07-20 3:45 ` TEC [not found] <E1jxAju-0004Dk-3O@lists.gnu.org> 2020-07-24 12:09 ` Alexander Adolf 2020-07-24 14:53 ` TEC
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=E1jxAjq-0004Dk-LH@lists.gnu.org \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Interest] Determanistic Org IDs' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).