emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonathan McHugh <indieterminacy@libre.brussels>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: ludo@gnu.org, orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org to ConTeXt exporter?
Date: Tue, 29 Dec 2020 22:51:05 +0100	[thread overview]
Message-ID: <871rf8l1rq.fsf@libre.brussels> (raw)
In-Reply-To: <87v9clolyd.fsf@posteo.net>

Hello Juan,

I investigated further the Context engine for Skribilo:
https://git.savannah.gnu.org/gitweb/?p=skribilo.git;a=tree;f=src/guile/skribilo/engine;h=9c6353eb7c6eae70de007c2f0a8f01092ae669a2;hb=HEAD

While I cant comment on it's Context engine functionality or efficacy, it clearly has a
decent breakdown of usecases across its 1300 lines. It appears to have
had low updates frequency, probably as a consequence of the stability of
Context's syntax (rather than the momentum of the DSL). It may be useful
as a checklist of key terms to tick off, if not a consideration for
framing anything to serve Org-Moders.

I have CC’d Ludovic Courtès, who has spearheaded Skribilo and all the
commits for it’s Context engine. Judging by his output within the Guix
community it’s possible that he may have some insights concerning this
thread:
https://lists.gnu.org/archive/html/emacs-orgmode/2020-12/msg00731.html

Part of Skribilo’s homepage blurb intrigued me:
"Last but not least, Skribilo can be thought of as a complete document
programming framework for the Scheme programming language that may be
used to automate a variety of document generation tasks. Technically,
the Skribilo language/API is an embedded domain-specific language
(EDSL), implemented via so-called “deep embedding”. Skribilo uses GNU
Guile 3.0 or 2.x as the underlying Scheme implementation."
https://nongnu.org/skribilo/index.html
Still early in my Lisp journey, I do not know whether it would be
abhorrent/inelegant for the eLisp orientation of Org-Mode to defer to Guile (at the
backend) for outputting in different formats.

Kind regards,


Jonathan

Juan Manuel Macías <maciaschain@posteo.net> writes:

> Hello, Jonathan,
>
> Jonathan McHugh <indieterminacy@libre.brussels> writes:
>
>> I have wondered about the interoperability between Context and Latex.
>>
>> As somebody who (previously) invested a lot of time into Latex, my migration to
>> Context (due to its emphasis on Lua) grew problematic once other commitments
>> grew.
>
> What I like about ConTeXt is its (let's say) avant-garde vocation. But
> for my everyday work I prefer LaTeX: more extensible, more versatile,
> even more documented. But we must accept that ConTeXt is also an
> advanced typographic laboratory where many functionalities also end up
> in LaTeX over time. In fact, as far as I know, the future LaTeX3 adopts
> some ideas from ConTeXt.
>
> On Lua, LuaLaTeX also has good support. And many new LaTeX packages are
> already getting very good use of LuaTeX features.
>
>> The lack of Context support in Org-Mode has made me consider reverting
>> back to Latex.
>
> I know some advanced ConTeXt users (I am not) who are very interested in
> migrating to Org Mode. In that aspect, I think a native exporter to
> ConTeXt would be of great help.
>
> Generally speaking, I think Org is the perfect interface to use TeX and
> friends. One of the things I like the most about Org Mode is that it
> allows working in (La)TeX at a very high level. Of course, for advanced
> use, the more you know about LaTeX and TeX, the better. For example, if
> I work on a large book, I usually write the entire configuration (the
> preamble, my macros, my LaTeX code, etc.) to an Org file, and then I generate
> a Preamble.tex file using tangle. I have a master file and several
> subdocuments for the parts and sections of the book. And I make heavy
> use of Org Publish. But in all that workflow, LaTeX is always in the
> background. It is mainly a matter of comfort: I love TeX and its
> derivatives, its power and its typographic refinement, but its language
> is very verbose and the sources are difficult to debug. Org mode is much
> more human readable. And even much more readable and comfortable than
> Markdown.
>
>> If I had a lot of time it would be wonderful to develop parsing
>> expression grammars to capture it all, irrespective of direction ... mmm time....
>
> Yes, time is the problem: I think TODO lists were invented to have a
> foot of mud in the future :-)
>
> Regards,
>
> Juan Manuel     


-- 
Jonathan McHugh
indieterminacy@libre.brussels


  parent reply	other threads:[~2020-12-29 21:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 13:38 Org to ConTeXt exporter? Juan Manuel Macías
2020-12-28 15:04 ` Marcin Borkowski
2020-12-28 15:38   ` Juan Manuel Macías
2020-12-28 16:09     ` Jonathan McHugh
2020-12-28 17:54       ` Juan Manuel Macías
2020-12-28 19:06         ` Jonathan McHugh
2020-12-29 21:51         ` Jonathan McHugh [this message]
2021-01-04  9:41           ` Ludovic Courtès
2020-12-28 16:23   ` Diego Zamboni
2020-12-28 18:03     ` Juan Manuel Macías
2020-12-28 19:23       ` Diego Zamboni
2020-12-28 20:03       ` Marcin Borkowski
2020-12-29 16:05         ` Juan Manuel Macías
2021-01-08  2:37 ` Jason Ross
2021-01-09 17:42   ` Juan Manuel Macías
2021-01-13  1:16     ` Jason Ross
2021-01-08  3:52 ` Jason Ross

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rf8l1rq.fsf@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=emacs-orgmode@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maciaschain@posteo.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).