How did you guys learn all this command line stuff? Also scripts?

The windows registry kind of scares me. I have attempted using it to fix random problems before, I forget what, but I didn’t really know what I was doing and was just desperately following tutorials back then :rofl: Was trying to fix stuff like SCREENSHOTS not saving to the screenshot folder, for instance. In the end, for some reason, the way I fixed it was… Downloading the snipping tool from the windows store?? Yeah IDK why I had to do that, since it was already seemingly opening that program whenever I hit the keyboard shortcuts, but I guess it didn’t function if you uninstall the windows store. facepalm filed under many reasons why I probably won’t go back to windows any time soon.

I have seen mention of this “fish” thing before. I may investigate that as well.

Appreciate your input!

:eyes:

“POSIX” :red_question_mark:

FASCINATING STUFF :double_exclamation_mark:

Cool! Thanks for the reply!

Yeah, I sort of agree with that. I mean personally I actually do want to learn to be comfortable with the command line. But as far as “Linux becoming more mainstream” goes, I tend to think about what percentage of computer users can ACTUALLY touch-type using a keyboard, as opposed to single finger sight-typing!! XD I’m lucky that when I went through K-12 they were still teaching general computer usage and TYPING (not to mention my mom got her first job after highschool JUST BECAUSE she knew how to type, so she really drilled typing into me as a kid after school stopped teaching it).

Although I will say, as I have been acclimating to CachyOS, I’ve found I barely needed to touch the terminal/scripting. In fact I probably could have avoided that altogether if I’d realized you can right-click a program in the application menu, to “edit application” and bring up a screen with a space to copy paste an environment variable into.

And the funny thing is, I feel that so far, CachyOS has been MORE compatible with my hardware/setup than windows was! For instance CachyOS was able to correctly label connected devices as being logitech stuff that was still associated to (i think) my logitech “unifying reciever”(u used to be able to connect multiple logitech devices via a single usb dongle). ALSO: I was able to set my TV(connected via HDMI occasionally, to show movies) TO THE CORRECT ASPECT RATIO (LMAO on windows you had to choose lowest common denominator, and I had to just accept that the edges of the screen would always be chopped off on the TV)

:face_holding_back_tears: wow i kind of forgot about batch files. that brings back memories. XD I got yelled at as a kid for playing with batch because my mom thought it was “hacking” LMFAO
I used to make crappy text adventures, and at some point I even resorted to using powershell for… batch editing a bunch of text files, I think? That was probably connected to my use of the program UTAU, an old vocal synthesizer.

:confounded_face: so true. can’t tell you how many times a problem i thought I’d “solved” came back for REVENGE over on my windows install. smhhhhhhh lmao

People left windows or other Operation systems for many reasons.

Main reason I started Linux was it would work faster and overall became much more efficient .

Learning commands is something you learn by practice or download a guide and use this as reference to help you.
os

I use Linux wise at the moment Raspberry Pi
Linux Pop
Debian

I am planning once I finish of some jobs remove a windows then put on Cathyos for main reason using this site.

Its a standard that defines a lot of things.
Compliance with the standard means things can be expected to work the same between different system/environments.
So many tools, like your SHELL, might be POSIX, and similarly other services/utilities/components might expect POSIX.

Its one thing to think of it as something like .. your script working between different systems.
But it should also be understood as a sort of specification that integrated systems might expect and/or work better with.
This is one of the reasons why I suggest that login shells should always be kept POSIX, or relatively close to it, while a users preferred shell in their terminal emulator can more or less be whatever they want.

Heres a wiki page:

And something a little more digestible from a quick search:

And for anyone who does not need to read the articles but might get a kick out of it here is a quote from the bottom of the last link;

There is another thing that helps to learn all these commands and that is the fact that you can repeat the last commands in the shell by using the up and down arrow keys. Also history prints a list of all your recent commands which is pretty helpful.

No offense, but honestly, I’m still blown away by this site. I would say that once you’ve survived this site, Linux can’t faze you anymore. :face_with_open_eyes_and_hand_over_mouth:

Another one I stumbled on is https://www.terminaltutor.com but I havent actually reviewed it.

In my opinion, this site is better designed visually, very clear, and more appealing to beginners.

Here’s another good night read:

Well, I’ve been around linux systems, somewhat consistently, since at least 2005.
Back then there was no other option then “rawdoging” it !

The first linux I used was Linux m68k on my Amiga. That was long before I had internet and I had to buy a book to get into it. Damn, now I feel old … :thinking:

You are old :wink:, so am I :grinning_face_with_smiling_eyes:, but that also makes us more experienced, which usually is good.
Less risk of screwing things up, and knowledgeable enough to fix most things our selves.

tar bomb - LOL~

I learned the command line installing a headless LAMP server about 20 years ago. I wanted to learn Linux, and that’s a damn good way to learn it. Just like learning anything, you just need the willingness to learn and repetition.

It means every time your system needs, QT_IM_MODULE, it returns fcitx anki.
And you didn’t have to put that into a script. You can just export QT_IM_MODULE=”fcitx anki”

To make it permanent , add it to your ~/.bashrc or ~/.profile at the very bottom. If so, you also have to source that file so source ~/.bashrc or . ~/.bashrcor restart the session.

Making it a bash script is just an unnecessary step.

I learned everything one problem at a time lol. I set up a linux file server a long time ago (over a decade at this point), and just for each thing I wanted to do, I would google it. When I didn’t understand an instruction, I googled the components of it. It’s certainly not the most structured way to learn but it worked for me.