From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Concern about new binding. Date: Fri, 12 Feb 2021 12:29:57 +0300 Message-ID: References: <20210202134950.vybbpf3iewbymfjo.ref@Ergus> <20210202134950.vybbpf3iewbymfjo@Ergus> <87zh0mmr54.fsf@gmail.com> <87tuqunw6q.fsf@telefonica.net> <835z3a5miu.fsf@gnu.org> <87pn1f2dlf.fsf@melete.silentflame.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8208"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: ofv@wanadoo.es, eliz@gnu.org, emacs-devel@gnu.org, Sean Whitton To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Feb 12 10:35:43 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAUrW-0001xs-Nx for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Feb 2021 10:35:42 +0100 Original-Received: from localhost ([::1]:32950 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lAUrV-000614-QY for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Feb 2021 04:35:41 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53810) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lAUoh-0004IL-40 for emacs-devel@gnu.org; Fri, 12 Feb 2021 04:32:47 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:56735) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lAUob-0000ha-T1; Fri, 12 Feb 2021 04:32:46 -0500 Original-Received: from localhost ([::ffff:41.202.241.3]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E079.0000000060264B35.00004178; Fri, 12 Feb 2021 02:32:37 -0700 Mail-Followup-To: Richard Stallman , Sean Whitton , ofv@wanadoo.es, eliz@gnu.org, emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:264477 Archived-At: * Richard Stallman [2021-02-07 08:34]: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > > You can do whatever you want. For example, I have an elisp function to > > mute (== any new messages to the thread are marked as read immediately) > > all unread threads I haven't touched, but avoid muting threads where I > > read messages, so I'll see new messages that later come into those > > threads. That's just one example; if you're willing to write the elisp > > you can probably make it happen. > > How would I direct notmuch to recognize all messages which were sent > to bug-gnu-emacs but not emacs-devel, and propose a change in the > Emacs user interface? The second criterion seems to require > humanlike understanding, not text processing. References: https://notmuchmail.org/searching/ Operators Xapian implements the usual operators and a few more that are useful when searching e-mails. Note: The operators need not be capitalized for notmuch, so 'NOT' and 'not' are equivalent. The capitalized form is used below only for readability '+' and '-' notmuch search +term1 will only return results that contain 'term1'. notmuch search -term2 will return results that do not contain 'term2'. '+' and '-' can also be used on bracketed expressions or phrases (see below). AND and NOT notmuch search term1 AND term2 will return results that contain both 'term1' and 'term2'. If no explicit operator is provided all search terms are connected by an implicit AND, so these two searches: notmuch search term1 AND term2 notmuch search term1 term2 are equivalent. notmuch search term1 NOT term2 will return results that contain 'term1' but do not contain 'term2'. For a query that looks more like natural language you can also use AND NOT notmuch search term1 AND NOT term2