From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: outline-minor-mode and org-mode capabilities for programming languages
Date: Tue, 11 May 2021 04:00:49 +0200 [thread overview]
Message-ID: <trinity-22f4134f-463b-4814-8733-655e6901e9d9-1620698449154@3c-app-mailcom-bs03> (raw)
In-Reply-To: <YJln4T7O11owlhNz@protected.localdomain>
> Sent: Tuesday, May 11, 2021 at 5:05 AM
> From: "Jean Louis" <bugs@gnu.support>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: outline-minor-mode and org-mode capabilities for programming languages
>
> * Christopher Dimech <dimech@gmx.com> [2021-05-10 15:53]:
> > > How about instead of embedding code in the text, to embed text in the
> > > code?
> >
> > Originally I had bought in the idea of Knuth and others, but did not
> > buy on their results with literate programming. What I find
> > valuable is the the development of protowriting that communicates
> > limited information. They maybe a parser that goes through the to
> > obtain a more literate translation.
>
> Simple Way to Document Code with Markdown, grep, and pandoc | Richard Zach
> https://people.ucalgary.ca/~rzach/blog/2014/05/simple-way-to-document-code-with-markdown-grep-and-pandoc.html
>
> Basically, few shell tools and a workflow may replace all the
> "literate programming" tools there are. Just write the markup in
> comments, and pre-process the file with `cut', `grep', etc. to
> generate output.
>
> > > That is where embedding text into the code comes in. There need not be
> > > visible text in the code, but one could click and get the same
> > > function elaborated with the markup source, markup result such as PDF,
> > > and one could jump back to the code.
> >
> > The strategy of hiding is good. But I promote the idea of having separate
> > files. Documentation in code will be limited, more elaborate schemes for
> > documunetation on a separate file. Most times the code is the place to check
> > things.
>
> That can be done by method using GNU Hyperbole or principle of it,
> just make each (defun ) or (defvar ) and maybe functions a button that
> points to something else, editable.
>
> Right now if I use M-RET with GNU Hyperbole it brings me to definition
> of a function, and often it works better than M-. that brings me also
> to definitions, but it will not find it at all times.
>
> > > In other words, don't make it too literate for illiterates.
> >
> > There has to be a background and foundation. For instance,
> > magnetism is one of those things that's just too difficult to
> > understand, except through an elaborate education in physics. In
> > computing, we have not arrived at that stage yet.
>
> Back in time we were making programs for schools that were very
> helpful for pupils to learn physics. We don't have much of it today.
I remember those - doing electical circuits, linear motion, etc. Were cool
stuff.
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> Sign an open letter in support of Richard M. Stallman
> https://stallmansupport.org/
> https://rms-support-letter.github.io/
>
>
next prev parent reply other threads:[~2021-05-11 2:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 8:53 outline-minor-mode and org-mode capabilities for programming languages Christopher Dimech
2021-05-09 9:11 ` Jean Louis
2021-05-09 12:35 ` Christopher Dimech
2021-05-09 12:45 ` Jean Louis
2021-05-09 13:00 ` Christopher Dimech
2021-05-09 16:27 ` Jean Louis
2021-05-09 17:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-09 17:50 ` Jean Louis
2021-05-09 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-09 19:09 ` Jean Louis
2021-05-10 1:49 ` Christopher Dimech
2021-05-10 6:22 ` Jean Louis
2021-05-10 6:53 ` Christopher Dimech
2021-05-10 7:32 ` Jean Louis
2021-05-10 8:32 ` Christopher Dimech
2021-05-10 9:29 ` Christopher Dimech
2021-05-10 9:31 ` Jean Louis
2021-05-10 10:01 ` Christopher Dimech
2021-05-10 11:43 ` Jean Louis
2021-05-10 12:52 ` Christopher Dimech
2021-05-10 17:05 ` Jean Louis
2021-05-11 2:00 ` Christopher Dimech [this message]
2021-05-10 10:27 ` Christopher Dimech
2021-05-10 11:53 ` Jean Louis
2021-05-10 12:32 ` Christopher Dimech
2021-05-10 16:07 ` Jean Louis
2021-05-11 2:26 ` Christopher Dimech
2021-05-10 8:46 ` Christopher Dimech
2021-05-10 9:15 ` Christopher Dimech
2021-05-10 9:33 ` Jean Louis
2021-05-10 6:08 ` Christopher Dimech
2021-05-10 1:25 ` Christopher Dimech
2021-05-09 13:02 ` Christopher Dimech
2021-05-09 16:34 ` Jean Louis
2021-05-09 14:02 ` Stefan Monnier via Users list for the GNU Emacs text editor
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-22f4134f-463b-4814-8733-655e6901e9d9-1620698449154@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).