From: "Drew Adams" <drew.adams@oracle.com>
To: "'xfq'" <xfq.free@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: About regexp
Date: Sun, 25 Nov 2012 07:41:33 -0800 [thread overview]
Message-ID: <F32F7B31DBD34FE1963ABADD5C2218EC@us.oracle.com> (raw)
In-Reply-To: <50B1DBEF.2040906@gmail.com>
> The default value of the variable `sentence-end-base' is:
> [.?!][]\"'")}]*
> There is a backslash in the second part of the regexp, why?
C-h v sentence-end-base tells you:
sentence-end-base is a variable defined in `paragraphs.el'.
Its value is "[.?!][]\"'")}]*"
IOW, the value is a string. The double-quote chars shown surrounding the string
are not characters in the string. The double-quote char shown just before the
single-quote char, ', is in the string. When printed, that char is escaped with
a backslash. The char in the string following the ' char is a different char (a
curly quote) - it is not used to indicate the string limits, so it need not be
escaped to distinguish it.
next prev parent reply other threads:[~2012-11-25 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 8:50 About regexp xfq
2012-11-25 15:41 ` Drew Adams [this message]
2012-11-26 7:50 ` xfq
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=F32F7B31DBD34FE1963ABADD5C2218EC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=xfq.free@gmail.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).