From: Adam Porter <adam@alphapapa.net>
To: emacs-devel@gnu.org
Subject: Re: Sv: Sv: Sv: Sv: Christmas wish: Literate Elisp
Date: Wed, 18 Dec 2019 17:52:51 -0600 [thread overview]
Message-ID: <87v9qdp4x8.fsf@alphapapa.net> (raw)
In-Reply-To: VI1P194MB0429356B0A992DBB3961CEE296530@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM
arthur miller <arthur.miller@live.com> writes:
> Yes Adam you are correct, but altering parser does not necessary mean
>
> that elisp will change in a way that will force you to change your
>
> existing code or coding practice. I proposed it in a way that will simply
>
> add an extra feature, which you don’t need to use if you don’t like it. It
>
> is trivial to make it by default ”off” by introducing new variable one can
>
> set in init file to enable it (or disable it, whichever is better for default).
>
> Hope it makes it a bit more clear what I suggested.
(Please do not double-space your messages.)
I have tried to explain this issue as clearly as I can. I will ask once
more: Do you understand that Elisp code written in the way you propose
would not be compatible with existing tools which parse Elisp? And that
such tools would require modification to parse such code correctly?
Stefan suggested ways to implement your idea as an alternative, literate
syntax, in a separate file format, by writing it in Elisp, using advice
and/or configuration variables, so that modification of the parser in C
would not be required, and the existing Elisp syntax and parser would
remain unchanged. That is a great idea. Why don't you want to do that?
next prev parent reply other threads:[~2019-12-18 23:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 15:45 Christmas wish: Literate Elisp arthur miller
2019-12-12 17:29 ` Stefan Monnier
2019-12-14 4:40 ` Sv: " arthur miller
2019-12-14 14:08 ` Stefan Monnier
2019-12-15 8:37 ` arthur miller
2019-12-16 12:01 ` Sv: " arthur miller
2019-12-16 13:41 ` Stefan Monnier
2019-12-16 14:02 ` Sv: " arthur miller
2019-12-16 16:07 ` Jonathan Leech-Pepin
2019-12-17 2:09 ` arthur miller
2019-12-17 11:06 ` Adam Porter
2019-12-18 16:29 ` Sv: " arthur miller
2019-12-18 18:49 ` Adam Porter
2019-12-18 20:04 ` Sv: " arthur miller
2019-12-18 23:18 ` Adam Porter
2019-12-18 23:53 ` Sv: " arthur miller
2019-12-20 15:58 ` Unknown
2019-12-18 21:18 ` Sv: Sv: Sv: " Stefan Monnier
2019-12-18 22:43 ` Christmas wish: Literate Elisp (Intro) VanL
2019-12-19 0:05 ` Sv: " arthur miller
2019-12-18 22:59 ` Sv: Sv: Sv: Christmas wish: Literate Elisp Adam Porter
2019-12-18 23:18 ` Sv: " arthur miller
2019-12-18 23:52 ` Adam Porter [this message]
2019-12-19 0:02 ` Sv: " arthur miller
2019-12-19 0:42 ` chad
2019-12-19 1:50 ` Jean-Christophe Helary
2019-12-20 0:55 ` Sv: " arthur miller
2019-12-20 15:00 ` Stefan Monnier
2019-12-20 15:50 ` Stefan Monnier
2019-12-20 15:50 ` Sv: " arthur miller
2019-12-20 16:17 ` Stefan Monnier
2019-12-20 16:34 ` Eduardo Ochs
2019-12-21 1:18 ` Sv: " arthur miller
2019-12-21 5:24 ` Eduardo Ochs
2019-12-21 5:52 ` Sv: " arthur miller
[not found] ` <VI1P194MB042965777086C4466B7FF5EC962C0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM>
2019-12-21 15:29 ` arthur miller
[not found] ` <VI1P194MB0429A123183C15AF8EC3956B962C0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM>
[not found] ` <jwv7e2pln3s.fsf-monnier+emacs@gnu.org>
[not found] ` <VI1P194MB0429F37A29A2720037CAD9F9962C0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM>
2019-12-22 7:01 ` Sv: " arthur miller
2019-12-20 16:51 ` Phillip Lord
2019-12-21 1:16 ` Tim Cross
2019-12-21 4:24 ` Sv: " arthur miller
2019-12-21 6:41 ` Tim Cross
2019-12-21 9:39 ` VanL
2019-12-21 14:17 ` Sv: " arthur miller
2019-12-14 4:16 ` Richard Stallman
2019-12-14 5:05 ` Sv: " arthur miller
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=87v9qdp4x8.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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 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.