I swear it feels like for a lot of the things I do on Linux there's a GUI app for it, but then if I wanna do something as basic as adjust my fan speed I gotta use the freaking terminal.
Like it's always at the worst possible time.
Edit: I’ve installed a distro on my gaming PC that I really liked, used it on my laptop. Sensors and fans were fully supported. Did not work at all on my PC so I told it to fuck off. It’s just too much of a pain to set up.
Thanks for this, I was wondering why Linux was using more power (on my UPS) compared to Windows.
I just added amd_pstate=passive to grub and it brought it down ~15 watts, there's other options but I believe they require kernel 6.3 or higher. More info here.
There's coreCTRL for AMD and apparently nvidia-setting for Nvidia?
AMD GPUs got more tools due to them being open source, while Nvidia's isn't and you are beholden to Nvidia bothering to implement support, which they often don't.
Also, idk if I would call fan curves that basic, haha. For the vast majority the default curve is sufficient.
Not sure if you're being sarcastic or serious. I've been using computers for decades and not once adjusted fan speeds, so that function doesn't seem very basic to me.
I think it's a matter of habit, really. After using a somewhat minimal Arch install with a WM instead of DE, I get frustrated when an app doesn't have a CLI version, using GUI now feels less comfy almost
Another thing that's satisfying is having a machine that knows when it needs to turn on the fan and never needing my input, which would be pretty ignorant on the subject anyway.
While this is not a serious post I'm going to take it seriously, so here are some of the reasons:
Nobody can easily remember the precise file name and if you don't get the first letters right you're screwed(did I mention capital letters matter?)
Wtf is --vo=tct? No sane person is remembering all of that (same goes for the rest 10000 parameters and options)
Again, waaayyy too many parameters, who remembers their playlist name? There is no autocomplete here, you're on your sad own in your sad little room with your sad little feelings, because there's no one there to tell you the song's precise name, because computers are assholes and don't hate you.
So why GUIs? Because they make computers seem like friendly fellas which actually care about you and give you options, tell you the available functions(without deciphering a 50 pages manual if done well)
If you take it seriously, then at least your complaints should be reasonable, not meme-worthy.
Autocomplete is a standard feature in CLI nowadays, so no need to remember everything.
And parameters usually have names chosen to make the most sense and to be memorable (e.g. vo = video output).
Can autocomplete fill in a YouTube URL or Spotify playlist name? Can I browse the list of what's available and filter, drill down, poke around according to my whimsy?
Or if I'm accessing a local file, how do I find that one video of my cat named VID-004326.MP4?
Can I autocomplete the parameters themselves, which are betimes lengthy and unwieldy to type out?
Even if it's possible, and I've mastered every arcane parameter necessary to do it, is it really faster / more convenient than doing it through a GUI?
Maybe there are good answers to the above questions—I don't know and would love to find out—but they and many more like them are surely reasonable and far from meme-worthy, or else I'm missing something huge.
In which situation would you need an autocomplete for YT URL? Online-only services designed for a web browser are crappy examples.
But anyway, yes, Spotify clients written for CLI do provide autocomplete and filters. I never tried YT, so I don't know.
Or if I’m accessing a local file, how do I find that one video of my cat named VID-004326.MP4?
And how do you do that using GUI? The exact same way, looking blindly and playing random videos (or name the file properly in the first place).
Can I autocomplete the parameters themselves, which are betimes lengthy and unwieldy to type out?
Obviously, yes, that's pretty much the entire point.
Even if it’s possible, and I’ve mastered every arcane parameter necessary to do it, is it really faster / more convenient than doing it through a GUI?
That mostly depends on the user, but often: yes, it is. Otherwise we'd all have moved on from CLI ages ago.
Please don't take this as a personal attack, but assuming CLI is some unwieldy, outdated idea requiring mysterious arcane knowledge to use effectively only shows ignorance.
It also hurts new users, because it discourages them from trying it for bad reasons.
The main annoyance with CLI is that it is not nearly as easy to discover things with it. With a gui you can just click through each setting and see what is what. With CLI you can't really, you gotta read the manual which definitely can be cumbersome. And even if the commands do try to make sense it is still very common to forget the abbreviation unless you use it often (or write it down). At least I do. I use git semi occasionally and keep forgetting amend.
And how do you do that using GUI? The exact same way, looking blindly and playing random videos (or name the file properly in the first place).
Thumbnails? Or maybe searching through find, which is not as straight forward as something like search in dolphin.
Also "name the file properly in the first place" is such an off putting mentality. I want my computer to simplify work by doing things for me, not need to properly catalog every random video because of the failures of my UI.
Same. When I’m importing 10-15k photos from a 3 day trip (motorsports photography) there’s no way to name all of them effectively. A GUI is a requirement for photo management imo.
You' can try installing yt-dlp. That one is still actively maintained. YouTube also actively trying to broke it, so the one available in debian repo might be out of date.
looks like it is using DLP backend, didn't read the whole error
[ytdl_hook] ERROR: [youtube] BBJa32lCaaY: Unable to extract uploader id; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
[ytdl_hook] youtube-dl failed: unexpected error occurred
Failed to recognize file format.
Let's hope youtube hasn't finally ground the project permanently
At the risk of being a 'works for me' guy, I tried downloading and playing a couple random videos and it worked on version 2023.07.06. So hopefully yt-dlp is alive and kicking!
Exactly! Takes so much of the pain away. And you know what would be really useful? If those scripts were accessible easily through simple buttons or sliders on which you could click, or something like along those lines.
For basic functionality I agree, but I don't think any dev would put the time and effort to implement buttons (much less pipe into another totally different software) for my extremely specific use cases. In the command line I'm presented with a toolset where I can do so myself.
IMO it's not even a Windows vs GNU/Linux debate (although yeah, maybe more of the users of the latter would be familiar with the CLI), it's about using the right tool for the job. Image or video editing? Good luck even starting to do anything without a mouse. Installing something? Yup, even on Windows I'd prefer doing scoop install foobar2000 instead of opening a store app or a website.
I use CLI daily for git and nano, but it's far from necessary for the average user. I'm not sure why some people want to propagate the idea that Linux is hard when it's just a little different than what most people are used to.
My brother used to constantly try to tell me this. I don't know how many times I had to compare number of keystrokes to number of clicks before he finally admitted GUI programs are easier even if you already know exactly what you're doing.
For something that needs very complex configuration like specific ffmpeg transcoding rules and cmake build files - you'd have menus that are 5-10 pages long and full of super detailed selections and forms, while in reality you'd only want to switch on or off one thing, so it would be easier just to write the command
When I made my small game engine I had a second window full of settings that I could change dymamicaly. After like 2 months of work it was so full of settings it was very hard to navigate even with all subdivisions and layouts properly made
Also, GUI apps often lack specific or new settings for the terminal app they're built on
Here's a novel idea, read what you're about to paste and try to understand what it does at least on high level. You can man each command to check what it does and whether the parameters provided make sense.
There is also that obscure forum post from 2012 that refers to a post from 2004, from someone who gives some cryptic advise with commands not even in the manual that are outdated from 5 major releases ago but somehow still work. Except for one command tgat you then google and find a forum post from 2016 that it has been renamed, but the functionality stayed the same.
Anyways you put it all together and your problem somehow got solved, but you seemed to have created a black magic incantation because now a three headed demon has appeared and eaten your neighbour alive.
I have no problems with small man pages. My problems with manpages arise when a command has hundreds of arguments and I need to find a very specific combination.
That'll be useful for a swap partition, but if you're using a swap file instead of a partition it won't work.
To clarify, a swap file is just a file on your hard drive the size you'd like your swap to be. Filled, at the start, with zeros. You still put it in your fstab to mount it but instead of a full partition, it's just a file.
This makes it more flexible, and easy to change the size of or turn it off or on during operation, safer to change the size (less steps, less ramifications, lower chance of data loss), or have it expand as needed, but is more restrictive in other features while being a bit slower and less secure.
Windows has a similar system for swap called a pagefile.
On linux, while there is a gui to change a swap partitions size, changing the swap files size has no gui. Even though it is, theoretically, a simpler operation. Simply run swapoff, delete the old file, create the new file, run swapon. No partition managment needed, essentially no chance of data loss
powershell is pretty great for windows tbh. I use arch and i love python and shell scripts but on windows powershell gets shit done. PS is great for vmware too. There's a lot of 'microsoft bad' that i agree with but powershell is not one of them.
I think the only reason Windows users are afraid of terminals is that they're not used to them. They're not that bad. Most terminal programs have a -(-)help command that shows you what you can do as well, in case you get stuck.
Powershell is pretty interesting but I haven't learnt much of it and it's hard to discover commands, arguments and fields within results. All the commands have really similar generic names and cryptic mnemonics. And an annoying amount of them are text based and don't actually interoperate with the ecosystem.
I'm more used to slinging around text with bash and the basic Linux utilities so I'm not inclined to learn more than I have to on the Windows side.
I wrote a couple hundred lines of it as part of my apprenticeship a few years ago and have occasionally needed to deal with small scripts since then.
In principle, I like the idea of static typing, as I'm a backend dev, but yeah, I don't particularly want a script to ever become large enough where static typing truly becomes useful.
I would strongly recommend using a full-fledged programming language instead. In particular, because Microsoft somehow managed to make Powershell feel even more verbose than even C#, which is one of the most unnecessarily verbose languages out there.
Back then, it also felt quite like a web technology, where many features were only available, if you had the right version combination of Windows, Powershell and .NET installed.
And of course, the biggest strength of Bash is unattainable, which is that there's multiple decades of people posting snippets and example commands online.
Having said all that, maybe for Ops folks, who *have* to script a Windows configuration and aren't proficient in any proper programming languages, it is genuinely quite useful.
Let me tell you a story of checking a signature and unzipping an exercise file for uni every week on my linux distro that was named 01_ML-exercise_Bayesian-sep.zip.gpg followed by 02-Ml-exercise-FisherLinearDiscriminant.zip.gpg
Hello noobs! I'll let you in on a secret. Pros use command line interface (CLI) both on Linux and on Windows for a lot of tasks. You know why? Because it's easier. Be like the pros, choose the easy path, use CLI!
Depending on the time availability of that pro. Sometimes I have the time to tailor to the needy's sensibilities. Other times all I can do spit out what I have whether it's GUI or CLI, take it or leave it.
Same here. I didn't imply that we only use CLI. Simply that for a lot of tasks CLIs are easier than GUIs. And therefore the CLI aversion is something to shed. The reverse is also true for other tasks too. Windows has historically put many tasks easier achieved via CLI behind a GUI. You wouldn't see me dead playing videos via CLI. I'd launch Plex, search and play instead. 🥲
Forget gui, I just want to git clone something and then type the name of the application I cloned into a command and have it run. None of this infinite searching for dependencies that didn't get installed with the initial run dependency installer.
I use Arch btw, and we don't have this kind of problems usually. Everything is in the repo, all the dependancies are accounted for. Or if not, they are in the repo.
I use Arch btw.
I mean, it obviously depends on what you're doing, but usually it's easier to find the right command than the right GUI, because implementing a CLI is a magnitude less work than implementing a GUI...
Shells offer a significantly faster and more powerful way of running programs when you know how to use them. The "helpful" Windows user is kneecapping the noob by offering a shiny but limiting GUI. Once you get a grasp of basic command line tools, you'll wonder why you bothered with pointing and clicking stuff.
I feel like the shell becomes much more complicated when you want to use configs. Or anything other than basic commands. At that point it becomes a pain in the ass, or tedious.
Other than that I agree. Also, GUI file managers are still superior. Sue me.
I still don't get why people like vim. Like sure, I use it to edit config files and stuff that needs sudo permissions, but in all honesty, if I could use any gui for that, like Kate, I wouldn't see any reason for using vim. Why do I need to relearn years how to Ctrl+ f or exiting the editor? buT iT'S FaStEr. Really? You spend how long looking up guides and cheat sheets on how to use it and it's faster? I mean sure, use what you are comfortable with but can you really say it's that much faster than just any text editor out there?
It's like Dvorak. You can be ~5% faster once you get over the turly enormous learning curve. The problem is, for most people, that 5% does not justify the huge initial investment.
Why would it though? If performing an action through the terminal shaves off only 2-3 seconds who cares?
If I want to open firefox though the terminal I can do that, sure…or I can just point and click on my taskbar/desktop. The time difference is virtually unnoticeable.
There’s a reason GUIs blew up. It’s not just because of user accessibility. There are legitimate things that are faster or less of a hassle with GUIs and I feel like the Linux community forgets that sometimes. Like using the terminal somehow makes them superior.
I'm new to Linux, and pretty new to Vim, but for me personally it works because of a couple of reasons:
(i) speed. yes, it's faster once you spent a little bit of time getting used to it. Vim movements or motions just make so much more sense in my mind, and being able to do all of them with few keystrokes feels pretty good and saves time.
(ii) comfort / muscle memory. This kind of ties to (i), where I just feel comfortable with my hands staying roughly at the same place on the keyboard the entire time I'm editing or writing something. Jumping here and there, deleting and copy-pasting, search/search-and-replace, creating-using-erasing macros, etc; things just feel so crisp and effortless.
(iii) simplicity. It is a terminal-based text editor, and so for me it's distraction-free. I just want to open up a text file and edit some stuff or even do some bit of writing, and I don't really feel like opening up a GUI text editors just to edit some stuff, or even write some stuff! I use Vim to write almost everything and it feels really good.
But when it comes down to it, anything like Kate or Notepadqq or any generic text editor works just fine.
The only reason I like vim is because I've literally never seen a Linux installation that didn't have vim. As a result, I know like 5 whole vim commands so I can still technically function on bare-bones installations. And even then, I only learned those 5 vim commands the first time I ran into a computer that didn't have nano or pico
Additionally, vim key bindings work in some other places too - like man and less (and most pagers I think). It also works in bash if you set -o vi which by default uses emacs keybindings. Ctrl+x, Ctrl+e (Shift+V in vi mode) to open your current entered command in $EDITOR which is handy for really long commands. Then save it in said editor, and boom - it runs in your shell.
The keybindings (vim and emacs alike) is actually a feature of GNU's readline library that bash gets for free since it uses it, the same trick works in other places that use the same library like a lot of REPLs and gdb (though those programs would need to expose their own way to change between vi and the default emacs mode).
That itself is a very good reason to know some basics of how to navigate around emacs and vi[m]!
I spent time learning vim and using a file manager (forgot which one) but after awhile I realized it’s less frustrating just using a damn GUI. I feel like the time difference isn’t too much discernible. More than anything vim is just frustrating.
When you master the tab key and the mouse cursor in a text editor, it’s a breeze.
And everything can be easily automated on shells, i love how i can setup a task on my pc and once finished send a request over wifi to my phone and use termux to generate a notification
There is a way to get genuine help from a Linux forum.
Say "Fuck this, I'm going back to Windows".
Don't do anything rash, give me a minute I'm wrapping the command with Tkinter
Two ways, the other is by saying "solved" with a half baked solution that's incorrect.
I guess you could say Linux fanboys' silliness is...
...terminal.
dad jokes this early in the morning (in the east part of the world)
I swear it feels like for a lot of the things I do on Linux there's a GUI app for it, but then if I wanna do something as basic as adjust my fan speed I gotta use the freaking terminal.
Like it's always at the worst possible time.
Edit: I’ve installed a distro on my gaming PC that I really liked, used it on my laptop. Sensors and fans were fully supported. Did not work at all on my PC so I told it to fuck off. It’s just too much of a pain to set up.
With kernel 6.5+, the default is now
amd_pstate=activefor Zen systems.I recommend
amd_pstate=guidedfor 6.4+ though as at least on my machine, this seems to yield the best performance/energy trade-off.Thanks for this, I was wondering why Linux was using more power (on my UPS) compared to Windows.
I just added
amd_pstate=passiveto grub and it brought it down ~15 watts, there's other options but I believe they require kernel 6.3 or higher. More info here.Also I was using this before but for other people, if your it87 based sensors aren't showing up, frankcrawford maintains an updated it87 module.
There's coreCTRL for AMD and apparently nvidia-setting for Nvidia?
AMD GPUs got more tools due to them being open source, while Nvidia's isn't and you are beholden to Nvidia bothering to implement support, which they often don't.
Also, idk if I would call fan curves that basic, haha. For the vast majority the default curve is sufficient.
Not sure if you're being sarcastic or serious. I've been using computers for decades and not once adjusted fan speeds, so that function doesn't seem very basic to me.
When building a system yourself, setting up a custom curve is how you get the best balance between cooling and noise.
I try to choose motherboards that support doing that in the bios, so I never have to worry about it on the OS level.
Fan curves are easy. Set them to always run at 100% and put on a noise canceling headset.
That's stupid. Why would I make my cat listen to something I wont? Can't have him wear my XM5s.
Of course not. You get him his own XM5s.
I think it's a matter of habit, really. After using a somewhat minimal Arch install with a WM instead of DE, I get frustrated when an app doesn't have a CLI version, using GUI now feels less comfy almost
This is part of the reason I haven't gone back to Linux for my gaming PC. I had zero desire to try to set a fan curve in the terminal.
And honestly with a pretty UI setting the fan curve is so satisfying.
Another thing that's satisfying is having a machine that knows when it needs to turn on the fan and never needing my input, which would be pretty ignorant on the subject anyway.
I feel that in my bones.
If I need to do something obscure, like organize your Magic: The Gathering card collection by artist, there's a GUI on Linux for that.
But if I want to adjust my monitor, I better break out the CLI!
I like cooler control. I hate appimage but I'm on arch so it's just a quick dive into the murky deep called the AUR.
Who need GUI apps when you can do these things on CLI:
imcat my-image.pngmpv --vo=tct "https://youtube.com/watch?v=BBJa32lCaaY"browshspt play --name "Your Playlist" --playlist --randomand perhaps many more I'm not currently aware of...
While this is not a serious post I'm going to take it seriously, so here are some of the reasons:
Nobody can easily remember the precise file name and if you don't get the first letters right you're screwed(did I mention capital letters matter?)
Wtf is --vo=tct? No sane person is remembering all of that (same goes for the rest 10000 parameters and options)
Again, waaayyy too many parameters, who remembers their playlist name? There is no autocomplete here, you're on your sad own in your sad little room with your sad little feelings, because there's no one there to tell you the song's precise name, because computers are assholes and don't hate you.
So why GUIs? Because they make computers seem like friendly fellas which actually care about you and give you options, tell you the available functions(without deciphering a 50 pages manual if done well)
If you take it seriously, then at least your complaints should be reasonable, not meme-worthy.
Autocomplete is a standard feature in CLI nowadays, so no need to remember everything.
And parameters usually have names chosen to make the most sense and to be memorable (e.g.
vo= video output).Serious person here.
Can autocomplete fill in a YouTube URL or Spotify playlist name? Can I browse the list of what's available and filter, drill down, poke around according to my whimsy?
Or if I'm accessing a local file, how do I find that one video of my cat named
VID-004326.MP4?Can I autocomplete the parameters themselves, which are betimes lengthy and unwieldy to type out?
Even if it's possible, and I've mastered every arcane parameter necessary to do it, is it really faster / more convenient than doing it through a GUI?
Maybe there are good answers to the above questions—I don't know and would love to find out—but they and many more like them are surely reasonable and far from meme-worthy, or else I'm missing something huge.
In which situation would you need an autocomplete for YT URL? Online-only services designed for a web browser are crappy examples.
But anyway, yes, Spotify clients written for CLI do provide autocomplete and filters. I never tried YT, so I don't know.
And how do you do that using GUI? The exact same way, looking blindly and playing random videos (or name the file properly in the first place).
Obviously, yes, that's pretty much the entire point.
That mostly depends on the user, but often: yes, it is. Otherwise we'd all have moved on from CLI ages ago.
Please don't take this as a personal attack, but assuming CLI is some unwieldy, outdated idea requiring mysterious arcane knowledge to use effectively only shows ignorance.
It also hurts new users, because it discourages them from trying it for bad reasons.
The main annoyance with CLI is that it is not nearly as easy to discover things with it. With a gui you can just click through each setting and see what is what. With CLI you can't really, you gotta read the manual which definitely can be cumbersome. And even if the commands do try to make sense it is still very common to forget the abbreviation unless you use it often (or write it down). At least I do. I use git semi occasionally and keep forgetting amend.
I like CLI. But it does have its shortcomings.
Thumbnails? Or maybe searching through find, which is not as straight forward as something like search in dolphin.
Also "name the file properly in the first place" is such an off putting mentality. I want my computer to simplify work by doing things for me, not need to properly catalog every random video because of the failures of my UI.
Name the file properly, say that to a photographer with 3 cameras and an auto export. This is what thumbs and a gui are built for.
Same. When I’m importing 10-15k photos from a 3 day trip (motorsports photography) there’s no way to name all of them effectively. A GUI is a requirement for photo management imo.
presses tab
Woa, dude!
Here is an alternative Piped link(s): https://piped.video/watch?v=BBJa32lCaaY
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source, check me out at GitHub.
Imcat is awesome, Debian and had a news reader with the same name.
MPV refuses to play any YouTube for me I suspect it has something to do with their new restrictions on YouTube DL.
Browsh looks absolutely magnificent until I actually try to use it, It seems like submitting form pages or maybe JavaScript is broken
You' can try installing
yt-dlp. That one is still actively maintained. YouTube also actively trying to broke it, so the one available in debian repo might be out of date.looks like it is using DLP backend, didn't read the whole error
Let's hope youtube hasn't finally ground the project permanently
At the risk of being a 'works for me' guy, I tried downloading and playing a couple random videos and it worked on version 2023.07.06. So hopefully yt-dlp is alive and kicking!
works for me is good, let's me know I likely have something else wrong, or they hate my ip
I do all my photo editing on the command line.
(kidding, of course)And remember kids, if it is a command, you can automate it and never do it again.
Exactly! Takes so much of the pain away. And you know what would be really useful? If those scripts were accessible easily through simple buttons or sliders on which you could click, or something like along those lines.
For basic functionality I agree, but I don't think any dev would put the time and effort to implement buttons (much less pipe into another totally different software) for my extremely specific use cases. In the command line I'm presented with a toolset where I can do so myself.
IMO it's not even a Windows vs GNU/Linux debate (although yeah, maybe more of the users of the latter would be familiar with the CLI), it's about using the right tool for the job. Image or video editing? Good luck even starting to do anything without a mouse. Installing something? Yup, even on Windows I'd prefer doing
scoop install foobar2000instead of opening a store app or a website.I used to use Chocolatey on Windows and briefly tried scoop but now I prefer winget. I dunno, it feels... More official? :)
I made the mistake of installing powershell using the Microsoft store. Now Winget refuses to update it. I have to open the store to do it.
My biggest gripe with Winget is it's not available on windows server yet.
You're right. I can't imagine using windows without scoop or chocolatey.
I use CLI daily for git and nano, but it's far from necessary for the average user. I'm not sure why some people want to propagate the idea that Linux is hard when it's just a little different than what most people are used to.
This seems like something a Linux elitist would say
tErMinAL iS mUCh MorE fRieNdLY. gUi is DuMB
My brother used to constantly try to tell me this. I don't know how many times I had to compare number of keystrokes to number of clicks before he finally admitted GUI programs are easier even if you already know exactly what you're doing.
It very highly depends on the application
For something used daily that's more or less true
For something that needs very complex configuration like specific ffmpeg transcoding rules and cmake build files - you'd have menus that are 5-10 pages long and full of super detailed selections and forms, while in reality you'd only want to switch on or off one thing, so it would be easier just to write the command
When I made my small game engine I had a second window full of settings that I could change dymamicaly. After like 2 months of work it was so full of settings it was very hard to navigate even with all subdivisions and layouts properly made
Also, GUI apps often lack specific or new settings for the terminal app they're built on
This, but written in normal case.
My rist hurts after 1 week on Windows.
Terminal is great until you paste a command from an online tutorial and it doesn't do what it is suppose to.
Do su rm -rf / to fix all issues you have
Just for those who are not aware don't do this. This is equivalent to deleting system32.
Is this some kind of pleb joke I'm too zfs to understand?
They're aren't meant to work. They're meant to make us feel pride and accomplishment.
Here's a novel idea, read what you're about to paste and try to understand what it does at least on high level. You can
maneach command to check what it does and whether the parameters provided make sense.I wrecked my kernel and rendered wifi unusable doing this just last week!
Hah! I can do all that without an online tutorial!
Hey, stop bashing linux:)
If there is a well written manual or a wiki im fine with using terminal programs.
But ofc, there's always no documentation available other than a man page.
There is also that obscure forum post from 2012 that refers to a post from 2004, from someone who gives some cryptic advise with commands not even in the manual that are outdated from 5 major releases ago but somehow still work. Except for one command tgat you then google and find a forum post from 2016 that it has been renamed, but the functionality stayed the same.
Anyways you put it all together and your problem somehow got solved, but you seemed to have created a black magic incantation because now a three headed demon has appeared and eaten your neighbour alive.
I rarely watch TV and I'd definitely watch that.
If you have a problem with man pages, you have a bigger problem.
I have no problems with small man pages. My problems with manpages arise when a command has hundreds of arguments and I need to find a very specific combination.
Searching helps. Open a man page, press forward slash, type your arg, press Enter. Press "n" to get to the next hit or Shift+n to go to the previous.
This https://github.com/dbrgn/tealdeer is handy to have and can condense the info down quite a bit in a lot of cases.
(Tealdeer is a play on the original utility's name
tldr)A manpage is usually perfectly good with how descriptive they are. Not a problem unless you're really short on time
I agree it's getting better, but some odd stuff does not exist yet. Like changing swap file size. Still need to use good old DD for that
That'll be useful for a swap partition, but if you're using a swap file instead of a partition it won't work.
To clarify, a swap file is just a file on your hard drive the size you'd like your swap to be. Filled, at the start, with zeros. You still put it in your fstab to mount it but instead of a full partition, it's just a file.
This makes it more flexible, and easy to change the size of or turn it off or on during operation, safer to change the size (less steps, less ramifications, lower chance of data loss), or have it expand as needed, but is more restrictive in other features while being a bit slower and less secure.
Windows has a similar system for swap called a pagefile.
On linux, while there is a gui to change a swap partitions size, changing the swap files size has no gui. Even though it is, theoretically, a simpler operation. Simply run swapoff, delete the old file, create the new file, run swapon. No partition managment needed, essentially no chance of data loss
If you're bored, you can visualize a rotating GUI in your mind. It's free and nobody can stop you.
As a Windows Infrastructure admin, I love this one.... and some of the responses. Perfect.
/crys in PowerShell
powershell is pretty great for windows tbh. I use arch and i love python and shell scripts but on windows powershell gets shit done. PS is great for vmware too. There's a lot of 'microsoft bad' that i agree with but powershell is not one of them.
Oh for sure, if we didn't have Powershell, I really would be crying,!
Deploy reg fixes to 100s of machines? Check. Check hotfix install status? Check. Audit local admin group members? Check.
Even our PE build environment is all run off a Posh script.
Write-Host "sob"
I think the only reason Windows users are afraid of terminals is that they're not used to them. They're not that bad. Most terminal programs have a -(-)help command that shows you what you can do as well, in case you get stuck.
I do think there is another reason, which is that the Windows CMD is awful. If that's your only reference, I understand not wanting to learn it.
Powershell is pretty interesting but I haven't learnt much of it and it's hard to discover commands, arguments and fields within results. All the commands have really similar generic names and cryptic mnemonics. And an annoying amount of them are text based and don't actually interoperate with the ecosystem.
I'm more used to slinging around text with bash and the basic Linux utilities so I'm not inclined to learn more than I have to on the Windows side.
I wrote a couple hundred lines of it as part of my apprenticeship a few years ago and have occasionally needed to deal with small scripts since then.
In principle, I like the idea of static typing, as I'm a backend dev, but yeah, I don't particularly want a script to ever become large enough where static typing truly becomes useful.
I would strongly recommend using a full-fledged programming language instead. In particular, because Microsoft somehow managed to make Powershell feel even more verbose than even C#, which is one of the most unnecessarily verbose languages out there.
Back then, it also felt quite like a web technology, where many features were only available, if you had the right version combination of Windows, Powershell and .NET installed.
And of course, the biggest strength of Bash is unattainable, which is that there's multiple decades of people posting snippets and example commands online.
Having said all that, maybe for Ops folks, who *have* to script a Windows configuration and aren't proficient in any proper programming languages, it is genuinely quite useful.
How is that different from being afraid of terminals?
It's not like you have to learn everything there is to it at once, you know.
I am a huge noob in the terminal, but --help, man, and basic knowledge about things like grep and pipes make me look like a wizard sometimes.
Let me tell you a story of checking a signature and unzipping an exercise file for uni every week on my linux distro that was named 01_ML-exercise_Bayesian-sep.zip.gpg followed by 02-Ml-exercise-FisherLinearDiscriminant.zip.gpg
Why do you need a gui for a timer? Just use sleep number && mpv someMusic.mp3
Why do people even use a Desktop Environment, so many GUIs !!!
DEs are bloat anyway
/dev/console masterrace
Fair
I actually never considered using sleep like that. Neat!
I use from time to time when i don't wanna spend to much time doing something like playing games
I used to be a user that was all about the terminal, but then i realized that gui apps have advantages
ubuntu unity user: oh yes we do
Unity was great. I hope the project to keep it going is successful.
How much do you think you're going to be using it?
Just this once.
You can see the characters in the terminal what more do you want?
I want to be attached to them, know their backstory and motivation, ya feel?
Hello noobs! I'll let you in on a secret. Pros use command line interface (CLI) both on Linux and on Windows for a lot of tasks. You know why? Because it's easier. Be like the pros, choose the easy path, use CLI!
Also if you meet a pro they will be happy to walk you through the GUI (if available) or CLI depending on what you feel comfortable with.
Depending on the time availability of that pro. Sometimes I have the time to tailor to the needy's sensibilities. Other times all I can do spit out what I have whether it's GUI or CLI, take it or leave it.
I use Bash and PowerShell often, and I'm fairly proficient in both. I also use a GUI in both Linux and windows as well.
Although, I might just be insane.
Same here. I didn't imply that we only use CLI. Simply that for a lot of tasks CLIs are easier than GUIs. And therefore the CLI aversion is something to shed. The reverse is also true for other tasks too. Windows has historically put many tasks easier achieved via CLI behind a GUI. You wouldn't see me dead playing videos via CLI. I'd launch Plex, search and play instead. 🥲
This is only Arch by the way. Most distros have pretty good forums
Forget gui, I just want to git clone something and then type the name of the application I cloned into a command and have it run. None of this infinite searching for dependencies that didn't get installed with the initial run dependency installer.
I use Arch btw, and we don't have this kind of problems usually. Everything is in the repo, all the dependancies are accounted for. Or if not, they are in the repo.
I use Arch btw.
Exactly why Docker was created
I would rather use Snap than Docker
Fuck Docker and their bullshit pricing schemes
Agreed but it is easy to copy paste terminal commands.
Not so convincing if you're just a causal user that has to trust random strangers with a unknown command that could just bork your whole OS.
Not wrong. Luckily I can read Bash at a middle school level lol. When in doubt, don't.
Assuming you can find one that actually does what you want
I mean, it obviously depends on what you're doing, but usually it's easier to find the right command than the right GUI, because implementing a CLI is a magnitude less work than implementing a GUI...
Easy, you just spin up a new instance for each tutorial you find, copy paste all of them, and keep whichever is still working
CI/CD bro
Honestly having such easy access to cli tools is very nice for when you want to work on a machine that doesn’t have a gpu
...I mean... he is not wrong.
#yearofthelinuxdesktop
which i usually only need for first time setup for my monitors then save the configuration to a script
eh, the cli is easier to use, anyway
Usually.
But have you ever used
arandr? Literal godsend.Yeah, xrandr can suck my dongle
bash noob
Shells offer a significantly faster and more powerful way of running programs when you know how to use them. The "helpful" Windows user is kneecapping the noob by offering a shiny but limiting GUI. Once you get a grasp of basic command line tools, you'll wonder why you bothered with pointing and clicking stuff.
I feel like the shell becomes much more complicated when you want to use configs. Or anything other than basic commands. At that point it becomes a pain in the ass, or tedious.
Other than that I agree. Also, GUI file managers are still superior. Sue me.
I still don't get why people like vim. Like sure, I use it to edit config files and stuff that needs sudo permissions, but in all honesty, if I could use any gui for that, like Kate, I wouldn't see any reason for using vim. Why do I need to relearn years how to Ctrl+ f or exiting the editor? buT iT'S FaStEr. Really? You spend how long looking up guides and cheat sheets on how to use it and it's faster? I mean sure, use what you are comfortable with but can you really say it's that much faster than just any text editor out there?
It's like Dvorak. You can be ~5% faster once you get over the turly enormous learning curve. The problem is, for most people, that 5% does not justify the huge initial investment.
Why would it though? If performing an action through the terminal shaves off only 2-3 seconds who cares?
If I want to open firefox though the terminal I can do that, sure…or I can just point and click on my taskbar/desktop. The time difference is virtually unnoticeable.
There’s a reason GUIs blew up. It’s not just because of user accessibility. There are legitimate things that are faster or less of a hassle with GUIs and I feel like the Linux community forgets that sometimes. Like using the terminal somehow makes them superior.
I can't wait for "I use dvorak btw" to be the new thing. The final stage after you become a vim using Linux expert
I'm new to Linux, and pretty new to Vim, but for me personally it works because of a couple of reasons:
(i) speed. yes, it's faster once you spent a little bit of time getting used to it. Vim movements or motions just make so much more sense in my mind, and being able to do all of them with few keystrokes feels pretty good and saves time.
(ii) comfort / muscle memory. This kind of ties to (i), where I just feel comfortable with my hands staying roughly at the same place on the keyboard the entire time I'm editing or writing something. Jumping here and there, deleting and copy-pasting, search/search-and-replace, creating-using-erasing macros, etc; things just feel so crisp and effortless.
(iii) simplicity. It is a terminal-based text editor, and so for me it's distraction-free. I just want to open up a text file and edit some stuff or even do some bit of writing, and I don't really feel like opening up a GUI text editors just to edit some stuff, or even write some stuff! I use Vim to write almost everything and it feels really good.
But when it comes down to it, anything like Kate or Notepadqq or any generic text editor works just fine.
The only reason I like vim is because I've literally never seen a Linux installation that didn't have vim. As a result, I know like 5 whole vim commands so I can still technically function on bare-bones installations. And even then, I only learned those 5 vim commands the first time I ran into a computer that didn't have nano or pico
Additionally, vim key bindings work in some other places too - like
manandless(and most pagers I think). It also works in bash if youset -o viwhich by default uses emacs keybindings. Ctrl+x, Ctrl+e (Shift+V in vi mode) to open your current entered command in$EDITORwhich is handy for really long commands. Then save it in said editor, and boom - it runs in your shell.The keybindings (vim and emacs alike) is actually a feature of GNU's readline library that bash gets for free since it uses it, the same trick works in other places that use the same library like a lot of REPLs and
gdb(though those programs would need to expose their own way to change between vi and the default emacs mode).That itself is a very good reason to know some basics of how to navigate around emacs and vi[m]!
And now for the second time in my life, I'm tempted to learn a bit more about the old gods of text editing. Damn you! /s
THANK YOU.
I spent time learning vim and using a file manager (forgot which one) but after awhile I realized it’s less frustrating just using a damn GUI. I feel like the time difference isn’t too much discernible. More than anything vim is just frustrating.
When you master the tab key and the mouse cursor in a text editor, it’s a breeze.
And everything can be easily automated on shells, i love how i can setup a task on my pc and once finished send a request over wifi to my phone and use termux to generate a notification
It's a matter of choice.