From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1561 invoked from network); 11 Jul 2021 03:22:17 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 11 Jul 2021 03:22:17 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1m2Q2o-001UWd-2v for ml@inbox.vuxu.org; Sat, 10 Jul 2021 22:22:14 -0500 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94) (envelope-from ) id 1m2Q2n-0089MX-J6 for ml@inbox.vuxu.org; Sat, 10 Jul 2021 22:22:13 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1m2Q2l-0089MP-He for ding@lists.math.uh.edu; Sat, 10 Jul 2021 22:22:11 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1m2Q2i-001UWF-9Y for ding@lists.math.uh.edu; Sat, 10 Jul 2021 22:22:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=XxhUNPUwGq76R8PBDUk2uLlXRWT57TgU4O9NmvL903Y=; b=B/F2LgNQxJxNJkBjdSZJnHAlJe lZQ2qenOJlLf6EePmnah71UBTPWdb9274o7TjSSPHapk2undNpSiYbDtHU/mMYJoJ5oBcV9BIij29 Tb8wyaQLAV5vTeST+t67wNm8ld1leA+Vf3qPDM8RkmgfaTVw8qJEQHPls+uxf16IGNmw=; Received: from mail.ericabrahamsen.net ([52.70.2.18]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m2Q2a-0005MV-FT for ding@gnus.org; Sun, 11 Jul 2021 05:22:03 +0200 Received: from localhost (c-71-197-184-122.hsd1.wa.comcast.net [71.197.184.122]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 8640CFEB2F; Sun, 11 Jul 2021 03:21:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1625973715; bh=XxhUNPUwGq76R8PBDUk2uLlXRWT57TgU4O9NmvL903Y=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=yFKcK+0bW2sLBHaNtDUoY7RS4pZEz0i2KsY0aojdChSuFXhRGxso7foBniG6S2bhG Ev6wAlRV5Tk6iN30F4zGf0AT+rot3aux4xJ+mHdifHN/FwvTdkOPBYvqM65K/zygM4 gh/iJc7JOBZzWJYP3sB3eFqwJz0kbNpep1Iz0mL0= From: Eric Abrahamsen To: "Jose A. Ortega Ruiz" Cc: ding@gnus.org Subject: Re: is it possible to search by list-id? References: <875yxllhkr.fsf@gnus.jao.io> <87a6mxlzen.fsf@ucl.ac.uk> <87sg0oj38s.fsf@gnus.jao.io> <87eec8it4j.fsf@gnus.jao.io> <8735sn3qw5.fsf@gnus.jao.io> Date: Sat, 10 Jul 2021 20:21:44 -0700 In-Reply-To: <8735sn3qw5.fsf@gnus.jao.io> (Jose A. Ortega Ruiz's message of "Sat, 10 Jul 2021 02:21:30 +0100") Message-ID: <874kd11qnr.fsf@ericabrahamsen.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: Precedence: bulk "Jose A. Ortega Ruiz" writes: > it seems to be possible to make this word (at least for searches backed > by dovecot's fts) simply with: > > (add-to-list 'gnus-search-expandable-keys "list-id") > > that is makng the error parsing the query go away, and transforming to > the spec ((list-id . "foo")), which in turn dovecot's IMAP search engine > seems to like. > > not sure if this is intended behaviour, but, as they say, > se non =C3=A8 vero, =C3=A8 ben trovato! :) No, this was a misunderstanding about how `completion-all-completions' works, the queries are definitely meant to pass unknown keywords straight through to the underlying engine. I've patched this now, and added new tests to prevent regression. Thanks for pointing it out! Eric