From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Christmas wish: Literate Elisp Date: Sat, 21 Dec 2019 17:41:29 +1100 Message-ID: References: <87h81vhrek.fsf@russet.org.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004070d1059a3116e1" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="184022"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel , Phillip Lord To: arthur miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 21 07:42:01 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iiYSe-000li8-Q2 for ged-emacs-devel@m.gmane.org; Sat, 21 Dec 2019 07:42:01 +0100 Original-Received: from localhost ([::1]:37172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iiYSc-0001zC-UX for ged-emacs-devel@m.gmane.org; Sat, 21 Dec 2019 01:41:58 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56975) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iiYST-0001un-SY for emacs-devel@gnu.org; Sat, 21 Dec 2019 01:41:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iiYSQ-0001qi-5F for emacs-devel@gnu.org; Sat, 21 Dec 2019 01:41:49 -0500 Original-Received: from mail-ot1-x336.google.com ([2607:f8b0:4864:20::336]:34667) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iiYSP-0001n7-O1 for emacs-devel@gnu.org; Sat, 21 Dec 2019 01:41:45 -0500 Original-Received: by mail-ot1-x336.google.com with SMTP id a15so14840275otf.1 for ; Fri, 20 Dec 2019 22:41:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qk5l++7Ngv9Ok3CaLjeExYotRTQaEYFdBabwvcc4aAY=; b=rv05W7a89rxPxGmcasIwR43kSgA0Wrr7gKZdgehLBVIUOQa7vzssHA+qQtacVvkIXZ UFUqE7W19fHihB09zdk3A9Rur+5h81anj64HCDvtnYAW/Eh7289BdsqmsuJ4Ym/Ho8Jq +GQLA7ikeOOeQwDdQdMHAkHWA8RzU1qm6hYqDWRxvINKDGPQVZtLVe3KK9wwzAc7CeWF TGfsR2yTzdNod61B7GlGruTQGdhlU2ofWoPOnKbqHy4d3gssHu7w6WLH0x6TTDfh3zKy +KuyELLOZ1pYI//KCP+SFMh1T/i0tDYYCg1uNZz7EccVyrUoTvJbTqc4gwIGvJGqpUDq Gr5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qk5l++7Ngv9Ok3CaLjeExYotRTQaEYFdBabwvcc4aAY=; b=FrIdAZSo9ITpTwjis59/gxqqNAjhIZ4Q6nVfh1CvUbayqx3EjbVY2SMUow/XD0o4By kwkDgEVaqx4KGvStDlzRu5FU02BlHQl8nRSQ/HgxplqIJJz9PrDN3BQhsv0ZANbhWKB9 l6v1kyEqLl/fuTMjQF7hhyGnR61Vc9htjh+Lupuuce0pSmYsdDVKe04n5tBwdEtabx0j ZJNjWx2smCRsHG9TcFzM8ZmfKEosY4p8mz11SZuyCivomEJ3lAPvIWzpqgQpfBZwTRrN uN+pKLpIwNYAXgTlmPzyMdngMmXhrTvp61n1BzNk2OpsHhpTRxAa0fmtc666ziELPLdC /2rQ== X-Gm-Message-State: APjAAAUrBwAD52ajs3+H0ea+dwwBREExqmlmnH2f5iZ4R54vqX2OIXUv acjvII9NnOshoHwKgkvhEzvR9jdlyM5h/l1DVm0= X-Google-Smtp-Source: APXvYqylZLRqLda41jTBUiLrTB8bbX6Mol+t5QZ6MJMnVLPloTW5AWHMKIUUec5XNZm/aagfGE+InXEj1xtunZlMuJI= X-Received: by 2002:a05:6830:1bda:: with SMTP id v26mr18882194ota.314.1576910500949; Fri, 20 Dec 2019 22:41:40 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::336 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243533 Archived-At: --0000000000004070d1059a3116e1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I certainly don't want to discourage you from experimenting and trying out ideas - this is what makes Emacs great. What I would encourage is, in this case, using org-mode to develop something non-trivial (possibly your literate elsip idea) as it will give you the elisp experience you need and more importantly, a taste of a form of literate programming, which will both highlight the limitations of the current implementation (ie.e. org-mode) and possibly, the literate programming approach itself. The key point is that it needs to be non-trivial. Most of the limitations I found with literate programming really only become evident in larger projects. For smaller things, it works great and it is how I maintain my own init.el file. It is only when you do something more complex that weaknesses become evident. I would also highly recommend re-visiting Stepan's posts after you have gained some more elisp experience. Stephan is one of the most experienced and knowledgeable contributors on this list. His advice and guidance are valuable and should be considered carefully. While it may not be obvious why he is making a recommendation, you can be fairly confident it is based on experience and deep knowledge of Emacs. Spending the time to analyze his suggestions and looking into them in detail is likely to save you a lot of time going down dead ends or having to re-design/re-factor things as you discover them the hard way. I hope you don't become too discouraged and do work at implementing your idea. At the very least, you may be able to find ways to improve or enhance org-mode, which is always a valuable contribution. On Sat, 21 Dec 2019 at 15:24, arthur miller wrote: > Very interesting and nice read, thank you for taking your time Tim. > > I have no idea if literate programmign is very good or not.I certainly > don't do it much. I never intended to present it as some kind of modern, > silver bullet or something. I hope I didn't sound like that. I am aware > that it is not the new idea either. > > Personally I really like ORG-mode and ipossibility to mix languages > in one and same file. I was just looking at something I was working > with and thought it had so much noise around stuff that matters. I > wondered if it could be simplified. Then I got the idea that elisp could > actually be written without special markers, since in elisp we put > all code between () (with some exceptions). As I stated in my very first > mail where I asked if we could have this in Emacs, I am not sure myself > if this is somethign very usefull or just a cool gimmick. I personally ca= n > see some nice use cases, but it might not be of value to somebody else. > I can maybe make a video where I play with it a bit after the hollidays i= t > it is interesting. > > Yes, you are right about tools, checkers and so on. If we call it "litera= l > elisp" > then one thing should be clear: literal elisp and elisp are not same. All > elisp is literal elisp, but all literal elsip would not be elisp. > Relevance of > this should be obvious to anyone, all current tools work with elisp, not > literal elisp. So if you open a buffer and type comments without ';' in > front, of course, identation, font locking etc will be confused. This > should > be self evident fact. Literal elisp would be a superset of elisp (with on= ly > one extra feature - different handling of comments). This is regardless > of implementation language, just as elisp would be same language > regardless if interpreter is written in C or Rust or Elisp for that > matter. > > While yes, I have hacked C code, it does not mean I have altered how > Elisp works. Elisp is still the very same, so even with the patch all Eli= sp > should still work and parse the very same in Emacs and all external > tools as it does since the beginning of the time. Look at the patch, appl= y > it, run it. There is even boolean flag that eliminates that code at run > time > if desired. I don't know how your lisp and your patches worked, not all > Lisps are created equal. It is interesting experience you share, and I do > understand what you mean and I agree with you. I am very conservative > myself when it comes to making changes, what is not broken should not > be repaired. I am also very pragmatic. I don't do changes just for > changes > sake, I do it only if it does something useful. > > Also, don't misstake me, I don't insist on change be done in C. I have do= ne > those changes the way I did because I am new to Emacs internals hacking. > I am not new to programming, but I have no idea how they do in Emacs code= , > what API calls are there and so on. I also have limited with time. So I > have > hacked where Emacs self help functionality and debugger has thrown me in. > > It turned to be some elisp and some C. I am sure it is possible to do thi= s > in > different ways, and if somebody is willing to implement some other way, > please go ahead. Of those two ideas that Stefan outlined, I am not willin= g > to implement them. First one is super brutish and inneficient, the second > one is sane but involves too much work. I don't have knowledge and time > to put into it. But I am sure it can be done. > > ------------------------------ > *Fr=C3=A5n:* Tim Cross > *Skickat:* den 21 december 2019 02:16 > *Till:* Phillip Lord > *Kopia:* arthur miller ; emacs-devel < > emacs-devel@gnu.org> > *=C3=84mne:* Re: Christmas wish: Literate Elisp > > I've been watching this thread and resisting adding to it, but feel now > might be when I can contribute something useful. > > This whole discussion seems to centre around some views that literate > programming for lisp is a positive way forward and therefore, making > changes to both C and Elisp parsing is a good idea if it means we can mov= e > to a 'modern' literate programming model with greater ease. > > As someone who has done literate programming for non-trivial projects > (i.e. something other than my .emacs file), I think this assumption needs > to be challenged. Literate programming has been around for a long time, b= ut > has failed to gain traction. Why? Is it due to the existing tools or is i= t > something more fundamental? > > I have been a fan of Donald Knuth's work for a long time. When I first > came across literate programming in the mid-90s, I thought it sounded > really interesting and a potentially great approach to writing code. A fe= w > of us adopted this approach in our project and embarked on this new path = of > discovery. Unfortunately, the reality just did not hold up to the promise= . > Some of this was due to limitations in tooling (relating to the 'weave' a= nd > 'tangle' tools of the time), but a big part really just failed because > people don't move between prose and code that easily and we don't maintai= n > the prose as well as the code. In the end, you just have lots of > out-of-date prose mixed in with your code, which is often more misleading > than no prose at all. > > The tools at the time were particularly poor when it came to working > within a REPL type environment. This was partly because they were a two > step process (tangling) and you could only go in one direction (getting > chagnes made in the REPL back into your source was distracting and often > forgotten, so work was frequently lost). Dealing with scope, namespaces e= tc > was a pain in a system which relied on 'tangling' of source files in orde= r > to get the final output and nearly all supporting utilities (code > formatters, highlighting, linters etc) were broken. Like others who have > posted in this thread, we thought it could all be improved if you could > eliminate the weaving/tangling and be free to just write prose within you= r > code, so we tried to do this with the lisp we were using (sorry, can't > remember what lisp flavor it was). At first glance, it looked very easy t= o > do - a few tweaks to the parser, some new reader macros and we should be > fine. On one level, it did fix some of the issues, but we did find lots o= f > unforeseen edge cases and it added sufficient additional complexity to th= e > whole system that in the end, we decided it just didn't deliver the > benefits we had hoped for. At the end of the day, it wasn't the tools or > the implementation which killed it - it was simply that literate > programming simply didn't fit with how people like to code. It was one of > those things which sounds nice in theory, but for most, fails in practice= . > > We did find the approach works better for some languages than others. For > example, languages like C, where you have a code, compile, run, test cycl= e, > it wasn't oo bad. However, for languages where you often included a more > REPL driven style of devleopment, where lots of devleopment is done as > experimentation/refinement at the repl, the paradigm added very little an= d > more often than not, just got in the way. We did find it was useful for > smaller tasks and configuration management, but for larger projects, > especially with teams of developers, it didn't stand up. > > So, my advice, for what it is worth is > > Implement a solution which does NOT require any modifications to either > the elisp parser or C code and use it to develop some non-trivial elisp > packages. You could probably base it on org-mode. My suspicion is that yo= u > will find that after some time, it really doesn't deliver what you hoped. > However, if I'm wrong, it will provide the necessary experience and > familiarity to help guide a more refined and targeted model for working > with literate programming and elisp. > > Don't under estimate the effort or impact making changes to either the > elisp parser or C sources will have. There has been a number of comments = in > this thread which makes it sound like you would just need to 'tweak' the > parser and everything will work. That 'tweaking' is far more complicated > than it might seem on the surface. One of the main benefits of lisp > dialects is there simple syntax and the idea of code as data. Any changes > made to either the syntax or parsing of elisp is going to impact on lots = of > things, many of which none of us have even thought about yet. > > My feeling is that if literate programming is a great way forward, this > will be evident in the number of people who start using an elisp literate > programming mode. If this does turn out to be the case, then we can use t= he > experiences from many people who are using that mode to see what can be > done to develop the paradigm further. This may involve low level C or els= ip > parser or syntax changes, but they will be based on experience and demand= . > > On Sat, 21 Dec 2019 at 03:56, Phillip Lord > wrote: > > > > Stefan Monnier writes: > > >> My proposal is to slightly change Elisp parser to treat lines that sta= rt > >> with any other printable character but '(' as a start of comment and t= o > >> simply ignore the line, just as it treats ';' as a comment. > > > > The `sexpresso` Haskell package follows the same idea ;-) > > > > As for using it in Elisp: I don't think there's anything stopping anyon= e > > 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. > > > I'm very late to this thread, for which apologies. > > My own package, lentic, could achieve this. It's gives you two > visualisations of the same file; so one with comment characters, and one > without. You can then do the literate part in one mode and the coding > part in another. > > It already supports org-mode delination markers; it could be made to > support brackets as a delineator too. > > Phil > > > > -- > regards, > > Tim > > -- > Tim Cross > > --=20 regards, Tim -- Tim Cross --0000000000004070d1059a3116e1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I certainly don't want to discourage you from exp= erimenting and trying out ideas - this is what makes Emacs great. What I wo= uld encourage is, in this case, using org-mode to develop something non-tri= vial (possibly your literate elsip idea) as it will give you the elisp expe= rience you need and more importantly, a taste of a form of literate program= ming, which will both highlight the limitations of the current implementati= on (ie.e. org-mode) and possibly, the literate programming approach itself.= The key point is that it needs to be non-trivial. Most of the limitations = I found with literate programming really only become evident in larger proj= ects. For smaller things, it works great and it is how I maintain my own in= it.el file. It is only when you do something more complex that weaknesses b= ecome evident.

