[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNU ELPA] Denote version 0.5.1
[GNU ELPA] Denote version 0.5.1
Wed, 10 Aug 2022 17:03:10 -0400
Version 0.5.1 of package Denote has just been released in GNU ELPA.
You can now find it in M-x package-list RET.
Denote describes itself as:
Simple notes with an efficient file-naming scheme
More at https://elpa.gnu.org/packages/denote.html
CHANGE LOG OF DENOTE
This document contains the release notes for each tagged commit on the
project's main git repository: <https://git.sr.ht/~protesilaos/denote>.
The newest release is at the top. For further details, please consult
the manual: <https://protesilaos.com/emacs/denote>.
Version 0.5.0 on 2022-08-10
The general theme of this release is to refine what we already offer.
As I explained in some discussions, Denote is feature-complete. We
can always improve the code or add some ancillary
function/command/variable, though all the main ideas have already been
implemented. Additional functionality can be provided by other
packages: I remain at the disposal of anyone willing to write such a
The present release covers more than 150 commits since version 0.4.0
All release notes: <https://protesilaos.com/emacs/denote-changelog>.
Templates for new notes
We now provide the `denote-templates' user option. A "template" is
arbitrary text that Denote will add to a newly created note right
below the front matter.
Templates are expressed as a `(KEY . STRING)' association.
• The `KEY' is the name which identifies the template. It is an
arbitrary symbol, such as `report', `memo', `statement'.
• The `STRING' is ordinary text that Denote will insert as-is. It can
contain newline characters to add spacing. The manual of Denote
contains examples on how to use the `concat' function, beside
writing a generic string:
The user can choose a template either by invoking the new command
`denote-template' or by changing the user option `denote-prompts' to
always prompt for a template when calling the `denote' command.
Thanks to Jean-Philippe Gagné Guay for refinements to this facility.
Done in pull request 77 on the GitHub mirror:
[ Jean-Philippe has assigned copyright to the Free Software
Revised format for Org `#+filetags' entry
Denote used to format tags in Org files by separating them with two
│ #+filetags: tag1 tag2
While this worked for some obvious use-cases, it is not supported by
Org. The Org documentation stipulates that tags be separated by the
colon sign. The above would then be written thus:
│ #+filetags: :tag1:tag2:
Denote now conforms with Org's specifications. To help users update
their existing notes, we provide the `denote-migrate-old-org-filetags'
command. It will perform the conversion in all Org files that had the
old notation. As with all Denote operations that rewrite file
contents, it DOES NOT SAVE BUFFERS. The user is expected to review
the changes, such as by using `diff-buffer-with-file'. Multiple
buffers can be saved with `save-some-buffers' (check its doc string).
This command is provided for the convenience of the user. It shall be
deprecated and eventually removed from future versions of Denote.
If you need help with any of this, please do not hesitate to contact
me either in private or in one of Denote's official channels (mailing
list, GitHub/GitLab mirror).
Thanks to Alan Schmitt for bringing this matter to my attention:
Also thanks to Jean-Philippe Gagné Guay for commenting on it as it
helped me decide to include the command in `denote.el':
Revised format for Markdown+YAML `tags:' entry
:PROPERTIES: :CUSTOM_ID: h:205a09cf-0159-425e-a6b3-41700fa3ad31 … …
|[Prev in Thread]
||[Next in Thread]|
- [GNU ELPA] Denote version 0.5.1,
ELPA update <=