From: Andreas Schwab <schwab@linux-m68k.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6390@debbugs.gnu.org
Subject: bug#6390: Should not regexp-quote quote newline?
Date: Thu, 10 Jun 2010 18:56:10 +0200 [thread overview]
Message-ID: <m2wru6vnbp.fsf@igel.home> (raw)
In-Reply-To: <AANLkTikv3or1QOUqr_gSLe7oCQS-IbheDXPIWz13CsvJ@mail.gmail.com> (Lennart Borgman's message of "Thu, 10 Jun 2010 17:34:46 +0200")
Lennart Borgman <lennart.borgman@gmail.com> writes:
> That the regexp-quoted string includes the new line character instead
> of the two chararcers \n.
How does that fit into the purpose of regexp-quote?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-06-10 16:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 14:42 bug#6390: Should not regexp-quote quote newline? Lennart Borgman
2010-06-10 15:01 ` Andreas Schwab
2010-06-10 15:02 ` Lennart Borgman
2010-06-10 15:34 ` Drew Adams
2010-06-10 16:08 ` Andreas Schwab
2010-06-10 16:11 ` Lennart Borgman
2010-06-10 16:22 ` Andreas Schwab
2010-06-10 16:46 ` Lennart Borgman
2010-06-10 17:03 ` Andreas Schwab
2010-06-10 18:07 ` Lennart Borgman
2010-06-10 23:11 ` Lennart Borgman
2010-06-11 0:44 ` Lennart Borgman
2010-06-10 15:22 ` Drew Adams
2010-06-10 15:34 ` Lennart Borgman
2010-06-10 16:28 ` Juanma Barranquero
2010-06-10 16:47 ` Lennart Borgman
2010-06-10 16:56 ` Andreas Schwab [this message]
2010-06-10 17:00 ` Lennart Borgman
2010-06-11 4:19 ` MON KEY
2010-06-11 4:43 ` Lennart Borgman
2010-06-11 20:09 ` MON KEY
2010-06-11 20:37 ` Lennart Borgman
2010-06-12 6:18 ` MON KEY
2010-06-12 13:28 ` Lennart Borgman
2010-06-14 3:00 ` MON KEY
2010-06-14 5:33 ` Lennart Borgman
2010-06-12 6:51 ` Kevin Rodgers
2010-06-12 13:37 ` Lennart Borgman
2011-07-09 5:30 ` Glenn Morris
2011-07-09 10:03 ` Lennart Borgman
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=m2wru6vnbp.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=6390@debbugs.gnu.org \
--cc=lennart.borgman@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.
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.