From: George McNinch <gmcninch@gmail.com>
To: ding@gnus.org
Subject: Re: nnir + namazu: always <= 999 matches ? ANS: commas!
Date: Thu, 06 Mar 2014 12:13:16 -0500 [thread overview]
Message-ID: <82iorr1c9f.fsf@chipmunk-via-gmail.com> (raw)
In-Reply-To: <82siqws54k.fsf@jazz-via-gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
Earlier, I wrote:
gm> I have some nnml groups, and I've configured nnir for use with
gm> the namazu engine. For any search, the ephemeral groups produced
gm> by nnir seem to contain no more than 999 matches even when
gm> namazu gets more hits than 999, and I'm not sure how to override
gm> that max.
Aha, I finally noticed that the *nnir* buffer had entries like:
,----
| 1,402. Re: Your message of Mon, 3 Nov 1997 15:44:21 -0500 (score: 2)
| /home/george/Mail/mathematics/135 (2,723 bytes)
`----
Note the *comma* in 1,402.
The regexp matching these entries did not allow for this comma, which
explains hit-counts being always <= 999.
The "hit number" that has the comma in it isn't actually used anywhere,
so there seems to be no harm to just include the possible comma in the
regexp.
Maybe there is some way to tell namazu not to emit commas when counting
past 1000, but I didn't see how in the man page.
Here is a patch for nnir.el fixing the regexp in nnir-run-namazu, though
I wasn't quite sure how I ought to "make the patch correctly" so that
someone can easily put the fix in the git archive. It is anyhow a simple
change.
[-- Attachment #2: nnir.el-diff --]
[-- Type: text/plain, Size: 923 bytes --]
diff -c /home/george/Config/dot-emacs/contrib/old/nnir.el /home/george/Config/dot-emacs/contrib/new/nnir.el
*** /home/george/Config/dot-emacs/contrib/old/nnir.el 2014-03-06 11:46:24.029862148 -0500
--- /home/george/Config/dot-emacs/contrib/new/nnir.el 2014-03-06 11:52:55.873872182 -0500
***************
*** 1483,1489 ****
(goto-char (point-min))
(while (re-search-forward
! "^\\([0-9]+\\.\\).*\\((score: \\([0-9]+\\)\\))\n\\([^ ]+\\)"
nil t)
(setq score (match-string 3)
group (file-name-directory (match-string 4))
--- 1483,1489 ----
(goto-char (point-min))
(while (re-search-forward
! "^\\([0-9,]+\\.\\).*\\((score: \\([0-9]+\\)\\))\n\\([^ ]+\\)"
nil t)
(setq score (match-string 3)
group (file-name-directory (match-string 4))
Diff finished. Thu Mar 6 11:53:21 2014
[-- Attachment #3: Type: text/plain, Size: 101 bytes --]
--
-===- George McNinch <gmcninch@gmail.com>
-===- http://gmcninch.math.tufts.edu
next prev parent reply other threads:[~2014-03-06 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 21:32 nnir + namazu: always <= 999 matches ? George McNinch
2014-03-06 17:13 ` George McNinch [this message]
2014-03-06 18:53 ` nnir + namazu: always <= 999 matches ? ANS: commas! Andreas Schwab
2014-03-07 16:58 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82iorr1c9f.fsf@chipmunk-via-gmail.com \
--to=gmcninch@gmail.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).