From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id AMkzJvAgDWH2BQAAgWs5BA (envelope-from ) for ; Fri, 06 Aug 2021 13:45:52 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id iCjsIfAgDWHycQAAB5/wlQ (envelope-from ) for ; Fri, 06 Aug 2021 11:45:52 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 1C8EA1C12A for ; Fri, 6 Aug 2021 13:45:52 +0200 (CEST) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id CCFF9291FA; Fri, 6 Aug 2021 07:45:48 -0400 (EDT) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) by mail.notmuchmail.org (Postfix) with ESMTPS id 0B299291F8 for ; Fri, 6 Aug 2021 07:45:46 -0400 (EDT) Received: by mail-lj1-x22c.google.com with SMTP id l4so11524502ljq.4 for ; Fri, 06 Aug 2021 04:45:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LU9Mii78EE/6ItmDEjKzxUdKFQ2g/5B4lXVFIrdKxfo=; b=Zq9+F1YafNQp5NUEoBv0YwMjZsl1HbVZ77UboE9+/9dNeeNgDRFrQPAEliweXe1f9m 5ZH2FCNW0A0FCer9jbujHZlNuoWURVZ9qv2uu2Df0qBMNYRu8ZgsOkSqqAMqCJbl2luw lDqeKWin+C3rgeAdPmNQJiA6uL7/PA4pF+CxUMMM6HppN106ots23XDlsm1P8S5wRMYM nbFmRX3ZTZgFJRaMw3JYwxJhwsZbJ0+z5yLdfCsolAeQL35YZL552/q4heULYw1EMf5S lEDcndsGCJt9YiHrYqcCJNKWkYv+vPdQE9e1Tv16GxhmHnoQuaI0+u9REb+Yc6Bcyn1l 1UxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LU9Mii78EE/6ItmDEjKzxUdKFQ2g/5B4lXVFIrdKxfo=; b=ZQ2ktgcw2RvW3o84aKGfRvLUQ3vMY4FRsc+WYzhYr3xVKeAJCiE3tZhzbe6MjZcXs4 nrhwnzgVQRiTWuRqeUiFdzHxlmEa6Rqvo4e7r8WcdIjqsVgzdUVIgaf/DsMOSqD4xmJM Q2BP1mLODxmYs1QY5kjp2kuWChfcmfeZ+2QXtefrgJbaRuljn/88XqNw/mwDvw6tHIEM gG9rm+aBiGMbgkGNF2UwoilDkhsIopIq6jvzW/TryUoJB2UekdAfK+CmrLBUEKXgCaMk l5yLpg72a/FQF5+xNEHzgTmnk72UXTzraS+Tnt9zHR/ZhbLTiyNAF1FcnmjsLJv6PMI9 oxIA== X-Gm-Message-State: AOAM5323kC9UFt0ZT4UPoY+BNGjTD0aLPUxfkVHe02DK7TM9InkJAgZE yWfzrFGc2BIROT+q5wUEGIgYLKOZeE1aXp4tsEw= X-Google-Smtp-Source: ABdhPJyYFYCbfCeoxkXzfofh+YunMP82wkPzKDjHlA4dKHMP6pD3F2DP3RcKLL2558XIXD/qz0lXU+QkEpxY/aswWKo= X-Received: by 2002:a2e:a44f:: with SMTP id v15mr6122839ljn.301.1628250344294; Fri, 06 Aug 2021 04:45:44 -0700 (PDT) MIME-Version: 1.0 References: <87tuk36jex.fsf@gmail.com> <87pmuqvpww.fsf@tethera.net> <87h7g2279z.fsf@gmail.com> In-Reply-To: <87h7g2279z.fsf@gmail.com> From: Adam Plaice Date: Fri, 6 Aug 2021 13:45:32 +0200 Message-ID: Subject: Re: Bug: Unrecognized option: --sort=newest-first To: Firmin Martin Message-ID-Hash: SJUUTGNOLREC3RGVSIVZIPZM5MMKXF2W X-Message-ID-Hash: SJUUTGNOLREC3RGVSIVZIPZM5MMKXF2W X-MailFrom: plaiceadam@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: notmuch@notmuchmail.org X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1628250352; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=AdSGd40eY9cQjkRXpAJPH6ortqR6XqSAzNb7lgVW6YE=; b=m74gwQCPL7h8qGHmglfybmpK6MvqoWaNqplWGQ1g3thOE+zCHgvqBeLHv2IrTqFixOCW9d QMi4cwj+AGi8fUIgC5DHtbW8qHClY4i4d18EbCJGc4xNMT4EJ/AYU7RTlw0RsT/HBJ0XkX /TYv9riFhXSCvxotFeYyaNFDUtMKKavEPkFX5obOFBR4JqL+LwzcOKvn2R+jrqavVMEo+P imTArYRc2+H7/t71i6MzKryi1oo8PpHw/A8dDcqNOVUt3HHMLWYvnkWTExMYdJ1b6tAAtP 68byxG2iSPuyFB3ExoXxLYn1xJl9Dn3ZZ49k2KWd1KOm3MlBUNmOB/U08AHflg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1628250352; a=rsa-sha256; cv=none; b=aNvcCMsAIXgOQlBGtx0hZ8qRznPbgGKXkuyH7LtumbeXbELTYg6dlVZR5fuIZZeCL73/hN E35/azRfg0nPhqVu4IU8dbOUfmKt+K/OFd3ZqhkDnOyQwMed1EAGUl+7DRXfDQuYXcYjTP QrhOBb6w7VhMTQPE3NuCFMRpUCMYtqPG6OykVowVVC0pnqYTqsGTv8uvdpiC8zRttqz2PO eyoYCKRLOQfqQs796ZmdK0l8qIWsYM8kjQlzuvS7DtWIk4/8yUhcrvCJeoFlP1E8oLga6o hfZ0Xg8OMf8levyqU4/C3SlA5fJybXkR9G2HY+hP9idojmIz5E/+wyMRpHk1hg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=Zq9+F1Ya; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: -0.90 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=Zq9+F1Ya; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: 1C8EA1C12A X-Spam-Score: -0.90 X-Migadu-Scanner: scn0.migadu.com X-TUID: rqbGyFTHsoYY > > Yep. If you choose to use MELPA, you need to (somehow) keep the notmuch > > binary in sync. > > Yeah, that's exactly what I've done. And the bug is unrelated to the > binary: it's in the notmuch-tree function (see the lower part of the bug > report). 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). Adam