From: Firmin Martin <firminmartin24@gmail.com>
To: Adam Plaice <plaice.adam+notmuch@gmail.com>,
David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Bug: Unrecognized option: --sort=newest-first
Date: Fri, 06 Aug 2021 14:06:00 +0200 [thread overview]
Message-ID: <87eeb622xj.fsf@gmail.com> (raw)
In-Reply-To: <CAJw81daM_VBMtxZ410M=F9kZWRD7Qc+32xZSXTRAeaTVBzE0MQ@mail.gmail.com>
Adam Plaice <plaice.adam+notmuch@gmail.com> writes:
> I'm not a notmuch developer, but I think that the point is that if
> you're using "unstable" MELPA (i.e. not Stable MELPA), then your emacs
> package will be based on the latest development version (tip of git
> master). If you've built the notmuch binary from a release, then the
> notmuch binary and the emacs package won't be in sync.
>
> The latest development version of notmuch does have a sort option:
>
> https://git.notmuchmail.org/git?p=notmuch;a=commit;h=32f42581e35ee0ebdd89c4cb44292e7979dc5eb7
>
> but it hasn't yet been included in any "released" version of notmuch.
>
>
> If you use use-package, then I'd recommend adding MELPA stable to your
> package-archives and pinning notmuch to melpa-stable:
>
> (use-package notmuch :pin melpa-stable)
>
> It won't solve the issue of notmuch-emacs being out of sync with
> repository packages (at least not on stable distros), but it will make
> it easier to keep up with from-source binary builds (or binaries from
> Nix/Guix if you use that).
Ah, that's make a lot of sense. Thanks, Adam.
I Will opt for that solution.
Also thank you David, I didn't understand immediately your reply.
Have a good day,
Firmin
prev parent reply other threads:[~2021-08-06 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 8:56 Bug: Unrecognized option: --sort=newest-first Firmin Martin
2021-08-06 10:16 ` David Bremner
2021-08-06 10:32 ` Firmin Martin
2021-08-06 11:45 ` Adam Plaice
2021-08-06 12:06 ` Firmin Martin [this message]
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=87eeb622xj.fsf@gmail.com \
--to=firminmartin24@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=plaice.adam+notmuch@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://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).