I would also highly recommend = re-visiting Stepan's posts after you have gained some more elisp experi= ence. Stephan is one of the most experienced and knowledgeable contributors= on this list. His advice and guidance are valuable and should be considere= d carefully. While it may not be obvious why he is making a recommendation,= you can be fairly confident it is based on experience and deep knowledge o= f Emacs. Spending the time to analyze his suggestions and looking into them= in detail is likely to save you a lot of time going down dead ends or havi= ng to re-design/re-factor things as you discover them the hard way.

I hope you don't become too discouraged and do w= ork at implementing your idea. At the very least, you may be able to find w= ays to improve or enhance org-mode, which is always a valuable contribution= .

On Sat, 21 Dec 2019 at 15:24, arthur miller <arthur.miller@live.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
Very interesting and nice read, thank you for taking your time Tim.

I have no idea if literate programmign is very good or not.I certainly=C2= =A0
don't do it much. I never intended to present it as some kind of modern= ,
silver bullet or something. I hope I didn't sound like that. I am aware=
that it is not the new idea either.

Personally I really like ORG-mode and ipossibility to mix languages
in one and same file. I was just looking at something I was working
with and thought it had so much noise around stuff that matters. I=C2=A0
wondered if it could be simplified. Then I got the idea that elisp could
actually be written without special markers, since in elisp we put
all code between () (with some exceptions). As I stated in my very first
mail where I asked if we could have this in Emacs, I am not sure myself
if this is somethign very usefull or just a cool gimmick. I personally can<= /div>
see some nice use cases, but it might not be of value to somebody else.
I can maybe make a video where I play with it a bit after the hollidays it<= /div>
it is interesting.=C2=A0

