You can use command line arguments for minetest to bypass the built in menu. You could then re-implement all menu features yourself.
they/them
You can use command line arguments for minetest to bypass the built in menu. You could then re-implement all menu features yourself.
It’s gradually getting there. The settings redesign was introduced a few versions ago, and the online content menu redesign will hopefully land in the next version (and potentially replace the current content tab after that). I agree that the main menu redesign might be a while away though.
I believe it is the implementation of the tick system in Mesecons (which VoxeLibre redstone is based on) that is the issue, and I agree it makes it nearly useless. It is absolutely an issue with the mod, not the engine, but would probably require a big rewrite of the mod to fix (not that I’m familiar with the actual implementation of mesecons).
Oh, that explains why ctrl is blue.
I’m assuming blue means a key is more used, so it’s showing Caps never gets used. enter doesn’t make sense though, so maybe it’s only showing key combinations?
That is interesting. WASM seems like it’s just a replacement for the TrueType hinting language (which is already a VM). So I guess it’s benefiting from a more standardised and audited virtual machine.
It’s also fairly limited to what it can do (source):
you can influence the process of mapping a string of characters into an array of glyphs, you can determine how those glyphs are positioned and their advance widths, but you cannot manipulate outlines, variations, line breaks, or affect text layout between texts of different font, variation, language, script or OpenType feature selection
I don’t see how the mentioned future drawing API will fit into that though.
Do you have a link for that, or a term I can search for? I’m not finding anything about it.
I’m not entirely sure how I feel about fonts containing WASM code… It feels like we’re overcomplicating things a bit.
Has IRC been getting many new features recently? It kind of feels like the sort of thing where software can become “finished”.
and all future commits
Not entirely true. As long as you hold the copyright to all of the code (there are no contributions from other people), you can change the license however you like. The important thing is that this only affects commits after the licence is changed. All earlier versions are permanently available under the license they were released with.
Also Haiku. I was impressed by the amount of software available for it.
I think it just needs a little polishing. They look a bid odd in those places for now.
It looks like it’s the addon’s fault, and has already been fixed in the github version. It’s also been abandoned, so it’s probably not worth keeping around anyway.
It seems to be caused by the FediAct addon, which doesn’t make any sense. Disabling the addon fixes the page without needing a reload, so it must be a CSS issue rather than an exception. Edit: it seems the addon is overriding the fadeIn
keyframe, but it looks fixed in the github version.
Anyone else getting a blank page? I had to go into inspect element and remove {opacity: 0} on the body to see anything.
If stability was their aim, they wouldn’t be breaking stuff all the time…
https://crates.io/search?q=neofetch brings up 21 versions to choose from (21 are actual neofetch clones). There is also a library to help you write even more of them.
A good starting point, but since they are GET requests, there is no reason to leave the browser.
You can visit the links directly, such as (I filled in OP’s instance):
I’ve heard from somewhere that chrome doesn’t render JSON nicely, so make sure to use firefox!
Other interesting parameters are saved_only
and disliked_only
.
I believe if you attach more than 4 images to a post, other mastodon servers will only show the first 4 images, and will not give any indication that the remaining images are missing.