vim is a terminal text editor which is notorious for being hard to exit from and hard to copy from
vim is a terminal text editor which is notorious for being hard to exit from and hard to copy from
RI barely know anything about linux. My first real foray was the stream deck, now bazzite, and I'm just trying to get away from windows for good lol
ZYeah Ctrl c does not stop it like 99% of terminal programs
ZIt's all good, we all were like that
Ai used to not know how to quit less 
ZAt the end of the day, is just remembering what did you change before the computer started crashing, so you can undo it
ZAin't Ctrl c as well?
RIf I can't find a google link to some random forum post telling me how to do it, I'm lost.
Actrl + c doesnt work, need to press q
ZAh right, sorry, muscle memory got me
Athats my instinct but my brain got confused when it doesnt work
RI really should learn how to use vim sometime but doing anything in the terminal scares the window user
Akinda optional today, nano exist
KYeah you don't have to use terminal text editors
KInstall Arch in a VM for an experience
Aif you really need to edit in terminal i recommend micro, sadly i dont think its maintained
Abut nano works in a pinch
RI hope I'll never have to edit anything in terminal
ZNo wonder, batch scripts look like arcaic gibberish xD
ZTbh you eventually will
Abatch and bash are same level of gibberish to me
RQuestion though, can basically all files be found and accessed through SDDM? My biggest hurdle so far is understanding the file structure.
Ayou mean dolphin? or gnome files?
ZSddm is the login screen
ROops I mean using KDE plasma or really any desktop enviroment, are all files visible and accessible?
ZYeah
Aif you turn on hidden files pretty much, but not all file are editable
ZI think you can request to open files with root perms from file managers but not sure
RWhich means to edit those files, I'd have to do so through the...terminal...?
Aalso fun fact, in linux everything is a file, your gpu is a file, so your mouse, etc
Acant be edited as in, you really shouldnt touch it anyway
ZAnd if you need to, is because you are following a guide or some kind of documentation at hand
Aalso cmiiw, you only required to edit file through terminal if your system cant boot into DE
RTypically yeah, that's what I'd be doing. But I like trying to navigate to it visually instead of just copy and pasting a file path in the terminal if I can. It helps me understand where things are stored in relation to other stuff. That's why I like trying to find things using the DE if I can first.
Abut most of guide in linux kinda use terminal or assume you know how to, because it is easier to give you list of command compared to screenshot a gui
RYep, which is why despite getting results for things I want, I really don't know how or why they worked or what they did. Example, I just got a command from someone on here on how to make the mouse bigger on the login screen, but why or how it worked is a total mystery to me.
KThis is a slight problem of using commands
Let's see the parts of the command to understand it better
Let's see the parts of the command to understand it better
Ksudo bash -c - Run a command as admin
printf - Print something. In this case, it prints
>
- Turn into a file. So it takes what we printed and turns it into a file
RIt goes beyond just the commands. Why did you place the file you created in the etc directory? what even is the etc directory and why does files in it effect the login screen?
K/etcsddm.conf.d means "SDDM Configuration Directory". SDDM is the name of your login screenRSee I really had no idea that's the purpose of the etc directory. Does it only hold configs for the OS itself or other apps too? One of my other issues is that apps seem to be able to be installed anywhere, and finding their directories are difficult. Simply searching through KDE sometimes finds nothing.
RAs in, typing the name from the desktop or searching via app launcher
Athis can only be fixed by experience unfortunately, the more you use it you will see the pattern
KOnly OS and system apps indeed, you gotta have admin permissions to edit it.
flatpak apps are in
flatpak apps are in
var and a bit messy, I thinkAsome flatpak use config in .config or .local i think
RI can tell you that apps installed via other apps or scripts like emudeck are hard to find. lol
Astuff like that should be documented in their respective website
KI think emudeck is kinda unique in installing wherever
Abut creating good documentation is hard 
Avim is true pain