From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Raw string literals in Emacs lisp.
Date: Wed, 30 Jul 2014 17:16:18 -0400 [thread overview]
Message-ID: <877g2uim3h.fsf@lifelogs.com> (raw)
In-Reply-To: CAMbiG3_fkidOqjKHFdfYs8zuTASdJ8o5ThNOovQE5P1KbH7-QA@mail.gmail.com
On Wed, 30 Jul 2014 14:01:52 -0700 Matthew Plant <maplant2@illinois.edu> wrote:
>> How about using a Unicode character as the marker? (prepares for stoning)
MP> I'm on the fence about this idea. It certainly would make parsing in
MP> reverse possible (assuming the reverse parsing functions do not operate on
MP> char *) and easy, but it would also possibly mess up formatting. It also
MP> might not add much convenience because frankly typing non-unicode
MP> characters is _hard_.
Eh, it's really not hard. If it was the only problem with this approach,
it could be enabled in the default keybindings.
MP> One suggestion would be to use the unicode left and right double/single
MP> quotation marks.
Oh, no. The markers shouldn't look like existing ASCII characters or
there will be lynchings. Maybe LEFT DOUBLE ANGLE BRACKET and RIGHT
DOUBLE ANGLE BRACKET would work (they look like << and >>).
Ted
next prev parent reply other threads:[~2014-07-30 21:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:47 Raw string literals in Emacs lisp Matthew Plant
2014-07-25 19:56 ` Tassilo Horn
2014-07-25 20:06 ` Matthew Plant
2014-07-25 20:15 ` Tassilo Horn
2014-07-25 20:24 ` Matthew Plant
2014-07-25 20:33 ` Tom Tromey
2014-07-25 21:40 ` Matthew Plant
2014-07-26 1:19 ` Stephen J. Turnbull
2014-07-26 5:28 ` Matthew Plant
2014-07-26 5:45 ` chad
2014-07-26 19:39 ` Matthew Plant
2014-07-27 12:27 ` Stephen J. Turnbull
2014-07-27 13:03 ` David Kastrup
2014-07-27 20:58 ` David Caldwell
2014-07-27 23:17 ` Matthew Plant
2014-07-28 18:27 ` Richard Stallman
2014-07-28 19:32 ` Matthew Plant
2014-07-29 19:15 ` Richard Stallman
2014-07-30 0:26 ` Matthew Plant
2014-07-30 4:28 ` Richard Stallman
2014-07-30 18:54 ` Matthew Plant
2014-07-28 2:16 ` Stephen J. Turnbull
2014-07-28 7:43 ` Andreas Schwab
2014-07-30 20:28 ` Ted Zlatanov
2014-07-30 20:41 ` David Caldwell
2014-07-30 20:54 ` Ted Zlatanov
2014-07-30 21:01 ` Matthew Plant
2014-07-30 21:16 ` Ted Zlatanov [this message]
2014-07-30 21:19 ` Matthew Plant
2014-07-31 10:13 ` Ted Zlatanov
2014-08-02 8:47 ` Alan Mackenzie
2014-08-02 9:14 ` David Kastrup
2014-08-02 10:23 ` Alan Mackenzie
2014-08-02 15:51 ` Richard Stallman
2014-08-03 6:50 ` Stephen J. Turnbull
2014-08-03 7:29 ` David Kastrup
2014-08-03 13:12 ` Stephen J. Turnbull
2014-08-03 13:27 ` David Kastrup
2014-08-03 15:01 ` Stephen J. Turnbull
2014-08-04 1:55 ` Richard Stallman
2014-08-04 6:38 ` David Kastrup
2014-08-05 1:41 ` Richard Stallman
2014-08-05 6:15 ` David Kastrup
2014-08-03 13:40 ` David Kastrup
2014-08-03 15:06 ` Stephen J. Turnbull
2014-08-04 1:55 ` Richard Stallman
2014-08-02 9:17 ` Andreas Schwab
2014-07-28 1:29 ` Stephen J. Turnbull
2014-07-26 21:37 ` Thorsten Jolitz
2014-07-29 6:32 ` William Xu
2014-07-29 7:40 ` Andreas Schwab
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=877g2uim3h.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).