From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Raw string literals in Emacs lisp.
Date: Sun, 03 Aug 2014 22:12:16 +0900 [thread overview]
Message-ID: <87y4v5lntb.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87zjfmowu0.fsf@fencepost.gnu.org>
David Kastrup writes:
> At any rate, things can get more complex, like with
>
> (format "%s%c\n""r#"?\") => "r#\"
> "
I'm not really worried about more complex. I am concerned about
whether there's an unambiguous answer to "what is the value -- or
error -- of eval-print-last-sexp at point?"
In the case of
(format "%s%c\n""r#"?\")-!-
it's "r#\"\n". But for
(format "%s%c\n""r#"?\"-!-)
you could argue that it's ?\" (that's XEmacs's opinion) or "?\\". I
guess for XEmacs (which already has this syntax in the wild) the rule
should be "longest match wins" (because otherwise there's no way to
evaluate r#"?\" in an interactive buffer), but for Emacs that looks
like a deal-killer, and it's already present with just r#"?\".
*sigh*
next prev parent reply other threads:[~2014-08-03 13:12 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
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 [this message]
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=87y4v5lntb.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=dak@gnu.org \
--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).