Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: giglio robbo' d'acciaio <dgiglio@iol.it>
To: info-gnus-english@gnu.org
Subject: Re: Custom message-cite-prefix-regexp
Date: Wed, 23 May 2007 15:51:18 +0200	[thread overview]
Message-ID: <87k5uzlkbt.fsf@father.nostromo.wy> (raw)
In-Reply-To: <b4md50rbv1m.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> What situation did you write about?  I couldn't reproduce the
> problem in hilighting citations in the article buffer.  Because
> the regexp used then is the one that the value of `m-c-p-r' is
> surrounded with "^\\(" ... "\\)"

I'm not sure I had unterstood your reply, but this is what I have in my
.emacs:

--8<---------------cut here---------------start------------->8---
 '(message-cite-prefix-regexp "\\([ 	]*[-_.[:word:]]+>+\\|[ ]*[]>|}:+]\\)+")
--8<---------------cut here---------------end--------------->8---

Note that the default value lacks the `:' after `}'.
-- 
      Daniele Giglio      Dona i tuoi cicli di clock alla ricerca!
      dgiglio@iol.it      http://boinc.berkeley.edu/
                          --------------------
                  - Come rendi Windows 98 piu' veloce?
                  - Lo getti con piu' forza.

  reply	other threads:[~2007-05-23 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1059.1179913513.32220.info-gnus-english@gnu.org>
2007-05-23 12:09 ` Katsumi Yamaoka
2007-05-23 13:51   ` giglio robbo' d'acciaio [this message]
     [not found]   ` <mailman.1089.1179937550.32220.info-gnus-english@gnu.org>
2007-05-23 23:03     ` Katsumi Yamaoka
2007-05-24 14:01       ` giglio robbo' d'acciaio
2007-05-22 16:43 giglio robbo' d'acciaio
  -- strict thread matches above, loose matches on Subject: below --
2007-04-30 11:14 custom message-cite-prefix-regexp giglio robbo' d'acciaio
2007-04-30 12:48 ` 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=87k5uzlkbt.fsf@father.nostromo.wy \
    --to=dgiglio@iol.it \
    --cc=info-gnus-english@gnu.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).