all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Anselm Helbig <anselm.helbig+news2009@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: I can not understant a paragraph in Emacs Lisp Reference.
Date: Sat, 11 Jul 2009 14:27:24 +0200	[thread overview]
Message-ID: <87bpnrcslv.wl%anselm.helbig+news2009@googlemail.com> (raw)
In-Reply-To: <mailman.2276.1247310683.2239.help-gnu-emacs@gnu.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

Hi!

> As a `\' is not special inside a character alternative, it can never
> remove the special meaning of `-' or `]'.  So you should not quote
> these characters when they have no special meaning either.  This would
> not clarify anything, since backslashes can legitimately precede these
> characters where they _have_ special meaning, as in `[^\]' (`"[^\\]"'
> for Lisp string syntax), which matches any single character except a
> backslash.
> 
> `[^\]'  or `"[^\\]"' , which is right ? what is Lisp string syntax for ?

Seems to be clear to me: the first one is correct, but the second one
also works, you're just specifying the same character twice, like in
`[^aa]'. So the elisp string would be "[^\\]". Do you know about 
M-x re-builder?

Happy hacking!

Anselm


-- 
Anselm Helbig 
mailto:anselm.helbig+news2009@googlemail.com


       reply	other threads:[~2009-07-11 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2276.1247310683.2239.help-gnu-emacs@gnu.org>
2009-07-11 12:27 ` Anselm Helbig [this message]
     [not found] <mailman.2289.1247323589.2239.help-gnu-emacs@gnu.org>
2009-07-11 14:55 ` I can not understant a paragraph in Emacs Lisp Reference Teemu Likonen
2009-07-11 14:46 waterloo
2009-07-11 15:05 ` Drew Adams
2009-07-11 15:10   ` waterloo
  -- strict thread matches above, loose matches on Subject: below --
2009-07-11 11:11 waterloo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bpnrcslv.wl%anselm.helbig+news2009@googlemail.com \
    --to=anselm.helbig+news2009@googlemail.com \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.