Yes, you are right about tools, checkers and so on. If we call it "lit= eral elisp"=C2=A0
then one thing should be clear: literal elisp and elisp are not same. All
elisp is literal elisp, but all literal elsip would not be elisp. Relevance= of=C2=A0
this should be obvious to anyone, all current tools work with elisp, not=C2= =A0
literal elisp. So if you open a buffer and type comments without ';'= ; in=C2=A0
front, of course, identation, font locking etc will be confused. This shoul= d
be self evident fact. Literal elisp would be a superset of elisp (with only=
one extra feature - different handling of comments). This is regardless
of implementation language, just as elisp would be same language=C2=A0
regardless if=C2=A0interpreter is written in C or Rust or Elisp for that matte= r.

While yes, I have hacked C code, it does not mean I have altered how=C2=A0<= /div>
Elisp works. Elisp is still the very same, so even with the patch all Elisp=
should still work and parse the very same in Emacs and all external=C2=A0
tools as it does since the beginning of the time. Look at the patch, apply<= /div>
it, run it. There is even boolean flag that eliminates that code at run tim= e
if desired. I don't know how your lisp and your patches worked, not all=
Lisps are created equal. It is interesting experience you share, and I do=C2=A0
understand what=C2=A0you mean and I agree with you. I am very = conservative=C2=A0
myself when it comes to making changes, what is not broken should not=C2=A0=
be repaired.=C2=A0I am also very pragmatic. I don't do changes just for ch= anges=C2=A0
sak= e, I do it=C2=A0only if it does something useful.=C2=A0=C2=A0

