SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For those users, the GUI is far more powerful than the commandline
Please define "powerful" in this context.
As I see it, a GUI can never be as complete (or powerful) as a CLI, simply because the CLI is unlimited. Due to their nature, GUIs are always a compromise between form and function, so something which one person considers "powerful" will be useless to another.
A CLI faces none of these limitations, purely because it doesn't have to conform to anyone's idea of how it should look or behave or what functionality it should contain.
As I see it, a GUI can never be as complete (or powerful) as a CLI, simply because the CLI is unlimited. Due to their nature, GUIs are always a compromise between form and function, so something which one person considers "powerful" will be useless to another.
For users who don't know how to use the commandline, the GUI is more powerful. I'm just saying that I don't believe X's sole purpose is to extend the functionality of the CLI. For many users (even on Linux), it is a replacement of the GUI.
Well... it comes down to your apps, and most of the apps I use are graphical. I use the CLI pretty much exclusively for system administration; I keep a terminal emulator open on each of my virtual desktops. Why not have the best of both worlds?
Well... it comes down to your apps, and most of the apps I use are graphical. I use the CLI pretty much exclusively for system administration; I keep a terminal emulator open on each of my virtual desktops. Why not have the best of both worlds?
Well that's what I have my Ubuntu for
But nothing beats the feel of typing out your demands and having them met with snappy, textual response!
Here's a script I have as an example of what I mean about CLI and GUI working together
Code:
#!/bin/bash
#
# Play Random CD.
DIRECTORY="$( find /local/Music/ -type d -path "/local/Music/*/*" -maxdepth 2 | sort -R | head -n 1 )"
pkill ogg123 >/dev/null 2>&1
if [ "$DISPLAY" = "" ]; then
ogg123 -q "$DIRECTORY" &
else
audacious -E "$DIRECTORY" >/dev/null 2>&1 &
fi
I simply type "playcd" at the command-line and it picks a CD from my collection at random and if I'm running in an X-Window environment it starts the audacious GUI to play it in a temporary playlist.
If I don't feel like listening to that CD, I just type playcd again and it will replace the temporary playlist with a new one in the already running instance of audacious.
You'll also see that I have ogg123 as a fallback incase I'm not running in X. (All my music is in .flac)
The point I'm trying to make showing you this is that because the audacious developers understood that the X GUI and command-line aren't two completely separate and competing environments we users can do nice little things like this from the command-line.
CLI is not outdated or obsolete and the GUI is not a replacement. Their full power is only seen when you start to use them together.
P.S.
My music is stored in a "/local/Music/Artist/Album/track - title.flac" structure, if anyone wants to try the above code for themselves.
When I used to self-host my website, I almost never used the GUI for maintenance on my server (Slackware). (I used the GUI a lot to make it work in the first place when I was learning my way around Linux.)
I'd log in, do what I had to do, and log out.
Now I tend mostly to use a GUI (Fluxbox) for day-to-day computing (the website is out on GoDaddy), but I'm likely to do maintenance from the GUI. Even on my Ubuntu and Debian machines, I'm more likely to open a terminal and sudo update-manager than I am to start Update Manager from the menu.
The command line is always faster, as long as one knows the commands.
On my machine I use dwm as window manager. Basically just because its very nice to work with terminals (in my case urxvt) within that wm. The only reason I need X is because of Firefox (with the vimperator plugin for easy keyboard control) and sometimes picture editing or LibreOffice. So even though I am using X on a daily basis you could consider me a non-GUI user.
On my machine I use dwm as window manager. Basically just because its very nice to work with terminals (in my case urxvt) within that wm. The only reason I need X is because of Firefox (with the vimperator plugin for easy keyboard control) and sometimes picture editing or LibreOffice. So even though I am using X on a daily basis you could consider me a non-GUI user.
Exactly the same for me, except I use Openbox. I also wonder how many Slackware users don't even use a GUI file manager but handle it all via the command line. I've tried to use mc on occasion, but to me it's more of a hindrance than a help.
I'm sure a large part of my preference is due to laziness, having acquired most of my command line knowledge ~20 years ago. But it's also nice not having to relearn everything whenever some GUI designer decides to change it.
I also wonder how many Slackware users don't even use a GUI file manager but handle it all via the command line. I've tried to use mc on occasion, but to me it's more of a hindrance than a help.
I agree that a GUI file manager is a major hinderance! I have tried to use mc also but if you are already in a shell nothing could be faster than the simple navigation and manipulation commands already available.
Another benefit of doing all file management from the shell is that your awareness of where you are and what you have is light years ahead of those who rely on GUI file tools.
Last edited by astrogeek; 12-30-2010 at 01:32 AM.
Reason: typo
Distribution: Slackware (mainly) and then a lot of others...
Posts: 855
Rep:
Well, the default init for slackware is 3 and I am going to let it be there as long as slackware decides to change it. I only use gui to watch movies, edit some pictures or to play games (pysol,kpat).
Other than that I really see no use to run startx.
i have yakuake autostart in my slackware. I use CLI for my file management and administrative task. but I use Firefox for browsing(which i use heavily).
I use the command line for anything related to the file system or configuration. I use FVWM2, customised to exactly how I want it. I don't even have a file browser in the menu lol.
Ask this in the Ubuntu section and I'd imagine you'd get a set of very different answers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.