I've been using the commandline for so long but was always too lazy to look up the rest of these commands after ctrl+a/e and ctrl+r THANK YOU!!!

post this commend again and again! There's always lazy idiots like me who will be helped that way!

• alt-. also pastes the last argument of the previous command (useful if you need to modify it a bit)
• instead of any shortcuts starting with "alt" you can also press "esc" followed by the second key, e.g. pressing "esc", releasing it and then "a" is the same as pressing "alt-a" (useful if you have only one hand available, or if alt is not availalble)
• if you put a space before a command, it will not be saved in history (useful sometimes, e.g. if you pass a password directly as an argument)

Makes me realize just how illogical and bad these shortcuts are

If you’re looking for a full list of these kind of navigation shortcuts, they all come from readline so read the man page for that. Or just look up the basic navigation of emacs which is what readline is mimicking.

But how do Linux users handle the crippling loneliness of their operating system not pestering them with ads on every update? How else can you know if your computer loves you? Where is the warmth of the corporate embrace?

plus it makes you feel like a hacker for a few seconds

I setup open SSH on windows so you can swing it both ways!

My main gripe is it runs cmd.exe and I gotta powershell to jump into that. If you auto powershell it doesn't work right.

The moment I loved the FOSS community was when I went on an Linux IRC channel, complained about my wifi not working, and some stranger messaged me detailed instructions with a patch in 20 minutes that completely fixed my issue.

I once plugged my linux laptop into the scanner and it just worked

I spent days tinkering with proprietary, outdated (seriously, win XP as target) programs that provide sort-of drivers, and nothing worked, on windows.

Mine worked out of the box on mint. Like, it detected the network HP shitbox and I could print, no user intervention. I was floored.

As an administrator, powershell is an essential tool these days. There are tunables that Microsoft simply only exposes via powershell even in their cloud Microsoft 365 environments. Just last month I had to rely on Powershell to trim previous versions on SharePoint, and 2 weeks ago I had to use Powershell to adjust a parameter on Exchange.

But also being able to pop a Powershell session and quickly apply a registry fix or run a diagnostic command or even just install a piece of software without disrupting a user's work is absolutely brilliant (plus saves a call when I can just email back and say "I've pushed it remotely, reboot and it should be sorted now")

When my computer starts to run out of ram and I immediately try and switch into the CLI so I can launch htop and kill the offender

I'm thinking of making Linux my daily driver apart for some software I need for work. People are super positive about it on here, but isn't it still the case that some peripherals won't work? Or that I'll spend a ton of time making the system work instead of actually using the system?

It would be for gaming that I'd use the Linux installation mostly.

With .tar.gz software usually the steps are:

1. Extract the archive
2. Find a file with the .sh extention - that's the shell script. It will most likely be named something like install.sh
3. Make it executable - by right clicking and enabling it in the properties or by opening a terminal in this folder and using a command:

chmod +x install.sh

4. Run the installer in the terminal:

./install.sh

It might ask you to run it as root and quit. In that case put a sudo before the command above and it will ask you for your password

sudo ./install.sh

And tbat's it, installation should begin. Follow the instructions in your terminal.

Can't say for TeamSpeak, but will say for Linux: setting everything up and figuring out your steps in edge cases is the hardest part. Once you figure it out, it gets so much easier.