unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Add Denote package
Date: Thu, 23 Jun 2022 17:13:45 +0300	[thread overview]
Message-ID: <87a6a3xyau.fsf@protesilaos.com> (raw)
In-Reply-To: <CADwFkmksPAPP8FKphGM3dpT-vR0YUf+ENddiWRarib41T9e1CA@mail.gmail.com>

> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 23 Jun 2022 11:25:35 +0200
>
>> What do you think?  Can I install the attached patch in elpa.git?
>
> LGTM, but put :url on the same line as the package name to follow the
> same format as other packages.

Thanks!  I have no problem with that.  Though note that my cursory,
fontaine, and tmr packages all have the :url on the subsequent line
(while my others have it on the same line).

>> Do you want me to explain more about this package?
>
> Out of curiosity, and if you find it useful, could you perhaps explain
> your motivation for writing this?  In particular, what are, in your
> view, the key differences to existing packages like org-roam?  Which
> types of users are likely to use this rather than e.g. org-roam?  [To
> be clear, none of these questions would affect its addition to GNU
> ELPA.]

There is a section in the manual which addresses Frequently Asked
Questions while others elaborate on the core principles and related
themes.  But since we are here this is an overview:

* My motivation for every package I write is to (i) solve a problem I
  have and/or implement a workflow I want, (ii) learn Emacs Lisp
  (programming in general) in a fun way through trial and error.

* The existence of PACKAGE is never a good reason for me not to try my
  own.  When the question arises of "why not contribute to PACKAGE
  instead?" the answer is that without me experimenting in the first
  place, I would lack the skills for such a task.  Furthermore,
  contributing to another package does not guarantee I get what I want
  in terms of workflow.

* To me, Denote streamlines tasks I was performing from my pre-Emacs
  days (before the summer of 2019) and later through an Elisp toy
  package I wrote (I can share the link, if you are curious).
  Specifically how files in my long-term storage are named and how notes
  are written as small files in a flat directory.

* I never used org-roam and am thus not fit to answer your question.
  What follows is purely subjective and constitutes no comparison
  between the two packages.  Its requirement for Org was reason enough
  for me not to try it.  I personally do not want to use Org for my
  notes (not unless necessary) on the premise that fewer features help
  me focus on the only task that matters: writing---and I write a lot.
  Added markup, to-do tracking, clocking time, org-babel, tables with
  formulas, multiple headings with property drawers, section
  folding... These are all wonderful features for the right task, such
  as the README.org of Denote, but not when all I want is pure text.
  For me, a restricted environment removes the temptation to add such
  constructs and thus boosts my productivity.  These extras also lock me
  into Emacs, whereas I want my notes to be accessible at all times.

* About which types of users may want to try Denote, it must be those
  who (i) see a value in the file-naming scheme that Denote implements
  as explained at length in the manual, (ii) want the flexibility to
  write notes in other file types beside Org and/or enjoy the
  flexibility the 'denote-type' command offers of picking the file type
  on demand.

-- 
Protesilaos Stavrou
https://protesilaos.com



  reply	other threads:[~2022-06-23 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  3:52 [ELPA] Add Denote package Protesilaos Stavrou
2022-06-23  9:25 ` Stefan Kangas
2022-06-23 14:13   ` Protesilaos Stavrou [this message]
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=87a6a3xyau.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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).