From: Daniel Brooks <db48x@db48x.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Matt Armstrong <matt@rfc20.org>,
emacs-devel@gnu.org, Naoya Yamashita <conao3@gmail.com>,
Alan Mackenzie <acm@muc.de>
Subject: Re: [PATCH] Interpret #r"..." as a raw string
Date: Tue, 02 Mar 2021 03:26:49 -0800 [thread overview]
Message-ID: <8735xdkd8m.fsf@db48x.net> (raw)
In-Reply-To: <87a6rl249j.fsf@igel.home> (Andreas Schwab's message of "Tue, 02 Mar 2021 12:18:00 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Mär 02 2021, Daniel Brooks wrote:
>
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> There is also the tcl way, where {} delimits kind of raw strings, but
>>> allows properly nested {} pairs inside.
>>
>> That's an unusual choice; I'll have to keep it in mind for the next time
>> this topic comes up. Apparently you can escape the curly braces if you
>> don't want them to be paired up inside this type of string.
>
> The backslash is not removed, though, so it is impossible to include a
> lone brace in a brace enclosed string.
Ok, that's even weirder.
db48x
next prev parent reply other threads:[~2021-03-02 11:26 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 18:18 [PATCH] Interpret #r"..." as a raw string Naoya Yamashita
2021-02-26 18:27 ` [External] : " Drew Adams
2021-02-26 18:53 ` Naoya Yamashita
2021-02-26 19:03 ` Drew Adams
2021-02-26 19:48 ` Stefan Monnier
2021-02-26 20:23 ` Naoya Yamashita
2021-02-26 20:34 ` Andreas Schwab
2021-02-26 20:39 ` Naoya Yamashita
2021-02-26 20:45 ` Andreas Schwab
2021-02-26 20:50 ` Naoya Yamashita
2021-02-26 20:54 ` Andreas Schwab
2021-02-26 20:03 ` Eli Zaretskii
2021-02-26 20:34 ` Naoya Yamashita
2021-02-26 19:09 ` Andreas Schwab
2021-02-26 20:00 ` Eli Zaretskii
2021-02-27 0:39 ` Daniel Brooks
2021-02-27 16:14 ` Richard Stallman
2021-02-27 16:18 ` Stefan Monnier
2021-03-01 5:19 ` Richard Stallman
2021-03-02 5:45 ` Matt Armstrong
2021-03-03 5:53 ` Richard Stallman
2021-03-03 6:14 ` Daniel Brooks
2021-03-03 7:00 ` Eli Zaretskii
2021-03-04 2:47 ` Matt Armstrong
2021-03-04 13:49 ` Eli Zaretskii
2021-03-04 16:55 ` Matt Armstrong
2021-03-05 5:44 ` Richard Stallman
2021-03-05 5:39 ` Richard Stallman
2021-03-05 8:01 ` Eli Zaretskii
2021-03-06 5:13 ` Richard Stallman
2021-03-06 6:04 ` Matt Armstrong
2021-03-07 6:13 ` Richard Stallman
2021-03-07 17:20 ` [External] : " Drew Adams
2021-03-06 8:27 ` Eli Zaretskii
2021-03-06 9:51 ` Daniel Brooks
2021-03-06 10:24 ` Eli Zaretskii
2021-03-07 6:08 ` Richard Stallman
2021-02-27 20:41 ` Daniel Brooks
2021-02-28 6:22 ` Zhu Zihao
2021-03-01 5:26 ` Richard Stallman
2021-03-01 12:06 ` Alan Mackenzie
2021-03-01 12:13 ` Andreas Schwab
2021-03-02 5:59 ` Matt Armstrong
2021-03-02 9:56 ` Daniel Brooks
2021-03-02 10:13 ` Andreas Schwab
2021-03-02 10:55 ` Daniel Brooks
2021-03-02 11:18 ` Andreas Schwab
2021-03-02 11:26 ` Daniel Brooks [this message]
2021-03-02 11:14 ` Alan Mackenzie
2021-03-02 11:52 ` Daniel Brooks
2021-03-02 12:01 ` Dmitry Gutov
2021-03-02 14:14 ` Alan Mackenzie
2021-03-02 14:32 ` Dmitry Gutov
2021-03-02 15:06 ` Alan Mackenzie
2021-03-02 11:41 ` Aurélien Aptel
2021-03-02 13:49 ` Stefan Monnier
2021-03-02 14:46 ` Aurélien Aptel
2021-03-02 15:11 ` Stefan Monnier
2021-03-02 16:07 ` Aurélien Aptel
2021-03-03 7:31 ` Alfred M. Szmidt
2021-03-03 16:02 ` Stefan Monnier
2021-03-02 20:36 ` Daniel Brooks
2021-03-03 0:27 ` Stefan Monnier
2021-03-03 0:42 ` Daniel Brooks
2021-03-03 8:16 ` Andreas Schwab
2021-03-03 9:25 ` Daniel Brooks
2021-03-03 9:29 ` Andreas Schwab
2021-03-03 10:02 ` Daniel Brooks
2021-03-03 10:11 ` Daniel Brooks
2021-03-03 10:14 ` Andreas Schwab
2021-03-03 11:48 ` Daniel Brooks
2021-03-03 10:12 ` Michael Albinus
2021-03-03 10:42 ` Daniel Brooks
2021-03-03 10:49 ` Michael Albinus
2021-03-03 16:12 ` Stefan Monnier
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=8735xdkd8m.fsf@db48x.net \
--to=db48x@db48x.net \
--cc=acm@muc.de \
--cc=conao3@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=matt@rfc20.org \
--cc=schwab@linux-m68k.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.