Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Svend Tollak Munkejord <stm@bacchus.pvv.org>
Subject: Less strict regexp in gnus-outlook...
Date: Tue, 18 Mar 2003 19:33:35 +0100	[thread overview]
Message-ID: <hdd4r607ce8.fsf@bacchus.pvv.ntnu.no> (raw)

Hi,

I use ognus-0.16 and find the Outlook deuglify function `W Y f' really
great, and I use it (almost) every day. However, it fails on some
particularly ugly e-mails:

1. There may be a space after the "Original Message" line:

----- Original Message ----- 
...

2. The "Original Message" line does not always have four consecutive
   hyphens:

-- Messaggio originale --

I fixed this in a simpleminded way by changing the regexp in
gnus-outlook-repair-attribution-block from

(defun gnus-outlook-repair-attribution-block ()
  "Repair a big broken attribution block."
  (save-excursion
    (let ((case-fold-search nil)
	  (inhibit-read-only t)
	  (cite-marks gnus-outlook-deuglify-cite-marks))
      (gnus-with-article-buffer
	(article-goto-body)
	(if (re-search-forward
	     (concat "^[" cite-marks " \t]*----* ?[^-]+ [^-]+ ?----*\n"
		     "[^\n:]+:[ \t]*\\([^\n]+\\)\n"
		     "\\([^\n:]+:[ \t]*[^\n]+\n\\)+")
	     nil t)
	    (progn
	      (gnus-kill-all-overlays)
	      (replace-match "\\1 wrote:\n")
	      (match-beginning 0)))))))


to 

...
	     (concat "^[" cite-marks " \t]*--* ?[^-]+ [^-]+ ?--*\\s *\n"
		     "[^\n:]+:[ \t]*\\([^\n]+\\)\n"
		     "\\([^\n:]+:[ \t]*[^\n]+\n\\)+")
...

Regards,
-- 
Svend Tollak Munkejord 


             reply	other threads:[~2003-03-18 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 18:33 Svend Tollak Munkejord [this message]
2003-03-22 14:27 ` Lars Magne Ingebrigtsen
     [not found]   ` <hdd65qbdzpg.fsf@bacchus.pvv.ntnu.no>
2003-03-22 18:29     ` Lars Magne 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=hdd4r607ce8.fsf@bacchus.pvv.ntnu.no \
    --to=stm@bacchus.pvv.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).