From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87473 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: [RFC] Gnus generalized search, part II Date: Sun, 23 Apr 2017 10:19:01 -0700 Message-ID: <8760hv6nzu.fsf@ericabrahamsen.net> References: <87zif930mt.fsf@ericabrahamsen.net> <871ssji6b2.fsf@uwo.ca> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1492968038 26079 195.159.176.226 (23 Apr 2017 17:20:38 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Apr 2017 17:20:38 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+m35689@lists.math.uh.edu Sun Apr 23 19:20:34 2017 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048035.atla03.us.yomura.com ([107.189.48.35]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d2LBZ-0006cD-KX for ding-account@gmane.org; Sun, 23 Apr 2017 19:20:33 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048035.atla03.us.yomura.com (Halon) with ESMTPS id 2a178119-2849-11e7-b087-b499baabecb2; Sun, 23 Apr 2017 17:20:37 +0000 (UTC) Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.87) (envelope-from ) id 1d2LAo-00026z-JI; Sun, 23 Apr 2017 12:19:46 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1d2LAk-00026R-Ro for ding@lists.math.uh.edu; Sun, 23 Apr 2017 12:19:42 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1d2LAj-00019b-O3 for ding@lists.math.uh.edu; Sun, 23 Apr 2017 12:19:42 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1d2LAf-0000S6-TM for ding@gnus.org; Sun, 23 Apr 2017 19:19:37 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d2LAY-0005G6-6u for ding@gnus.org; Sun, 23 Apr 2017 19:19:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:kATRjLtzDsiJ1jXs445/Xw+0D6c= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87473 Archived-At: Dan Christensen writes: > Looks interesting. Two questions: > > Will mairix be supported? Sure! At least, I think so -- I'm not clear why nnmairix is its own server, rather than being an nnir engine. I think if it's used in raw mode it should work just like the other engines. At any rate, as many engines as possible should be supported. > How do you handle differing capabilities of the search backends? > E.g. mairix supports substring searches, and fuzzy matches, which > are handy if you are looking for a word that might be singular or > plural, or might be a noun or a verb, for example. This is something I haven't figured out yet, and wanted to get feedback from people here. Obviously a lot of engines support regexp/substring/fuzzy searching (even IMAP with the FUZZY capability), but I haven't come up with a good way of indicating that yet. I guess two distinct things need to be supported: regexps, and substring matches. Off the top of my head we could do: "subject:/cat(ch?)/" for regexp: forward slashes around the string. "subject:cat*" for substrings: a leading or trailing asterisk. Engines that can't handle regexp would be required to ignore them -- they would never make sense. Engines that can do substrings would transform the asterisks appropriately; engines that can't would just drop the asterisk and hope. What do you think? Eric