From: Xinglu Chen <public@yoctocell.xyz>
To: zimoun <zimon.toutoune@gmail.com>, Andrew Tropin <andrew@trop.in>,
50077@debbugs.gnu.org
Subject: [bug#50077] [PATCH v2 3/3] gnu: Add emacs-notmuch.
Date: Tue, 14 Sep 2021 21:20:31 +0200 [thread overview]
Message-ID: <87y27zrmkg.fsf@yoctocell.xyz> (raw)
In-Reply-To: <861r5rtbji.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
On Tue, Sep 14 2021, zimoun wrote:
> Hi,
>
> On Tue, 14 Sep 2021 at 17:29, Xinglu Chen <public@yoctocell.xyz> wrote:
>> On Tue, Sep 14 2021, Andrew Tropin wrote:
>>> On 2021-09-04 11:42, Xinglu Chen wrote:
>
>>> Not sure if we need to hardcode the path to notmuch binary (some people
>>> can use guix for managing emacs packages, but not system), but I think
>>> it's a rare case and this default is reasonable and easily fixable by
>>> simple `(setq notmuch-command "notmuch")` in the cases, when notmuch
>>> itslef provided by other package manager.
>>
>> Yeah, this default should work for most people, and as you said, people
>> who haven’t installed Notmuch via Guix can just set to the
>> ‘notmuch-command’ to the appropriate value. It’s Emacs after all... ;-)
>>
>> Also, since there was a consensus that Emacs packages that were included
>> in “regular” packages should be packaged as separate ‘emacs-’ packages,
>> I think it would be a good idea to add a paragraph about that in the
>> manual.
>
> I agree. For references, this question appears here:
>
> <http://issues.guix.gnu.org/issue/49457>
> <http://issues.guix.gnu.org/issue/50231>
>
> so it seems something is missing in the manual. :-)
Just sent a patch for it. :-)
<https://issues.guix.gnu.org/issue/50589>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-09-14 19:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 14:10 [bug#50077] [PATCH 0/3] Various improvements to Notmuch Xinglu Chen
2021-08-16 14:12 ` [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output Xinglu Chen
[not found] ` <87o89owoi0.fsf@trop.in>
2021-08-28 10:34 ` Xinglu Chen
2021-08-30 7:14 ` Andrew Tropin
2021-08-30 13:33 ` [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.) Xinglu Chen
2021-09-01 9:50 ` Andrew Tropin
[not found] ` <874kb4lcvf.fsf@yoctocell.xyz>
[not found] ` <456243eca955ecc83b26663ed4e7e22d5170f03d.camel@student.tugraz.at>
[not found] ` <87sfynq2xm.fsf@zancanaro.id.au>
2021-09-03 16:14 ` Xinglu Chen
2021-08-16 14:12 ` [bug#50077] [PATCH 2/3] gnu: notmuch: Build Info manual Xinglu Chen
2021-08-16 14:12 ` [bug#50077] [PATCH 3/3] gnu: notmuch: Use 'cc-for-target' instead of hardcoding 'gcc' Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 0/3] Improvements to Notmuch Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 1/3] gnu: notmuch: Build Texinfo manual Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 2/3] gnu: notmuch: Make cross-compilable Xinglu Chen
2021-09-04 9:42 ` [bug#50077] [PATCH v2 3/3] gnu: Add emacs-notmuch Xinglu Chen
2021-09-14 7:22 ` Andrew Tropin
2021-09-14 15:29 ` Xinglu Chen
2021-09-14 15:35 ` zimoun
2021-09-14 19:20 ` Xinglu Chen [this message]
2021-09-14 7:05 ` bug#50077: [PATCH v2 0/3] Improvements to Notmuch Nicolas Goaziou
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y27zrmkg.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=50077@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=zimon.toutoune@gmail.com \
/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/guix.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).