From: Adam Porter <adam@alphapapa.net>
To: emacs-devel@gnu.org
Subject: Re: Sv: Sv: Sv: Christmas wish: Literate Elisp
Date: Wed, 18 Dec 2019 16:59:52 -0600 [thread overview]
Message-ID: <874kxxqlxz.fsf@alphapapa.net> (raw)
In-Reply-To: jwvpngls5bv.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Thre is no discussion of changing the existing syntax/semantic of
> Elisp here. Arthur is proposing a new file format/syntax as an
> alternative to the use of weave/tangle or Org-mode.
That's not my understanding of what Arthur is proposing. You did
propose an alternative file format in earlier messages when you wrote:
> As for using it in Elisp: I don't think there's anything stopping
> anyone from making such a `literate-elisp-mode` and even arrange for
> `load` to handle such a file (just like there is already a package
> that lets `load` work directly on .org files). I'd welcome such a
> package in GNU ELPA.
And:
> Note that in my comment above I meant it in existing Emacsen,
> i.e. without any modification to the C code. The idea is to make use
> of existing hooks such as `load-source-file-function` or
> `file-name-handler-alist`. I'm not sure what hook could be used to do
> the same with byte-compilation, but in the worst case, an advice
> should do the trick.
But Arthur has been proposing to alter the Emacs Elisp parser itself,
e.g. when he wrote:
> My proposal is to slightly change Elisp parser to treat lines that
> start with any other printable character but '(' as a start of comment
> and to simply ignore the line, just as it treats ';' as a comment
And:
> I was able to make readevalloop do what I want. It was rather trivial
> to implement this (once I realized how it works 🙂). Emacs built fine
> and I was able to test wtih eval-buffer and eval-regionwhich worked as
> intended.
> It was just 4 code lines, I just copied codeto parse comment and
> change the condition in if-statement:
> However, byte compiler is not happy about this. It emits warnings for
> every word out of code blocks as references to free variables. I am
> not sure where to look to patch it, maybe another day.
And:
> If we would just use directives in comments then we already have org +
> babel. But I think 4 extra lines of C code to enable this feature in
> eval-loop was a trivial price to pay :-).
> Now I just wonder how to change the bytecode compiler. Unfortunately
> it seems to be much more involved process. I don't know if I can do
> it, since I am not so acquainted with Emacs internals, so it would be
> cool if someone more knowledgeable can at least hint me if not help.
I've looked again at all messages in the thread. Am I missing
something?
next prev parent reply other threads:[~2019-12-18 22:59 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 ` Adam Porter [this message]
2019-12-18 23:18 ` Sv: Sv: Sv: Sv: Christmas wish: Literate Elisp arthur miller
2019-12-18 23:52 ` Adam Porter
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=874kxxqlxz.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.