Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: scoring
Date: 07 Dec 1999 13:56:01 +0100	[thread overview]
Message-ID: <rjzovmvrj2.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: Brian May's message of "07 Dec 1999 10:29:45 +1100"

Brian May <bmay@csse.monash.edu.au> writes:

> I can't imagine any possible reason why you might want to search for
> \, but perhaps I am mistaken.

But ``\(foo\|bar\)'' would look like ``"\\(foo\\|bar\\)"'' if these
fields used the sexp widget instead of the regexp widget.  `\' is used
a lot in regexps.

One could of course come up with a new meaning of `\' that doesn't
correspond to what you tell the Lisp reader, nor to what is described
in the Regexp section of the manual, nor to what is expected by
commands such as `isearch-forward-regexp'.  I believe that would be
evil.

The current syntax is the same as the syntax expected by
`isearch-forward-regexp'.


  reply	other threads:[~1999-12-07 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-25  0:03 scoring Brian May
1999-12-01 20:56 ` scoring Lars Magne Ingebrigtsen
1999-12-02  1:41   ` scoring Brian May
1999-12-05 21:53     ` scoring Kai Großjohann
1999-12-06  2:58       ` scoring Brian May
1999-12-06  4:11         ` scoring Lars Magne Ingebrigtsen
1999-12-06 12:53           ` scoring Jan Vroonhof
1999-12-06 13:09             ` scoring Per Abrahamsen
1999-12-06 13:21               ` scoring Hrvoje Niksic
1999-12-06 13:02           ` scoring Kai Großjohann
1999-12-06 23:29             ` scoring Brian May
1999-12-07 12:56               ` Per Abrahamsen [this message]
2000-04-21 20:00                 ` scoring Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1996-06-12 18:14 scoring michael lamoureux
1996-06-12 22:02 ` scoring Lars Magne Ingebrigtsen
1996-06-12 22:15 ` scoring Steven L Baur

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=rjzovmvrj2.fsf@zuse.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).