Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: info-gnus-english@gnu.org
Subject: About toothpicks (was Re: nnimap-split-fancy)
Date: Fri, 17 Dec 2010 18:30:39 +0100	[thread overview]
Message-ID: <87aak4488w.fsf_-_@gmail.com> (raw)
In-Reply-To: <m2r5dg3086.fsf@verilab.com> (Tommy Kelly's message of "Fri, 17 Dec 2010 09:09:13 -0600")

Tommy Kelly <tommy.kelly@verilab.com> writes:

> asjo@koldfront.dk (Adam Sjøgren) writes:

>> ... it helps
>> pinpointing where I have forgotten some \'s or something (I am used to
>> Perls regexp syntax, so remembering all the leaning toothpicks in Emacs
>> regexps is sometimes a problem :-))
>
> Yeah, me too. For example: why does the . in domain1.com require the
> "\\" when included in the fancy split approach, but no toothpicks at all
> are needed when the same string is included in the normal (non fancy)
> approach?
>
> At first I assumed it was because in the fancy approach the string is a regexp
> while in non-fancy it's just a plain string. But that's not true is it? The
> use of things like "^" and ".*"  in non-fancy shows it's a regexp too,
> no?

It's really simple. '.' matches anything except newline, including a
dot. If you want to match a literal dot, you need '\.', but inside lisp
strings, double quotes and backslashes must be escaped with a backslash,
so what you end up with is "\\.".

  Štěpán

  reply	other threads:[~2010-12-17 17:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1292548275.31723.info-gnus-english@gnu.org>
2010-12-17  9:38 ` nnimap-split-fancy Adam Sjøgren
2010-12-17 10:36   ` nnimap-split-fancy Richard Riley
2010-12-17 15:09   ` nnimap-split-fancy Tommy Kelly
2010-12-17 17:30     ` Štěpán Němec [this message]
2010-12-17 22:39       ` About toothpicks (was Re: nnimap-split-fancy) Tommy Kelly
2010-12-18  8:16         ` Error in (info "(gnus)Splitting Mail") Štěpán Němec
     [not found]         ` <mailman.13.1292660334.28168.info-gnus-english@gnu.org>
2010-12-18 18:45           ` Lars Magne Ingebrigtsen
2010-12-18 22:33             ` Tommy Kelly
2010-12-19 14:27               ` Ted Zlatanov
2010-12-19 15:24                 ` Štěpán Němec
2010-12-19 15:53                 ` Tommy Kelly
2010-12-27 15:07                   ` Ted Zlatanov
2010-12-27 16:34                     ` Steinar Bang
     [not found]                   ` <mailman.5.1293462475.24495.info-gnus-english@gnu.org>
2010-12-27 15:38                     ` Richard Riley
2010-12-28 13:21                       ` Tommy Kelly
     [not found]                       ` <mailman.0.1293542535.18545.info-gnus-english@gnu.org>
2010-12-28 15:48                         ` Richard Riley
     [not found]                 ` <mailman.6.1292772417.12385.info-gnus-english@gnu.org>
2010-12-19 15:55                   ` Richard Riley
2010-12-18 19:12     ` nnimap-split-fancy Eric S Fraga
     [not found]   ` <mailman.4.1292598585.3076.info-gnus-english@gnu.org>
2010-12-17 21:18     ` nnimap-split-fancy Adam Sjøgren

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=87aak4488w.fsf_-_@gmail.com \
    --to=stepnem@gmail.com \
    --cc=info-gnus-english@gnu.org \
    --cc=tommy.kelly@verilab.com \
    /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).