I don't know of one, but why not install gnome on Mint (or Debian)?
@lemm.ee
since commercial usage is not free
Commercial usage oft the osm data is free, see the OSM license. The article even speculates that they switched from Google maps due to licenses costs.
Of course this doesn't apply to commercial services that provide e.g. map tiles.
I would consider that ifconfig is deprecated on many distros and would therefore teach about iproute2 (mostly the ip and ss commands) instead. Additionally I would consider editing files essential, even if it is with nano.
Maybe mention more modern and simpler help tools like tldr, as they could be even more useful to beginners.
To introduce the shell and utilities, I would try to find a somewhat realistic use case that combines multiple aspects, like analyzing some files or spellchecking instead of simply mentioning every feature one by one.
Having the commands listed at the bottom by default is one thing i personally dislike about nano, because they take up space while being useless to someone knowing the commands (or at least knowing how to open the help in, which is what you can do in vim to achieve the cheat sheet). The alternative that vim uses, is to show the commands when starting the editor without opening a file.
You don't even need to look at the extension to identify most file formats, as there are unique magic numbers stored at the beginning of most (binary) formats. Only when a single binary format is reused to appear as two different formats to the user, e.g. zip and cbz are extensions relevant. This is how the file command and most (?) Linux file explorers identify files, and why file extensions are traditionally largely irrelevant on Linux/Unix.
This means your idea of suggesting software based on the file type is even more practicable than you described.
Keeping the details about vim in the extras is what I would do as well, but I would definitely tell the students that vim and vi exist, because they are the only editors available on many systems.
I use both versions actively, the main differences of SCEE compared to StreetComplete are the addtion of more obscure questions (for example building and roof colors, species/genus of trees), allowing direct editing of tags and disabling the gamification/statistics.
So compared to plain bash without autocomplete and Ctrl+R it may be useful. It is probably a step back for everyone else.
I think it could be much worse than even a plain shell with ^R, as the llm will be slower than the normal history search and probably has less context than the $HISTFILE.
I don't really have a single favorite a language, if I am able to choose freely it depends on the task.
I'm currently using a Fairphone 4 with Lineage without problems. The battery life is good enough to last me a full day, the only weakness i noticed is the camera. I find it acceptable, but other phones in a similar price range are just better.
The other problem I initially encountered was that because Lineage didn't officially support the Fairphone 4 until recently, I had to use an unofficial build that didn't receive normal updates.
Why not write your own version? Getting the temperatures is easy and portable with the sensors command from lm-sensors. The rest of the info is easy to get using various commands (e.g. uptime, free) combined with a bit of sed/grep/awk for formatting.
thanks for using Leebra!
go to feed...