Go to file
Lucien Cartier-Tilet 1a4c2c6bb9
Add issue templates for Github
2022-09-07 10:29:24 +02:00
.github Add issue templates for Github 2022-09-07 10:29:24 +02:00
.dir-locals.el Update CONTRIBUTING and dir variables 2022-09-07 10:21:16 +02:00
.gitignore Add gitignore 2022-08-24 03:27:27 +02:00
CONTRIBUTING.org Fix links in CONTRIBUTING 2022-09-07 10:26:02 +02:00
Eask Update Eask information 2022-08-24 18:33:56 +02:00
LICENSE.md Change some function names, add README, LICENSE and CONTRIBUTING 2021-06-15 18:32:21 +02:00
Makefile Add CI 2022-08-24 03:27:27 +02:00
README.org Add MELPA badges 2022-09-04 14:34:03 +02:00
org-unique-id.el Bump to version 0.4.1 2022-09-07 10:21:16 +02:00



https://github.com/Phundrak/org-unique-id/actions/workflows/workflow.yml/badge.svg https://melpa.org/packages/org-unique-id-badge.svg https://stable.melpa.org/packages/org-unique-id-badge.svg


org-unique-id is a utility package for org users that are tired dealing with random org IDs for their headers that change on each org to HTML export (and other kinds of exports). This package creates meaningful custom IDs for org headers that wont change unless the user modifies them manually.


This package can be installed like any other simple package. Your first option is to download org-unique-id or clone this package in your load-path and add the following to your configuration:

(require 'org-unique-id)
(add-hook 'before-save-hook #'org-unique-id-maybe)

You can also use a package manager such as Quelpa or Straight in order to load automatically your package. In my case, I prefer the latter with its use-package integration:

(use-package org-unique-id
  :require t
  :after org
  :straight (org-unique-id :type git
                           :host github
                           :repo "Phundrak/org-unique-id")
  :init (add-hook 'before-save-hook #'org-unique-id-maybe))

I personally add :build t to my straight recipe to ensure my package is compiled.

If you know how to handle this with a pure Straight recipe, or with a Quelpa recipe, dont hesitate to submit a PR to add it to this README!


While org-unique-id may be installed on your Emacs instance, it is not active by default. This is because it can take some time to generate all the required IDs in your org file which may hang your Emacs instance for a bit. Therefore, automatic IDs are enabled on a per-file basis with the option unique-id.

Here is an example of an org buffer with org-unique-id enabled:

#+title: Test file
#+options: unique-id:t

* Test level 1
:CUSTOM_ID: Test-level-1-zmb40t305kj0
** Test level 2
:CUSTOM_ID: Test-level-1-Test-level-2-spn40t305kj0
* Test level 1
:CUSTOM_ID: Test-level-1-1nx40t305kj0

The CUSTOM_ID properties are generated on save and only once. Once the CUSTOM_ID of a heading is set, the package will not modify it even if the name of the heading itself is modified. To regenerate it, delete the CUSTOM_ID and let org-unique-id regenerate it. If you dont like the CUSTOM_ID generated by org-unique-id, you can overwrite it yourself and org-unique-id will not modify it.

Note that unique-id:t is absolutely required in order to get these CUSTOM_ID. Here is the same buffer after save without this option:

#+title: Test file
* Test level 1
** Test level 2
* Test level 1

It is also possible to manually call org-unique-id (interactively or not) on the current buffer. This will not check the value of the unique-id option.

Breaking changes


The option auto-id is renamed to unique-id.


org-unique-id is available under the GNU GPL-3.0 license. You can find the full text in LICENSE.md.