Comment by jimmar

Comment by jimmar 4 hours ago

4 replies

Markdown is the minimum viable product. It’s easy to learn and still readable if not rendered in an alternate format. It’s great.

For making PDFs, I’ve recently moved from AsciiDoc to Typst. I couldn’t find a good way to get AsciiDoc to make accessible PDFs, and I found myself struggling to control the output. Typst solves all of AsciiDoc’s problems for me.

But in the end, no markup language will make you write better. It’s kind of like saying that ballpoint pens are limiting your writing, so you should switch to mechanical pencils.

undeveloper 4 hours ago

typst looks interesting -- but how are you writing it? from what I looked at, it looks like theres an official web editor and a vscode plugin with limited support. this feels pretty limited, as someone who came in expecting something like obsidian.

  • TRiG_Ireland 3 hours ago

    I'm not aware of any limitations in the Tinymist plugin.

    And you can just write it in the plain text editor of your choice, and keep an eye on the PDF with typst watch.

    • addaon an hour ago

      > I'm not aware of any limitations in the Tinymist plugin.

      I looked into this a while ago, and couldn't find a workflow I could live with. Have things improved? What's the workflow like for working on an image in, say, OmniGraffle to include in the document? Does text search in embedded PDFs work these days? LinkBack so I can edit the images easily inline?

  • MillironX 3 hours ago

    I've started experimenting with Typst for a few documents, and here's my stack:

    - Zed editor with Typst plugin

    - Tinymist LSP settings turned on to render on save in Zed, see https://code.millironx.com/millironx/nix-dotfiles/src/commit...

    - Okular open to the output document. Okular refreshes the document when changed on disk.

    It's not as polished as say, LaTeX Workshop in VSCode, but it gets the job done.