From: kaz@ashi.footprints.net (Kaz Kylheku)
Subject: Re: On refining regexp by adding exceptions systematically
Date: 3 Oct 2002 11:38:53 -0700 [thread overview]
Message-ID: <cf333042.0210031038.56c8ee4e@posting.google.com> (raw)
In-Reply-To: 9e8ebeb2.0210030427.4544cb00@posting.google.com
gnuist007@hotmail.com (gnuist) wrote in message news:<9e8ebeb2.0210030427.4544cb00@posting.google.com>...
> Here is regular expression in emacs lisp that initially seems to work
> for the job:
Goddamned idiot, you have already been advised not to crosspost Lisp
questions to comp.lang.lisp. If you can't understand a simple thing
like that, you aren't fit to participate in any activity that requires
thought.
next prev parent reply other threads:[~2002-10-03 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 12:27 On refining regexp by adding exceptions systematically gnuist
2002-10-03 18:38 ` Kaz Kylheku [this message]
2002-10-03 23:04 ` Kaz Kylheku
[not found] ` <tvikna.obd.ln@lart.ca>
2002-10-07 14:13 ` Rodney Sparapani
2002-10-05 13:31 ` Alan Mackenzie
2002-10-05 16:11 ` Stefan Monnier <foo@acm.com>
2002-10-05 17:45 ` Alan Mackenzie
2002-10-06 3:02 ` Vassil Nikolov
2002-10-06 7:48 ` Alan Mackenzie
2002-10-05 19:46 ` Christopher Browne
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf333042.0210031038.56c8ee4e@posting.google.com \
--to=kaz@ashi.footprints.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).