From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Stephen J. Turnbull'" <stephen@xemacs.org>
Cc: "'Mark A. Hershberger'" <mah@everybody.org>,
emacs-devel@gnu.org, emacsweblogs@nongnu.org,
'smc' <smc@manticore.es>
Subject: RE: [Emacsweblogs] i18n
Date: Mon, 1 Feb 2010 10:56:07 -0800 [thread overview]
Message-ID: <0B0F20F17689462CA495798B348F923D@us.oracle.com> (raw)
In-Reply-To: <jwvbpg9c5jg.fsf-monnier+emacs@gnu.org>
> It would be easy to change the reader such that _"foo" is
> automatically read as (_ "foo"), just like we do for 'foo -> (quote foo).
Oh sure. And break existing code.
It might be easy to change the reader to do that.
But why? What's really gained by such a change?
Lisp (in general) has always read + eval'd a sexp such as (list 'foo_"bar") to
produce the list (foo_ "bar"). You would have it return (foo (_ "bar"))?
Caveat: I haven't followed this thread. I thought the question was about markup.
Why would a feature request for markup make us want to change the Lisp reader?
Apologies if I misunderstand the suggestion.
next prev parent reply other threads:[~2010-02-01 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1e7a74211001281954h1295a717id942a4405dc98b25@mail.gmail.com>
[not found] ` <87vdekbt60.fsf@everybody.org>
2010-01-31 15:29 ` [Emacsweblogs] i18n smc
2010-02-01 7:52 ` Mark A. Hershberger
2010-02-01 8:51 ` Stephen J. Turnbull
2010-02-01 12:04 ` Juri Linkov
2010-02-01 13:22 ` Stephen J. Turnbull
2010-02-01 18:13 ` tomas
2010-02-01 18:20 ` Andreas Schwab
2010-02-01 21:45 ` i18n Juri Linkov
2010-02-01 16:01 ` [Emacsweblogs] i18n Stefan Monnier
2010-02-01 18:56 ` Drew Adams [this message]
2010-02-01 20:33 ` i18n Stefan Monnier
2010-02-01 21:36 ` [Emacsweblogs] i18n Drew Adams
2010-02-01 23:14 ` i18n Stefan Monnier
2010-02-02 1:21 ` [Emacsweblogs] i18n Kenichi Handa
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=0B0F20F17689462CA495798B348F923D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=emacsweblogs@nongnu.org \
--cc=mah@everybody.org \
--cc=monnier@iro.umontreal.ca \
--cc=smc@manticore.es \
--cc=stephen@xemacs.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.