From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Treat sourceforge tracker messages with gnus-cite
Date: Sun, 02 Oct 2005 19:39:31 +0200 [thread overview]
Message-ID: <v9slvj3jjg.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
some projects copy sourceforge tracker comments to mailing list which
are readable on gmane.org, e.g. gmane.comp.tex.xdvi.devel and
gmane.mail.mh-e.devel.
Unfortunately these article are hard to read because of the citation
style (see below for details) without proper quotation marks:
- message 1 (original article)
- message 2
- [...]
- last message
It would be nice if these articles could be made more readable with
the gnus-cite machinery, including collapsing of long quotes (I have
gnus-cited-lines-visible set to '(3 . 6)).
Below is an example taken from
<E1EKi7t-0005gM-Ju@sc8-sf-web4.sourceforge.net> [1]:
--8<---------------cut here---------------start------------->8---
Bugs item #1306141, was opened at 2005-09-27 15:06
Message generated for change (Comment added) made by psg
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=113357&aid=1306141&group_id=13357
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MIME
Group: CVS
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Eric Ding (ericding)
Assigned to: Nobody/Anonymous (nobody)
Summary: msg display broken after displaying msg w/ inline image
Initial Comment:
[Everything from "Initial Comment" to "^Comment By:" is the very first
article in this thread, so it should have the highest gnus-cite-N
face.]
----------------------------------------------------------------------
>Comment By: Peter S Galbraith (psg)
Date: 2005-09-28 16:02
Message:
Logged In: YES
user_id=31877
[This is the second article, so it should be in gnus-cite-(N-1) face]
----------------------------------------------------------------------
Comment By: Bill Wohler (wohler)
Date: 2005-09-27 18:26
Message:
Logged In: YES
user_id=93690
[This is the most recent article. It should be displayed in default
face.]
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=113357&aid=1306141&group_id=13357
--8<---------------cut here---------------end--------------->8---
I tried to fiddle with `gnus-cite-parse' without much success
(everything below "Initial Comment" seems to belong to the initial
comment):
--8<---------------cut here---------------start------------->8---
--- gnus-cite.el 26 Aug 2005 14:10:02 +0200 7.15
+++ gnus-cite.el 02 Oct 2005 19:24:51 +0200
@@ -801,6 +801,18 @@
(goto-char begin))
(goto-char start)
(setq line (1+ line)))
+ ;; Try to support "Initial Comment" on sourceforge list:
+ (goto-char (point-min))
+ (when (re-search-forward "Initial Comment:" max t)
+ (setq begin (count-lines (point-min) (point)))
+ (setq end (or (re-search-forward "^-\\{60,\\}\n+>?Comment By:" max t)
+ begin))
+ ;; I'm not sure what this does...
+ (setq entry nil)
+ (while (< begin end)
+ (push begin entry)
+ (setq begin (1+ begin)))
+ (push (cons "" entry) alist))
;; Horrible special case for some Microsoft mailers.
(goto-char (point-min))
(when (re-search-forward gnus-cite-unsightly-citation-regexp max t)
--8<---------------cut here---------------end--------------->8---
Maybe I should use `gnus-cite-loose-attribution-alist'.
Ideas? Suggestions?
Bye, Reiner.
[1] Other MIDs:
<E1EKNuE-0003UV-Lj@sc8-sf-web1.sourceforge.net>
<E1EKNuE-0003UV-Lj@sc8-sf-web1.sourceforge.net>
<E1ELMBx-0000c4-3d@sc8-sf-web4.sourceforge.net>
<E1ELPEV-0007cw-4U@sc8-sf-web2.sourceforge.net>
<E1EL3Wu-0001gL-Eh@sc8-sf-web4.sourceforge.net>
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next reply other threads:[~2005-10-02 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 17:39 Reiner Steib [this message]
2005-10-03 16:56 ` Wes Hardaker
2005-10-13 20:15 ` Reiner Steib
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=v9slvj3jjg.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).