From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87558 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: any partial or rudamentary documentation of new nnselect work somewhere? Date: Sun, 14 May 2017 10:48:55 +0800 Message-ID: <87a86gb1bc.fsf@ericabrahamsen.net> References: <86r301wqx2.fsf@local.lan> <87y3u9bk86.fsf@hanan> <867f1oxwsb.fsf@local.lan> <87fugcz2fu.fsf@hanan> <86o9uzwnh4.fsf@local.lan> <87a86ioosl.fsf@ericabrahamsen.net> <86fug8vpl5.fsf@local.lan> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1494730240 3328 195.159.176.226 (14 May 2017 02:50:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 14 May 2017 02:50:40 +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+m35773@lists.math.uh.edu Sun May 14 04:50: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 1d9jc8-0000fQ-W5 for ding-account@gmane.org; Sun, 14 May 2017 04:50: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 1a89ddd5-3850-11e7-b087-b499baabecb2; Sun, 14 May 2017 02:50:36 +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 1d9jbL-0005P2-RO; Sat, 13 May 2017 21:49:43 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1d9jbI-0005OM-VR for ding@lists.math.uh.edu; Sat, 13 May 2017 21:49:41 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1d9jbH-0005od-OO for ding@lists.math.uh.edu; Sat, 13 May 2017 21:49:40 -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 1d9jbG-0003DN-Al for ding@gnus.org; Sun, 14 May 2017 04:49:38 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d9jb5-0007in-U3 for ding@gnus.org; Sun, 14 May 2017 04:49:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:NzdAFzsUFZwru1H7b/SvMLLRZEQ= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87558 Archived-At: Harry Putnam writes: > You would know vastly more than I about the capabilities of any of the > search tools available now. But I believe you are right in thinking > they would not index code very well at all. "Vastly" is an overstatement :) But I think we can assume it's not going to work. [...] >> That sounds pretty useful. Maybe there's no need for a mixin class at >> all; this could be a standard feature of the indexed search class. If >> grep wasn't available on the system, you'd just get a polite note to >> that effect. > >> Actually, there's already a regexp syntax: surrounding text with forward >> slashes. Search engines that don't handle regexps could simply transform >> "body:/(.*)/" into "grep:(.*)"... >> >> Hmmm... > > Yes, yes, and away you go... That two phase bit sounds really > useful. I am really sorry to be of no help at all. > > If you fellows have any low level scut work that needs doing, and I do > mean `low level'... that is, no coding required. > > I realize that is a piss poor offer, and there probably is nothing > like that involved... but still ... just in case .. the offer stands. Thinking about it further, I think automatically translating regexps into "grep:" might be going overboard, and would introduce unnecessary complications. But providing the grep functionality itself still sounds like a good idea. And thanks for the offer of help! It's true there's not a whole lot to be done at this point, just a bit of leftover functionality, then tests and docs. What would be most useful is if someone could explain git better to me so that the rebase process was less bewildering :(