From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: font-lock function matcher sample
Date: Wed, 04 Aug 2004 20:08:52 GMT [thread overview]
Message-ID: <jwv657yu0qr.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: cerfgi$g39$1@reader10.wxs.nl
> Mmm, yes, you're right. But this means that I'm not clever enough to see
> through those nested statements. I need to unroll them before they make
> sense to me.
Don't think so operationally. Instead take a step back and only consider
the things you know for sure: right after the while loop the condition is
nil.
Stefan
next prev parent reply other threads:[~2004-08-04 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 21:08 font-lock function matcher sample Arjan Bos
2004-07-25 8:26 ` Alan Mackenzie
2004-07-25 19:55 ` Arjan Bos
2004-07-26 20:59 ` Stefan Monnier
2004-07-26 21:00 ` Stefan Monnier
2004-07-27 18:12 ` Arjan Bos
2004-07-27 18:36 ` Stefan Monnier
2004-08-03 18:09 ` Arjan Bos
2004-08-03 18:39 ` Stefan Monnier
2004-08-04 18:56 ` Arjan Bos
2004-08-04 19:48 ` Stefan Monnier
2004-08-04 20:00 ` Arjan Bos
2004-08-04 20:08 ` Stefan Monnier [this message]
2004-08-05 19:16 ` Arjan Bos
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=jwv657yu0qr.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).