From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Guile regular expressions are too greedy
Date: Wed, 22 Jul 2009 15:32:12 +0200 [thread overview]
Message-ID: <87eis8etcz.fsf@gnu.org> (raw)
In-Reply-To: 4A671033.6010503@btinternet.com
Chris Dennis <cgdennis@btinternet.com> writes:
> Unfortunately the name of the font really is "Nimbus Sans L" -- it's
> the fact that font names can contain spaces that causes the problem,
> and means that I can't use ([^ ]+) to match the font name.
Aaah, I understand.
Then it may be that POSIX regexps are too inflexible for that job.
Perhaps you could use something like SRFI-13's `string-tokenize' to
split the string into individual words, and then write your own
processor to determine which words are part of the font name, and which
words are font hints.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-07-22 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 10:05 Guile regular expressions are too greedy Chris Dennis
2009-07-22 12:21 ` Ludovic Courtès
2009-07-22 13:12 ` Chris Dennis
2009-07-22 13:32 ` Ludovic Courtès [this message]
2009-07-22 13:41 ` Peter Brett
2009-07-22 15:47 ` Guile regular expressions are too greedy [Solved] Chris Dennis
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eis8etcz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).