this post was submitted on 05 Dec 2024
816 points (96.9% liked)

linuxmemes

24275 readers
1819 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    816
    Who is excited? (lemmy.world)
    submitted 4 months ago* (last edited 4 months ago) by trespasser69@lemmy.world to c/linuxmemes@lemmy.world
    141 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] ArcaneSlime@lemmy.dbzer0.com 1 points 3 months ago* (last edited 3 months ago)

    Same, but I learned (rather quickly mind you) enough of the CLI to get by, and continue learning to this day. I looked up a few "Bash basics" and "linux terminal basics" videos on youtube and followed along like it was a class which really helped. And whenever I have to figure out how to solve an issue I have (for instance my airpods didn't want to connect through the GUI at first) and it gives me a CLI fix (bluetoothctl in this case) I try to remember it, or I can always go "ah fuck what was that command again.." and search it again, or I put some of those in a textfile called linuxcommands.txt that I can reference back to, or I can try bluetoothctl -h for help, or man bluetoothctl for the manual for bluetoothctl (and that works with most CLI programs.) Honestly sometimes I prefer the CLI now.

    Now I need to learn all of the symbols and hotkeys and for loops and cool shit like that, but I'll get there.