Re: Comments wanted on code highlighting in PDF output

[Luca Fascione]

On Mon, Feb 21, 2022 at 9:01 PM Jean Abou Samra <jean@abou-samra.fr> wrote:

> Are you aware of
>
> https://myrealbook.vintherine.org/
>
> ?
>

I was not, the material I was working from was the openbook project, by
Mark Veltzer.
He's done all the heavy work, I'm just working on how to build his stuff
and make it beautiful.
(and using that work as an opportunity to learn stuff).

> Once I'm done with these, if there's still interest, I could see if I
> > can help with this stuff. I like parsey things fwiw.
> >
> > The idea of parsing lisp was because I was imagining you could scrape
> > the .scm source files to build a database of callables and their
> > signatures and then use that to guide highlighting examples found in
> > the docs. Wasn't aware of your other script
>
>
> Yeah, Scheme (at least its Guile incarnation) has enough
> reflective power that parsing it by hand is not necessary.
>

Yes, I've not done that much Lisp, but I have done a lot of TCL when I was
younger.
TCL is (very approximately) a lisp implementation with a fair few
liberties,
so aside from parens, ticks, commas and let, I feel relatively at home.
Like it would be in lisp, parsing TCL with TCL is kinda the whole point of
the language, almost.

I must say I miss the $ for dereferencing variables, the way Scheme has it
seems more confusing to me.
(and the parentheses... take some getting used to, esp with strange
indentation patterns)



> We actually do some parsing (scripts/build/lilypond-words.py),
> and that is what I hope to replace.
>

... with? Guile directly?

I like messing with language-y parse-y things a lot, if I can help
with anything, happy to

L