[GNU ELPA] Denote version 2.3.2

[ELPA update]

Version 2.3.2 of package Denote has just been released in GNU ELPA.
You can now find it in M-x list-packages RET.

Denote describes itself as:

  =================================================
  Simple notes with an efficient file-naming scheme
  =================================================

More at https://elpa.gnu.org/packages/denote.html

## Summary:

             ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                   DENOTE: SIMPLE NOTES WITH AN EFFICIENT
                             FILE-NAMING SCHEME

                            Protesilaos Stavrou
                            info@protesilaos.com
             ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


  This manual, written by Protesilaos Stavrou, describes the customization
  options for the Emacs package called `denote' (or `denote.el'), and
  provides every other piece of information pertinent to it.

  The documentation furnished herein corresponds to stable version 2.3.0,
  released on 2024-03-24.  Any reference to a newer feature which does not
  yet form part of the latest tagged commit, is explicitly marked as such.

  Current development target is 3.0.0-dev.

## Recent NEWS:

                         ━━━━━━━━━━━━━━━━━━━━━━
                          CHANGE LOG OF DENOTE

                          Protesilaos Stavrou
                          info@protesilaos.com
                         ━━━━━━━━━━━━━━━━━━━━━━


This document contains the release notes for each tagged commit on the
project’s main git repository: <https://github.com/protesilaos/denote>.

The newest release is at the top.  For further details, please consult
the manual: <https://protesilaos.com/emacs/denote>.

Table of Contents
─────────────────

1. Version 2.3.0 on 2024-03-24


1 Version 2.3.0 on 2024-03-24
═════════════════════════════

  This release brings a host of user-facing refinements to an already
  stable base, as well as some impressive new features. There is a lot
  to cover, so take your time reading these notes.

  Special thanks to Jean-Philippe Gagné Guay for the numerous
  refinements to parts of the code base. Some of these are not directly
  visible to users, but are critical regardless. In the interest of
  brevity, I will not be covering the most technical parts here. I
  mention Jean-Philippe’s contributions at the outset for this reason.
  Though the Git commit log is there for interested parties to study
  things further.


1.1 Check out the `denote-explore' package by Peter Prevos
──────────────────────────────────────────────────────────

  This package provides several neat extensions that help you make
  better sense of your knowledge base, while keeping it in good order.
  The `denote-explore' package has commands to summarise the usage of
  keywords, visualise connections between notes, spot infrequently used
  keywords, and jump to previous historical entries.

  • Git repository: <https://github.com/pprevos/denote-explore>.
  • Documentation:
    <https://lucidmanager.org/productivity/denote-explore>.

  Now on to Denote version `2.3.0'!


1.2 Link to a heading inside a Denote Org file
──────────────────────────────────────────────

  Denote creates links to files by using their unique identifier. As Org
  provides the `CUSTOM_ID' property for per-heading identifiers, we now
  leverage this infrastructure to compose links that point to a file and
  then to a heading therein. This only works for Org, as no other plain
  text major mode has a concept of heading identifiers (and it is not
  Denote’s job to create such a feature).

  I demonstrated the functionality in a video:
  <https://protesilaos.com/codelog/2024-01-20-emacs-denote-link-org-headings/>

  Technically, the `denote:' link type has the same implementation
  details as Org’s standard `file:' and has always had this potential to
  jump to a section inside the given file.


1.2.1 The `denote-org-store-link-to-heading' user option
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The user option `denote-org-store-link-to-heading' determines whether
  `org-store-link' links to the current Org heading (such links are
  merely “stored” and need to be inserted afterwards with the command
  `org-insert-link'). Note that the `org-capture' command uses the
  `org-link' internally if it has to store a link.

  When its value is non-nil, `org-store-link' stores a link to the
  current Org heading inside the Denote Org file. If the heading does
  not have a `CUSTOM_ID', it creates it and includes it in the heading’s
  `PROPERTIES' drawer. If a `CUSTOM_ID' exists, `org-store-link' use it
  as-is.

  This makes the resulting link a combination of the `denote:' link
  type, pointing to the identifier of the current file, plus the value
  of the heading’s `CUSTOM_ID', such as:

  • `[[denote:20240118T060608][Some test]]'
  • `[[denote:20240118T060608::#h:eed0fb8e-4cc7-478f-acb6-f0aa1a8bffcd][Some
    test::Heading text]]'

  Both lead to the same Denote file, but the latter jumps to the heading
  with the given `CUSTOM_ID'. Notice that the link to the heading also
  has a different description, which includes the heading text.

  The value of the `CUSTOM_ID' is determined by the Org user option
  `org-id-method'. The sample shown above uses the default UUID …  …