Is there any developer out there who is working on #GTK4/#libadwaita GUI editor for typesetting documents in #latex/#typst. As much as I love them, modal editors like #vim/#helix are not for me.
After couple of hours poking around I now know how to embed #typst markup from yaml to a typst document :-)
I’m working on resume made with typst (as I’m looking to find a new job by end of September), and in that I’m using #yaml file to separate presentation from the content. Job descriptions can involve links, and thus those entries need to be evaluated.
First observation was:
#eval(job.description, mode: "markup")
If mode-parameter is not defined, typst will try to parse the string as an expression (i.e. mode: "code" is the efault, which is feasible in this case.
Another problem was the use of the hash character for tags, which is used for comments in yaml.
I sorted that out by putting every description into double quotes after trying a few different approaches:
description:
"I first worked on Keystone Security Monitor for RISC-V by enabling it
for CVA6 running on FPGA. This work was part of the EU funded
<a class="hashtag" data-tag="link" href="https://social.kernel.org/tag/link" rel="tag ugc">#link</a>("https://www.spirs-project.eu/")[SPIRS project].
It involved
tuning the
<a class="hashtag" data-tag="link" href="https://social.kernel.org/tag/link" rel="tag ugc">#link</a>("https://buildroot.org/")[BuildRoot]
based embedded stack, and
fixing various
<a class="hashtag" data-tag="link" href="https://social.kernel.org/tag/link" rel="tag ugc">#link</a>("https://github.com/keystone-enclave/keystone/issues/378")[issues].
in the OpenSBI firmware.
For the second half of my contract I'm enabling Linux for the new SoC's
developed by
<a class="hashtag" data-tag="link" href="https://social.kernel.org/tag/link" rel="tag ugc">#link</a>("https://sochub.fi/")[SocHub project]."
The screenshot shows the end result.
Nothing too complicated but took some time to find working patterns so putting here as a #note for myself :-)
This morning I'm looking at #typst.
The first thing in the tutorial (https://typst.app/docs/tutorial/writing-in-typst/) is how to write a header, and it annoys me that it makes the same mistake HTML, and everything following HTML, made: you specify the level of the heading absolutely, and it's not scoped to a section of the document.
So when you want to have a heading one level lower, you have to know what level the previous heading was. And you can't tell how much of the document the heading applies to, only inferring it as going until the next header of the same or higher level.
I've always wondered why #TeXLaTeX has
\section{name}
instead of
\begin{section}{name} ... \end{section}
@christianp at first I was wondering why you would want an error message. Then I realized that this was generated by my reader in response to something you had entered that was invalid latex.
This is an interesting conundrum in how to present code in an environment that respond to that code:
@christianp The command line tool is literally a single binary that recompiles within milliseconds after you press save in your editor. That said, the web interface is faster since it recompiles on keypress, so I don't see a problem with sticking to it
I haven't tried #Typst yet, but if it has good error messages, native SVG support, and #wasm plugins, is there any chance it's not amazing? I'm so stoked to check it out now.
Dovete scrivere dei paper? O, più frivolmente, volete scrivere giochi di ruolo con un discreto layout? Odiate Word, non siete mai riusciti a venire a patti con LaTeX e volete qualcosa tipo il markdown come difficoltà? Date una possibilità a #typst ( https://typst.app ). C'è sia l'IDE online che l'interprete, è molto promettente e con pochi sbattimenti sono riuscito a creare il layout 2colonne + sfondo di D&D3 :-)
Playing around with #typst it’s like a dream come true so far. I edit in #emacs, changes show up in the generated pdf very quickly with the command line tool in watch mode. No fussing around with ponderous toolchains. Next up converting a medium size doc with a lot of equations from #asciidoc.
@ambihelical
Hey I'm new to #emacs and I'd love to integrate #typst into it. I saw that there is a treesitter module but I'm not knowledgeable enough to set it up properly. Maybe you know a bit more on how to accomplish this?
Thanks to some incredible toil+creativity by one of our equally incredible designers at work, I should have a decent example of using #Quarto + #Typst + #Observable Plot + (ofc) #RStats to generate data-driven PDF reports with a fairly complex multi-page layout ready to blog and git sometime next week. #StayTuned