Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: asjo@koldfront.dk (Adam Sjøgren)
Cc: info-gnus-english@gnu.org
Subject: Re: nnmail-split-fancy: Can not split on Subject
Date: Mon, 10 Jul 2017 17:58:28 +0300	[thread overview]
Message-ID: <ygmr2xotk2z.fsf@alpha> (raw)
In-Reply-To: <8760f2c11o.fsf@tullinup.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Sat, 08 Jul 2017 19:04:51 +0200")

On 2017-07-08 19:04 +02, asjo@koldfront.dk (Adam Sjøgren) wrote:
> Göktuğ writes:
>
>> where ‘<redacted2>’ is a short word of only alphanumerical characters.
>> What am I doing wrong?
>
> There is this odd thing that a word-boundary match is tacked on to the
> beginning and start of the regexp, which sometimes is confusing.
>
> I usually get around it by sticking ".*" to either, or both, ends, when
> it doesn't match as I expect it to.
>
> You can also change the variable nnmail-split-fancy-match-partial-words.
>
> (See
> https://www.gnu.org/software/emacs/manual/html_node/gnus/Fancy-Mail-Splitting.html
> starting from "Normally, value in theses split must match a complete
> word"...)
>
> Remember you can use B q (or even B t) to check your splits match as you
> expect them to.
>
>
>   Best regards,
>
>     Adam

Thank you so much!  Setting `nnmail-split-fancy-match-partial-words' to
t worked for me.  I've overlooked that section in the manual.

Best,

        gk.

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

      reply	other threads:[~2017-07-10 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08 14:35 Göktuğ Kayaalp
2017-07-08 17:04 ` Adam Sjøgren
2017-07-10 14:58   ` Göktuğ Kayaalp [this message]

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=ygmr2xotk2z.fsf@alpha \
    --to=self@gkayaalp.com \
    --cc=asjo@koldfront.dk \
    --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).