Also, don't misstake me, I don't insist on change be done in C. I h= ave done
those changes the way I did because I am new to Emacs internals hacking.
I am not new to programming, but I have no idea how they do in Emacs code,<= /div>
what API calls are there and so on. I also have limited with time. So I hav= e
hacked where Emacs self help functionality and debugger has thrown me in.

It turned to be some elisp and some C. I am sure it is possible to do this = in=C2=A0
different=C2=A0ways, and if somebody is willing to implement some other way,
ple= ase go ahead. Of those two ideas that Stefan outlined, I am not willing
to = implement them. First one is super brutish and inneficient, the second=C2= =A0
one= is sane but=C2=A0involves too much work. I don't have knowledge an= d time
to = put into it. But I am sure it can be done.

Fr= =C3=A5n: Tim Cross <theophilusx@gmail.com>
Skickat: den 21 december 2019 02:16
Till: Phillip Lord <phillip.lord@russet.org.uk>
Kopia: arthur miller <arthur.miller@live.com>; emacs-devel <emacs-devel@gnu.org><= br> =C3=84mne: Re: Christmas wish: Literate Elisp
=C2=A0
I've been watching this thread and resisting adding to it, but fee= l now might be when I can contribute something useful.

This whole discussion seems to centre around some views that literate = programming for lisp is a positive way forward and therefore, making change= s to both C and Elisp parsing is a good idea if it means we can move to a &= #39;modern' literate programming model with greater ease.

