From: Jorge P. de Morais Neto <jorge+list@disroot.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Jameson Graef Rollins <jrollins@caltech.edu>,
Tomi Ollila <tomi.ollila@iki.fi>,
notmuch@notmuchmail.org
Subject: Re: moving the config into the database [was: Re: [PATCH] Display extra headers for emacs-mua - db config option]
Date: Tue, 10 Dec 2019 09:46:14 -0300 [thread overview]
Message-ID: <8736ds8i21.fsf@disroot.org> (raw)
In-Reply-To: <87muc18i6d.fsf@fifthhorseman.net>
Hello.
Em [2019-12-09 seg 13:31:22-0500], Daniel Kahn Gillmor escreveu:
> One problem with such a "perennial text file" is that people will want
> to edit it. When they do, what should happen?
Well, the file could be named "notmuch-config-view" and the contents
could include comments explaining it is just a view. Besides, the
generation of such a file could be opt-in.
I hope you don't mind my insistence (it is my personality) and, of
course, there is still the problem of slightly increasing Notmuch's
complexity to provide a small benefit for relatively few people. It is
(obviously) your call, since you understand much more about the Notmuch
codebase (and free/libre software development in general) than me.
Besides, it is not me who am going to actually implement this (I am
unfortunately unable to contribute C code to Notmuch at this moment).
Regards
--
- <https://jorgemorais.gitlab.io/justice-for-rms/>
- I am Brazilian. I hope my English is correct and I welcome feedback.
- Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
- Free/libre software for Replicant, LineageOS and Android: https://f-droid.org
- [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]]
next prev parent reply other threads:[~2019-12-10 12:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 16:27 [PATCH] Display extra headers for emacs-mua - db config option Johan Parin
2019-11-16 16:35 ` Tomi Ollila
2019-11-16 16:53 ` Johan Parin
2019-11-21 2:48 ` Daniel Kahn Gillmor
2019-11-21 12:16 ` David Bremner
2019-11-21 18:29 ` Johan Parin
2019-11-21 21:56 ` Johan Parin
2019-11-22 2:51 ` Daniel Kahn Gillmor
2019-11-22 17:46 ` Carl Worth
2019-11-21 12:27 ` David Bremner
2019-11-21 19:47 ` Daniel Kahn Gillmor
2019-11-21 21:38 ` Tomi Ollila
2019-11-22 2:43 ` moving the config into the database [was: Re: [PATCH] Display extra headers for emacs-mua - db config option] Daniel Kahn Gillmor
2019-12-08 16:47 ` Jorge P. de Morais Neto
2019-12-08 17:12 ` Jameson Graef Rollins
2019-12-08 18:19 ` Jorge P. de Morais Neto
2019-12-09 18:31 ` Daniel Kahn Gillmor
2019-12-10 12:46 ` Jorge P. de Morais Neto [this message]
2019-12-10 17:01 ` Daniel Kahn Gillmor
2019-12-12 11:59 ` Jorge P. de Morais Neto
2019-12-10 16:11 ` Jameson Graef Rollins
2019-12-11 10:53 ` David Edmondson
2019-12-11 14:00 ` David Bremner
2019-12-11 14:21 ` David Edmondson
2019-12-12 16:25 ` Daniel Kahn Gillmor
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736ds8i21.fsf@disroot.org \
--to=jorge+list@disroot.org \
--cc=dkg@fifthhorseman.net \
--cc=jrollins@caltech.edu \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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://yhetil.org/notmuch.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).