From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: Easy regexp issue
Date: 22 Jan 2007 11:26:22 -0800 [thread overview]
Message-ID: <1169493981.553162.162930@l53g2000cwa.googlegroups.com> (raw)
In-Reply-To: <1169213390.880236.176320@q2g2000cwa.googlegroups.com>
HS wrote:
> Thanks everyone! The problem was solved!
> I wanted it for this:
For future reference, when messing with this problem:
The function "princ" is useful, it prints things without lisp syntax
around them. So, if you do (princ foo) you see what string a function
will recieve when sent the string foo. Therefore, you can write foo in
lisp syntax and see what it means.
For example (princ "\\\\\\") =>\\\
next prev parent reply other threads:[~2007-01-22 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 18:32 Easy regexp issue HS
2007-01-18 19:32 ` Joost Kremers
2007-01-19 7:28 ` Kevin Rodgers
[not found] ` <mailman.3295.1169191738.2155.help-gnu-emacs@gnu.org>
2007-01-19 7:49 ` Barry Margolin
2007-01-19 13:29 ` HS
2007-01-22 19:26 ` Robert Thorpe [this message]
2007-01-20 6:09 ` Kevin Rodgers
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=1169493981.553162.162930@l53g2000cwa.googlegroups.com \
--to=rthorpe@realworldtech.com \
/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).