unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: "emacs-devel" <emacs-devel@gnu.org>
Subject: [ELPA] Add Denote package
Date: Thu, 23 Jun 2022 06:52:26 +0300	[thread overview]
Message-ID: <871qvgc9z9.fsf@protesilaos.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

Hello everyone,

I have a new package that I would like to contribute to the FSF via GNU
ELPA.  It is called "denote" and aims to be a simple tool for taking
notes in a flat directory using a strict and efficient file-naming
scheme.  Denote provides the means to create links between notes and can
produce a buffer with backlinks to the current one ("backlinks" are the
links in other notes pointing to the present entry).

Denote creates Org files by default, but there is an option to use plain
text (.txt) or Markdown with either YAML or TOML notation for the file's
front matter (the area at the top with the tile, date, tags).

The webpage of the manual: <https://protesilaos.com/emacs/denote>.  It
is comprehensive and covers everything one needs.

I have received patches from Damien Cassou (FSF-covered), Kaushal Modi
(FSF-covered), and Jack Baty (small; below the threshold).

What do you think?  Can I install the attached patch in elpa.git?  Do
you want me to explain more about this package?  Something else to
consider?

[ I will tag a release once the patch is installed. ]

All the best,
Protesilaos (or simply "Prot")

-- 
Protesilaos Stavrou
https://protesilaos.com

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-elpa-packages-denote-New-package.patch --]
[-- Type: text/x-patch, Size: 925 bytes --]

From 3e4dfef1afcd84eb440cfcd4ac568e59702ec6b8 Mon Sep 17 00:00:00 2001
Message-Id: <3e4dfef1afcd84eb440cfcd4ac568e59702ec6b8.1655954849.git.info@protesilaos.com>
From: Protesilaos Stavrou <info@protesilaos.com>
Date: Thu, 23 Jun 2022 06:27:04 +0300
Subject: [PATCH] * elpa-packages (denote): New package

---
 elpa-packages | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/elpa-packages b/elpa-packages
index 2bfb8f3cae..e072b035c5 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -183,6 +183,11 @@
  ("debbugs"		:url nil :doc ("debbugs.texi" "debbugs-ug.texi"))
  ("delight"		:url "https://git.savannah.gnu.org/r/delight.git"
   :auto-sync t)
+ ("denote"
+  :url "https://git.sr.ht/~protesilaos/denote"
+  :auto-sync t
+  :doc "README.org"
+  :ignored-files ("COPYING" "doclicense.texi"))
  ("detached"		:url "https://git.sr.ht/~niklaseklund/detached.el"
   :news "CHANGELOG.org"
   :readme "README.md"
-- 
2.36.1


             reply	other threads:[~2022-06-23  3:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  3:52 Protesilaos Stavrou [this message]
2022-06-23  9:25 ` [ELPA] Add Denote package Stefan Kangas
2022-06-23 14:13   ` Protesilaos Stavrou
2022-06-27  9:55     ` Stefan Kangas
2022-06-27  3:02 ` Protesilaos Stavrou
2022-06-27  8:47   ` Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qvgc9z9.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=emacs-devel@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).