Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: miscellaneous Gnus problems/questions
Date: 12 Jun 1996 09:42:50 +0200	[thread overview]
Message-ID: <rjhgsho4cl.fsf@kleene.dina.kvl.dk> (raw)
In-Reply-To: jbw@cs.bu.edu's message of Wed, 12 Jun 1996 00:11:20 -0400


>>>>> "JW" == Joe Wells <jbw@cs.bu.edu> writes:

JW> 4.  What does the name "eething" mean?  Why "ee"?

When I try to pronounce `nneething' is sounds just like `anything'.

JW> 12. nnmail-split-it adds "\\<" and "\\>" around the patterns the user
JW>     supplies in nnmail-split-fancy.  This breaks any patterns which don't
JW>     begin and end at word boundaries.  This is undocumented.  

No, it is documented in the section about fancy mail splitting:

Gnus>   In these splits, FIELD must match a complete field name.  VALUE must
Gnus> match a complete word according to the fundamental mode syntax table.
Gnus> You can use `.*' in the regexps to match partial field names or words.

JW>     It would be nice if this was optional.

I think `.*' is easy enough to add the few places it is needed.

JW> 13. "*" has word syntax in the article buffer.  

It has symbol syntax in Gnus 5.2.

JW> 15. A bug in nnmail-split it: "\\>\\)" should be "\\)\\>".

I don't see how that can make a difference.

JW> 16. Editing a SCORE file directly doesn't get noticed.  What does one have
JW>     to do to get the changes noticed by Gnus?

gnus-score-flush-cache


  parent reply	other threads:[~1996-06-12  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-12  4:11 Joe Wells
1996-06-12  6:03 ` Jason L Tibbitts III
1996-06-12 21:25   ` Ken Olstad
1996-06-14  2:10   ` Joe Wells
1996-06-14  4:56     ` Jason L Tibbitts III
1996-06-12  7:42 ` Per Abrahamsen [this message]
1996-06-12  7:51   ` Joe Wells
1996-06-12  8:17     ` Per Abrahamsen
1996-06-14 15:30 ` Kai Grossjohann

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=rjhgsho4cl.fsf@kleene.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).