From: Steven L Baur <steve@miranova.com>
Subject: Re: September Gnus 0.31 is released
Date: 26 Jan 1996 15:17:10 -0800 [thread overview]
Message-ID: <m2pwc68s21.fsf@miranova.com> (raw)
In-Reply-To: Mark Borges's message of 26 Jan 1996 12:50:34 -0800
This article should not buttonize either, as in Manoj's original.
>>>>> "mb" == Mark Borges <mdb@cdc.noaa.gov> writes:
mb> Weird.
mb> *All* the URL's in *all* the followups to Manoj's original article
mb> (#6899) -- mine(#6927), Manoj's(#6927) and Steve's(#6928) have been
mb> turned into buttons. The original article (#6899) has no buttons,
mb> except for those in the signature block.
mb> Even the ones with a space after a URL, e.g., both
mb> <URL: ftp://ftp.pilgrim.umass.edu/pub/misc/ding/>
mb> and
mb> <URL:ftp://ftp.pilgrim.umass.edu/pub/misc/ding/>
mb> work, so that apparently wasn't the problem.
mb> So what is so unique about the original #6899?
The .signature. Unhide the original .signature and you will find a
quote from Larry Wall attributed in a fashion typically expected at
the top of an article. I traced it with the debugger, and basically
Gnus is testing each of the entries in gnus-button-alist, without
resetting point to the beginning of the article. The goose is cooked
on an original article (no citation at the top), and a citation in the
.signature -- only the remainder of the .signature gets buttonized.
Naturally anyone running Gnus 5 will not see this, since Gnus 5 uses
only a single regexp, not an alist and the problem cannot arise in
that case.
Here's the fix:
===================================================================
RCS file: RCS/ChangeLog,v
retrieving revision 1.31
diff -u -r1.31 ChangeLog
--- ChangeLog 1996/01/26 16:12:09 1.31
+++ ChangeLog 1996/01/26 23:10:45
@@ -1,3 +1,8 @@
+Fri Jan 26 15:10:09 1996 Steven L. Baur <steve@miranova.com>
+
+ * gnus-vis.el (gnus-article-add-buttons): Need to reset point to top
+ of article before trying the next regexp in the gnus-button-alist.
+
Fri Jan 26 07:47:59 1996 Lars Magne Ingebrigtsen <larsi@eistla.ifi.uio.no>
* gnus.el (gnus): Goto the first unread group.
===================================================================
RCS file: RCS/gnus-vis.el,v
retrieving revision 1.12
diff -u -r1.12 gnus-vis.el
--- gnus-vis.el 1996/01/26 16:12:09 1.12
+++ gnus-vis.el 1996/01/26 23:09:17
@@ -1397,6 +1397,7 @@
(setq beg (point))
(while (setq entry (pop alist))
(setq regexp (car entry))
+ (goto-char beg)
(while (re-search-forward regexp nil t)
(let* ((start (and entry (match-beginning (nth 1 entry))))
(end (and entry (match-end (nth 1 entry))))
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
In article <ThisIsAGnusBug12345@miranova.com> somebody wrote:
prev parent reply other threads:[~1996-01-26 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-25 16:12 Lars Magne Ingebrigtsen
1996-01-25 18:36 ` Steven L Baur
1996-01-25 21:50 ` Wes Hardaker
1996-01-25 22:44 ` luis fernandes
1996-01-26 1:07 ` Steven L Baur
1996-01-26 15:28 ` Colin Rafferty
1996-01-26 17:47 ` Wes Hardaker
1996-01-26 17:48 ` Steven L Baur
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-26 16:46 ` Lars Magne Ingebrigtsen
1996-01-26 17:37 ` Steven L Baur
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-28 0:13 ` Steven L Baur
1996-01-30 16:29 ` Lars Magne Ingebrigtsen
1996-01-25 23:54 ` srivasta
1996-01-26 19:33 ` Mark Borges
1996-01-26 20:28 ` Steven L Baur
1996-01-26 20:29 ` Manoj Srivastava
1996-01-26 20:39 ` Colin Rafferty
1996-01-26 20:50 ` Mark Borges
1996-01-26 23:17 ` Steven L Baur [this message]
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=m2pwc68s21.fsf@miranova.com \
--to=steve@miranova.com \
/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).