From: Tomi Ollila <tomi.ollila@iki.fi>
To: <zack@debian.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [Stefano Zacchiroli] Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
Date: Mon, 26 Mar 2012 15:34:04 +0300 [thread overview]
Message-ID: <m2aa33o81v.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87ehsfr6lb.fsf@zancas.localnet>
Interesting, 'R' in emacs gives empty content. I might have Austin's
reply change in this version -- although I suspect the problem is not
there. Everyone using emacs MUA with latest notmuch(1)es experiment
pressing 'R' while reading the mail I'm replying to
Pasting content...
> [ multipart/mixed ]
> [ message/rfc822 ]
> From: Stefano Zacchiroli <zack@debian.org>
> Subject: Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/
> To: 628018@bugs.debian.org
> Date: Mon, 26 Mar 2012 11:36:06 +0200
>
> [ multipart/signed ]
> [ Good signature by key: 0x4900707DDC5C07F2DECB02839C31503C6D866396 ]
> [ multipart/mixed ]
> [ text/plain ]
> Here is an updated patch set that ships the notmuch-mutt utility and
> updated the Debian packaging for it. It is now better integrated with
> notmuch: it has been renamed to "notmuch-mutt" (to match the naming
> convention of other notmuch interfaces) and stores all its data under
> ~/.cache/notmuch/mutt/ to avoid polluting user $HOME with other
> directories. I've also fixed the Debian packaging to generate the
> manpage during build.
I think storing stuff to .../.cache/... is Great !!!
However, if we're "allowing" public software to use .../.cache/notmuch
directory we should have policy to do so. I suggest we add a description
file to notmuch source distribution which describes the public software
that are allowed to contain files in notmuch XDG directories. The file
could have format which describes the file/directory name, the software
using it and some description why this file is there.
Another thing is this .cache hardcoding. Should this be resolved
first by using $XDG_CACHE_HOME, (then *MAYBE* $XDG_CONFIG_HOME/.cache)
and finally $HOME/.cache
Tomi
>
> The first patch in the set adds notmuch-mutt to contrib/, the second
> updates debian/ to build a new "notmuch-mutt" binary package.
>
> The full story is available at http://bugs.debian.org/628018
>
> David: I'm still unable to get through the moderation queue of the
> notmuch mailing list. Would you be so kind to forward this mail there,
> for patch review?
>
> TIA,
> Cheers.
next prev parent reply other threads:[~2012-03-26 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 10:32 [Stefano Zacchiroli] Bug#628018: [PATCH] mutt-notmuch in notmuch contrib David Bremner
2012-03-26 10:37 ` [Stefano Zacchiroli] Bug#628018: [PATCH] notmuch-mutt utility for notmuch/contrib/ David Bremner
2012-03-26 12:34 ` Tomi Ollila [this message]
2012-03-26 15:09 ` Jameson Graef Rollins
2012-03-26 15:29 ` Stefano Zacchiroli
2012-03-26 18:52 ` Stefano Zacchiroli
2012-03-26 19:03 ` Scott Barker
2012-03-26 21:15 ` Stefano Zacchiroli
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=m2aa33o81v.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@notmuchmail.org \
--cc=zack@debian.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://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).