msravi

Wait. I still export NFS mounts from my TrueNAS server and make them available to all other machines on my LAN (music, books, documents, photos, etc). The article and comments here give me the feeling that NFS is outadated and shouldn't be used anymore. Am I doing things wrong?

Very skeptical that this would work for me. None of the topics that Kagi chooses to "cover" in their seven or so stories for the day resonates with what I'd want to read. That's exactly why we have feeds that you can tune to your tastes and so on. Getting rid of endless scrolling and such might be a good thing though.

I prefer a more "physical" explanation - you have two carriers: sin(wt) and cos(wt), and you're modulating bits I and Q onto the two carriers and adding them up before transmitting. Now, mathematically, that's the same as representing the two bits as I+jQ and multiplying it with cos(wt)+jsin(wt). Demodulation is simply multiplying that output with the complex conjugate cos(wt)-jsin(wt), which in physical terms translates to mixing with a local oscillator output and low pass filtering.

> Just have a master settings.typ that you import in top1.typ, top2.typ and top3.typ?

Yes, but each included file (like education.typ, publications.typ, etc) should also get these settings propagated from top - which typst doesn't allow - the appropriate settings need to be included in each of these files.

> you can pass global settings at build time with `typst c --input name=value`

This is something I did not know - will check.

> Regarding point 2: you can put your settings in a file `settings.typ` and import it from multiple files.

Let's say I have 3 flavors of settings and 10 different typ files - normally I'd just have 3 flavors of top.typ (top1.typ, top2.typ, top3.typ) with the correct settings for each flavor with settings proagated to all 10 files. Compiling top1/top2/top3 would then create flavor1.pdf, flavor2.pdf, and flavor3.pdf

Now how do I do it with settings1.typ, settings2.typ and settings3.typ? I have to go into the 10 different files and include the appropriate settings file! Or employ hacks like creating a common settings.typ using bash in the Makefile and including the common settings.typ in the 10 different files.

Edit: This is an actual use case - I'm helping with a resume, and have 3 different resume styles - a resume, a cv, and a timeline - and different files like education, work experience, honors, awards, publications, projects, etc and the level of detail, style, and what is included or not in each is controlled by which resume style is active. In latex I did this using \newcommand and the ifthenelse package.

In typst, I have had to resort to passing these global settings as arguments to functions spread across these different files, so each resume item (function) instantiated from the top file has a bunch of parameters like detail_level = 1, audited_courses = true, prefix_year = false, event_byline = true, include_url = true, etc., which make the functions unweildy.

I have only two peeves with typst.

1. They should have carried forward the latex standard as-is for math, instead of getting rid of the backslash escape sequence, etc.

2. There is no way to share a variable across a file's scope - so can't have a setting that is shared across files - not even with state variables.

Other than this, typst is solid, and with the neovim editor and tinymist lsp, is great to write with.

Looks very good. Was looking to replace ltex (which is really slow), but for some reason the nvim-lspconfig filetype setting for harper doesn't seem to have (la)tex listed as a default, although markdown and typst are listed. Anyone knows why?

But doesn't seem like a bird strike issue here, right? And given the rarity of a dual engine failure, seems to point to not calling up full thrust? But seems to me that this kind of error would be more common without any technical safeguards?

...accessed through Obsidian (esp on mobile) -- On Android, you can "Open folder as vault"

Or neovim with FzfLua (on laptop)