From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org
Subject: Re: Character literals for Unicode (control) characters
Date: Sat, 05 Mar 2016 15:28:22 +0000 [thread overview]
Message-ID: <CAArVCkRPFrpXkE4+Z48V529gUZSirVWbotzv1EeqRDeT8aFv0w@mail.gmail.com> (raw)
In-Reply-To: <56D8623F.6060806@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Do., 3. März 2016 um 17:11 Uhr:
> On 03/02/2016 09:47 PM, Lars Ingebrigtsen wrote:
> > And then I thought -- well, if we should have a literal syntax for
> > Unicode control characters, why not for all of them?
> Something like that would make sense. The escape sequence should bracket
> the name, so that the escape sequences could be used in strings without
> ambiguity. Something like \u[NAME], say.
>
> I'd still prefer to use characters as-is in strings if they're
> displayable, e.g., the Lisp string:
>
> "Use Greek capital letters (Α–Ω) to denote figures."
>
> is more readable than:
>
> "Use Greek capital letters (\u[GREEK CAPITAL LETTER ALPHA]\u[EN
> DASH]\u[GREEK CAPITAL LETTER OMEGA]) to denote figures."
>
> But for undisplayable or hard-to-read characters the escape sequence
> would be a win.
>
> More issues: should we insist on the full official name? should we allow
> obsolescent aliases? lower-case instead of upper case? initial prefixes
> of names?
>
>
We should probably do whatever Perl does (
http://perldoc.perl.org/charnames.html). I haven't checked in detail what
is allowed by Perl (except that it allows \N{name} and \N{U+code}), but it
would be simpler to just adopt Perl's behavior (to a reasonable extend)
than trying to come up with our own syntax.
[-- Attachment #2: Type: text/html, Size: 1776 bytes --]
next prev parent reply other threads:[~2016-03-05 15:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 5:47 Character literals for Unicode (control) characters Lars Ingebrigtsen
2016-03-03 6:20 ` John Wiegley
2016-03-03 6:25 ` Lars Ingebrigtsen
2016-03-03 6:34 ` Drew Adams
2016-03-03 16:11 ` Paul Eggert
2016-03-03 20:48 ` Eli Zaretskii
2016-03-03 23:58 ` Paul Eggert
2016-03-05 15:28 ` Philipp Stephani [this message]
2016-03-05 15:39 ` Marcin Borkowski
2016-03-05 16:51 ` Philipp Stephani
2016-03-06 2:27 ` John Wiegley
2016-03-06 15:24 ` Philipp Stephani
2016-03-06 15:54 ` Eli Zaretskii
2016-03-06 17:35 ` Philipp Stephani
2016-03-06 18:08 ` Paul Eggert
2016-03-06 18:28 ` Philipp Stephani
2016-03-06 19:03 ` Paul Eggert
2016-03-06 19:16 ` Philipp Stephani
2016-03-06 20:05 ` Eli Zaretskii
2016-03-13 20:31 ` Philipp Stephani
2016-03-14 20:03 ` Paul Eggert
2016-03-14 20:30 ` Eli Zaretskii
2016-03-15 11:09 ` Nikolai Weibull
2016-03-15 17:10 ` Eli Zaretskii
2016-03-16 8:16 ` Nikolai Weibull
2016-03-14 21:27 ` Clément Pit--Claudel
2016-03-14 21:48 ` Paul Eggert
2016-03-19 16:27 ` Philipp Stephani
2016-03-20 12:58 ` Paul Eggert
2016-03-20 13:25 ` Philipp Stephani
2016-03-25 17:41 ` Philipp Stephani
2016-04-22 2:39 ` Paul Eggert
2016-04-22 7:57 ` Eli Zaretskii
2016-04-22 8:01 ` Eli Zaretskii
2016-04-22 9:39 ` Elias Mårtenson
2016-04-22 10:01 ` Eli Zaretskii
2016-04-25 17:48 ` Paul Eggert
2016-03-05 16:35 ` Clément Pit--Claudel
2016-03-05 17:12 ` Paul Eggert
2016-03-05 17:53 ` Clément Pit--Claudel
2016-03-05 18:16 ` Eli Zaretskii
2016-03-05 18:34 ` Clément Pit--Claudel
2016-03-05 18:56 ` Eli Zaretskii
2016-03-05 19:08 ` Drew Adams
2016-03-05 22:52 ` Clément Pit--Claudel
2016-03-06 15:49 ` Joost Kremers
2016-03-06 16:55 ` Drew Adams
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=CAArVCkRPFrpXkE4+Z48V529gUZSirVWbotzv1EeqRDeT8aFv0w@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.