!trippinthroughtime@lemmy.ca

IIUC, their solution is to run a script every time one wants to launch a game with the desired controller calibration ^[1]; this does not feel ideal to me.

I’ve had issues with controller drift in Cairn ^[2][1].

What tool do you use to accomplish that?

[…] I love your use of references.

Thank you! 😘

[…] you can use Steam’s controller settings to expand the dead zones. […]

I tried this, but I can’t get it to work: to use steam’s deadzone control, I need to enable Steam Input ^[2], but when I do that, my controller no longer works in games ^[1].

[…] Make sure the kcm-joystick package is installed for KDE.

On Arch Linux ^[1], that package doesn’t appear to exist ^[2].

What distro are you on? […]

Arch Linux ^[1].

[…] I haven’t found many editors with typst support unfortunately

I’m not sure what you mean — I personally just write it in VS Code ^[1], and then compile it locally ^[2].

[…] I’ve definitely had my fair share of experiences wrestling with Typst to do things that are trivial in LaTeX […]

Could you share some of these experiences? 🙂

[…] [Typst] still has not reached feature parity with LaTeX […]

What, in your opinion, do you think it’s still lacking?

[…] LaTeX ignores whitespace, so you can just use a formatter to space out your code and ensure the curly braces. This is not even an option in typst, which uses the space as an escape character.

I’m not sure I exactly follow what you mean. Could you elaborate?

Update (2026-03-20T00:37Z): @Meron35@lemmy.world, it has since been found that Typst is aware of this inconsistency ^[7].

[…] You can see how this would start to struggle even with high school level maths, with bracketed terms and possibly fractional terms in exponents, integrals, etc.

For example, it is very difficult for me to work out the difference between the following three in typst. That is specifically not what you want from a typesetting language.

1/2(x + y)
1/x(x + y)
1/2^x(x + y)

[…]

I think these are valid complaints. For clarity, this is the output that I found for each:

1. ^[1]
2. ^[2]
3. ^[3]

I was surprised by the second; I expected it to produce ^[6]. I didn’t know what to expect for the third.

I tried searching through the documentation ^[4], but I was unable to find any information that exactly defined expressions ^[5], and how they are grouped within the fraction when juxtaposed like in your examples.

[…] \frac{n(n+1)}{2} in latex turns into (n(n + 1)) / 2 in typst […]

Note that one can also write that as frac(n(n+1), 2) ^[1][4].

[…] For example, \frac{n(n+1)}{2} in latex turns into (n(n + 1)) / 2 in typst. The typst code is incredibly unclear - the first set of brackets with the slash together actually form the fraction operator, so neither end up visible. […]

IMO, it’s only unclear if one isn’t familiar with the syntax — I think the documentation states the behaviour clearly:

[…] Multiple atoms can be grouped into a single expression using round grouping parentheses. Such parentheses are removed from the output, but you can nest multiple to force them. ^[1]

This isn’t in defense of Typist’s syntax, but I challenge you to show the uninitiated your example LaTeX expression, \frac{n(n+1)}{2}, and see if they are able to accurately parse it.

[…] use markdown with a typst backend

How could one do that?

I don’t know what Typst’s custom font support was like in the past, but, currently ^[1], Typst does allow the usage of custom fonts:

• The Typst CLI can use installed system fonts ^[1.2].
• The Typst CLI can be passed directories that should be scanned for fonts through the --font-path argument or the TYPST_FONT_PATHS environment variable ^[1.3].
• Fonts can also be uploaded directly to the web app ^[1.1].

I’d say it still have a long way to go, especially for advanced use cases […]

What do you think it’s still lacking?

For clarity, does that mean that the floating gem thing is really as black as its shadow?