As someone who has done literate programming for non-trivial projects = (i.e. something other than my .emacs file), I think this assumption needs t= o be challenged. Literate programming has been around for a long time, but = has failed to gain traction. Why? Is it due to the existing tools or is it something more fundamental?

I have been a fan of Donald Knuth's work for a long time. When I f= irst came across literate programming in the mid-90s, I thought it sounded = really interesting and a potentially great approach to writing code. A few = of us adopted this approach in our project and embarked on this new path of discovery. Unfortunately, the reality jus= t did not hold up to the promise. Some of this was due to limitations in to= oling (relating to the 'weave' and 'tangle' tools of the ti= me), but a big part really just failed because people don't move between prose and code that easily and we don't maintai= n the prose as well as the code. In the end, you just have lots of out-of-d= ate prose mixed in with your code, which is often more misleading than no p= rose at all.

The tools at the time were particularly poor when it came to working w= ithin a REPL type environment. This was partly because they were a two step= process (tangling) and you could only go in one direction (getting chagnes= made in the REPL back into your source was distracting and often forgotten, so work was frequently lost). = Dealing with scope, namespaces etc was a pain in a system which relied on &= #39;tangling' of source files in order to get the final output and near= ly all supporting utilities (code formatters, highlighting, linters etc) were broken.=C2=A0 Like others who have posted = in this thread, we thought it could all be improved if you could eliminate = the weaving/tangling and be free to just write prose within your code, so w= e tried to do this with the lisp we were using (sorry, can't remember what lisp flavor it was). At first glance= , it looked very easy to do - a few tweaks to the parser, some new reader m= acros and we should be fine. On one level, it did fix some of the issues, b= ut we did find lots of unforeseen edge cases and it added sufficient additional complexity to the whole system th= at in the end, we decided it just didn't deliver the benefits we had ho= ped for.=C2=A0 At the end of the day, it wasn't the tools or the implem= entation which killed it - it was simply that literate programming simply didn't fit with how people like to code. I= t was one of those things which sounds nice in theory, but for most, fails = in practice.

We did find the approach works better for some languages than others. = For example, languages like C, where you have a code, compile, run, test cy= cle, it wasn't oo bad. However, for languages where you often included = a more REPL driven style of devleopment, where lots of devleopment is done as experimentation/refinement at the rep= l, the paradigm added very little and more often than not, just got in the = way.=C2=A0 We did find it was useful for smaller tasks and configuration ma= nagement, but for larger projects, especially with teams of developers, it didn't stand up.

So, my advice, for what it is worth is

Implement a solution which does NOT require any modifications to eithe= r the elisp parser or C code and use it to develop some non-trivial elisp p= ackages. You could probably base it on org-mode. My suspicion is that you w= ill find that after some time, it really doesn't deliver what you hoped. However, if I'm wrong, it w= ill provide the necessary experience and familiarity to help guide a more r= efined and targeted model for working with literate programming and elisp.

Don't under estimate the effort or impact making changes to either= the elisp parser or C sources will have. There has been a number of commen= ts in this thread which makes it sound like you would just need to 'twe= ak' the parser and everything will work. That 'tweaking' is far more complicated than it might seem on the = surface. One of the main benefits of lisp dialects is there simple syntax a= nd the idea of code as data. Any changes made to either the syntax or parsi= ng of elisp is going to impact on lots of things, many of which none of us have even thought about yet.

My feeling is that if literate programming is a great way forward, thi= s will be evident in the number of people who start using an elisp literate= programming mode. If this does turn out to be the case, then we can use th= e experiences from many people who are using that mode to see what can be done to develop the paradigm furthe= r. This may involve low level C or elsip parser or syntax changes, but they= will be based on experience and demand.

On Sat, 21 Dec 2019 at 03:56, Phillip Lord <phillip.lord@russet.or= g.uk> wrote:


Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> My proposal is to slightly change Elisp parser to treat lines that= start
>> with any other printable character but '(' as a start of c= omment and to
>> simply ignore the line, just as it treats ';' as a comment= .
>
> The `sexpresso` Haskell package follows the same idea ;-)
>
> As for using it in Elisp: I don't think there's anything stopp= ing anyone
> from making such a `literate-elisp-mode` and even arrange for `load` t= o
> 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.


I'm very late to this thread, for which apologies.

My own package, lentic, could achieve this. It's gives you two
visualisations of the same file; so one with comment characters, and one without. You can then do the literate part in one mode and the coding
part in another.

It already supports org-mode delination markers; it could be made to
support brackets as a delineator too.

Phil



--
regards,

Tim

--
Tim Cross



--
regards,

Tim=

--
Tim Cross

--0000000000004070d1059a3116e1--