From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: category codes and regexps
Date: 26 Jul 2004 17:14:24 -0400 [thread overview]
Message-ID: <jwvd62i79p9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <x5oem2bldk.fsf@lola.goethe.zz>
>> > Assume that I want to check a buffer for characters which aren't Thai,
>> > and which aren't in the range a-z. My first idea was this:
>>
>> > [^\cta-z]
>>
>> \(?:[a-z]\|\ct\)
> What part about "which aren't" did you not understand?
Damn!
Stefan "Oops"
prev parent reply other threads:[~2004-07-26 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 20:59 category codes and regexps Werner LEMBERG
2004-07-25 23:59 ` Kenichi Handa
2004-07-26 2:05 ` Werner LEMBERG
2004-07-26 19:26 ` Stefan Monnier
2004-07-26 19:48 ` David Kastrup
2004-07-26 21:14 ` Stefan Monnier [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
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=jwvd62i79p9.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).