From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Re: Random regex/fancy-split question
Date: Tue, 05 Apr 2011 10:57:57 -0400 [thread overview]
Message-ID: <m2d3l0yccq.fsf@nwalsh.com> (raw)
In-Reply-To: <87y63ox2z2.fsf@bifteki.lan> (Leonidas Tsampros's message of "Tue, 05 Apr 2011 16:05:53 +0300")
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
Leonidas Tsampros <ltsampros@upnet.gr> writes:
>
> Maybe you can give that rule a try.
Indeed that works. More of a workaround than an explanation, but suits me for
the moment. Thanks!
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | I have seen the truth and it makes no
http://nwalsh.com/ | sense.
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
prev parent reply other threads:[~2011-04-05 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 17:05 Norman Walsh
2011-04-04 17:12 ` Randal L. Schwartz
2011-04-05 11:01 ` Norman Walsh
2011-04-05 13:05 ` Leonidas Tsampros
2011-04-05 14:57 ` Norman Walsh [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=m2d3l0yccq.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=ding@gnus.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).