From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Slighty improved regexps for citations
Date: Tue, 25 Feb 2003 22:06:39 +0100 [thread overview]
Message-ID: <m3znok5azm.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <m3adgk6rmx.fsf@hamster.pflaesterer.de>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
Sorry there was a little error (I forgot the true-part in the regexp for
message.el). Here is the correct patch (the other one again so it's more
convenient for the one who commits)
Here something for the changelog:
2003-02-25 Karl Pflästerer <sigurd@12move.de>
* message.el (message-cite-prefix-regexp): added `:' and `#'
* deuglify.el (gnus-outlook-deuglify-cite-marks): added `:'
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch(2) for message.el --]
[-- Type: text/x-patch, Size: 999 bytes --]
Index: message.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/message.el,v
retrieving revision 6.306
diff -u -r6.306 message.el
--- message.el 23 Feb 2003 13:39:47 -0000 6.306
+++ message.el 25 Feb 2003 21:10:13 -0000
@@ -488,8 +488,9 @@
:type 'regexp)
(defcustom message-cite-prefix-regexp
+(setq message-cite-prefix-regexp
(if (string-match "[[:digit:]]" "1") ;; support POSIX?
- "\\([ \t]*[-_.[:word:]]+>+\\|[ \t]*[]>|}+]\\)+"
+ "\\([ \t]*[-_.[:word:]]+>+\\|[ \t]*[]>|:#}+]\\)+"
;; ?-, ?_ or ?. MUST NOT be in syntax entry w.
(let ((old-table (syntax-table))
non-word-constituents)
@@ -504,7 +505,7 @@
"\\([ \t]*\\(\\w\\)+>+\\|[ \t]*[]>|}+]\\)+"
(concat "\\([ \t]*\\(\\w\\|["
non-word-constituents
- "]\\)+>+\\|[ \t]*[]>|}+]\\)+"))))
+ "]\\)+>+\\|[ \t]*[]>|:#}+]\\)+"))))
"*Regexp matching the longest possible citation prefix on a line."
:group 'message-insertion
:type 'regexp)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: patch for deuglify.el --]
[-- Type: text/x-patch, Size: 554 bytes --]
Index: deuglify.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/deuglify.el,v
retrieving revision 6.10
diff -u -r6.10 deuglify.el
--- deuglify.el 8 Feb 2003 21:20:53 -0000 6.10
+++ deuglify.el 25 Feb 2003 20:33:47 -0000
@@ -244,7 +244,7 @@
:type 'number
:group 'gnus-outlook-deuglify)
-(defcustom gnus-outlook-deuglify-cite-marks ">|#%"
+(defcustom gnus-outlook-deuglify-cite-marks ">|#%:"
"Characters that indicate cited lines."
:type 'string
:group 'gnus-outlook-deuglify)
[-- Attachment #4: Type: text/plain, Size: 193 bytes --]
bye
KP
--
He took his vorpal sword in hand:
Long time the manxome foe he sought--
So rested he by the Tumtum tree,
And stood awhile in thought. "Lewis Carroll" "Jabberwocky"
next prev parent reply other threads:[~2003-02-25 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 20:27 Karl Pflästerer
2003-02-25 21:06 ` Karl Pflästerer [this message]
[not found] ` <hhk7fnrxnc.fsf@blah.pl>
2003-02-26 17:05 ` Karl Pflästerer
2003-02-25 21:19 ` Reiner Steib
2003-02-25 22:05 ` Karl Pflästerer
2003-02-25 22:27 ` Karl Pflästerer
2003-02-25 23:09 ` Frank Schmitt
2003-02-26 16:37 ` Reiner Steib
2003-02-26 17:59 ` Karl Pflästerer
2003-02-26 22:11 ` Karl Pflästerer
2003-02-25 21:33 ` Raymond Scholz
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=m3znok5azm.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.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).