unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: help-gnu-emacs@gnu.org
Subject: Re: Why are RegExps never working?
Date: Fri, 16 Nov 2007 11:17:23 +0100	[thread overview]
Message-ID: <yoijy7cywl3g.fsf@remote4.student.chalmers.se> (raw)
In-Reply-To: 87oddu4vpf.fsf@lion.rapttech.com.au

Tim X <timx@nospam.dev.null> writes:

> bojohan+news@dd.chalmers.se (Johan Bockgård) writes:
>
>> Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
>>
>>> There's a minor 'catch' here, which may prove interesting.  The
>>> `character-classes' supported by the regexp engine of Emacs
>>> consider the end of a line a [[:space:]] character
>>
>> There are several modes where this is not true, including Lisp and C. In
>> these modes newlines have `endcomment' syntax.
>
> isn't this controlled by the syntax table?

Yes.

> As you can modify the syntax table, you can modify how such things
> work. I seem to remember seeing a bit of elisp that did this to make
> the regexp easier to write when needing to do re-search. from memory,
> I think it temporarily changed the newline syntax entry in the local
> syntax table, performed the search and since this was all done within
> a saved context, everything is restored afterwards.

(with-syntax-table (copy-syntax-table ...)
  (modify-syntax-entry ...))

-- 
Johan Bockgård

  reply	other threads:[~2007-11-16 10:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 14:06 Why are RegExps never working? Sven Bretfeld
2007-11-11 14:47 ` Peter Dyballa
2007-11-11 15:19   ` Sven Bretfeld
2007-11-11 15:52     ` Peter Dyballa
2007-11-11 23:24       ` Sven Bretfeld
2007-11-12  9:39         ` Peter Dyballa
2007-11-12  9:53           ` Sven Bretfeld
     [not found]       ` <mailman.3307.1194823515.18990.help-gnu-emacs@gnu.org>
2007-11-12  8:21         ` Harald Hanche-Olsen
2007-11-12  9:55           ` Sven Bretfeld
2007-11-12 10:15             ` Lennart Borgman (gmail)
2007-11-12 15:10               ` Drew Adams
2007-11-12 16:01                 ` Sven Bretfeld
     [not found]           ` <mailman.3326.1194861370.18990.help-gnu-emacs@gnu.org>
2007-11-12 13:04             ` Richard G Riley
2007-11-12 18:54               ` Drew Adams
2007-11-13  8:55           ` Tim X
2007-11-13 13:54             ` Richard G Riley
     [not found]     ` <mailman.3268.1194797266.18990.help-gnu-emacs@gnu.org>
2007-11-12 23:53       ` Giorgos Keramidas
2007-11-13 15:49         ` Peter Dyballa
2007-11-13 16:37           ` Giorgos Keramidas
2007-11-13 23:51             ` Sven Bretfeld
2007-11-14  9:55               ` Peter Dyballa
2007-11-14 17:52                 ` Sven Bretfeld
     [not found]             ` <mailman.3482.1194997914.18990.help-gnu-emacs@gnu.org>
2007-11-14  3:13               ` Giorgos Keramidas
2007-11-14  9:22         ` Johan Bockgård
2007-11-16  5:15           ` Tim X
2007-11-16 10:17             ` Johan Bockgård [this message]
2007-11-11 15:21 ` Bastien
2007-11-11 14:38   ` Sven Bretfeld

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=yoijy7cywl3g.fsf@remote4.student.chalmers.se \
    --to=bojohan+news@dd.chalmers.se \
    --cc=help-gnu-emacs@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.
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).