From the article ...
Fixed input issues with Worms Armageddon.
Interesting that normal keyboard and mouse input would have a unique issue with just that one game.
I wonder what they do that's not normal for handling input?
this post was submitted on 27 Apr 2024
1 points (100.0% liked)
Linux Gaming
15300 readers
15 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
I believe that the custom for a lot of wine patch notes is just to mention the first application reported with the bug even if it affects many applications. So that could be what's happening here.
What do you use to automatically add that licence to your comments? That’s really cool! Big fan of creative commons.
What do you use to automatically add that licence to your comments? That’s really cool! Big fan of creative commons.
Its a manual copy/paste of the following text...
[~CC~ ~BY-NC-SA~ ~4.0~](https://creativecommons.org/licenses/by-nc-sa/4.0/)
I use the Lemmy web client, and they don't have a signature section on the account to set once and forget.
Why do you put strikethrough the text though?
Why do you put strikethrough the text though?
The single ~ reduces the font size.
For ~example~
Not on my client.
Strange.
On the Lemmy web client its two tildes ~ for strikeout.
One tilde is the subset font size.
Before ^superset^ After
^superset^
Before ~subset~ After
~subset~
Before ~~strikeout~~ After
~~strikeout~~
What client are you using?
Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:
Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:
Yeah it looks like the subscript and superscript fonts are not being supported on third party android/apple clients properly, but only the Lemmy web client.
My goal was actually just to make the font smaller, and not so much subscript/superscript.
I may have to revert the change, and just make the font for the link regular sized.
Either that, or just wait for the android/apple clients to catch up to the Lemmy web client.
Voyager. And this is how it looks, by the way.
Are you running outdated version of voyager? Because it looks fine to me
Yes, I was. I checked in F-Droid and the reason it didn't automatically update was something to do with an incompatible signature. But I updated it manually and it's looking fine now.
What formatting text do they use for subscript/superscript?
The Lemmy help page for formatting has the formatting text I'm using.
Seems like others are having the same problem. Looks like the non-web clients need to add support for subscript and superscript to themselves.