The LQ poll series continues. For desktop Linux use, do you prefer working in a terminal or a GUI?

--jeremy

I'm happy in a terminal for most things, but a GUI for internet, videos, & time waster games.

5 members found this post helpful.

Both, of course!

System tasks, coding, directory maintanance, etc. in terminal.
Overwiews, coding checks, advanced text edit, PDF work, etc. in a GUI.

And mostly, in these days, one works in a very convenient way: in a terminal within the GUI!

10 members found this post helpful.

Termial

1 members found this post helpful.

Ditto.

1 members found this post helpful.

Use the terminal quite often, but the GUI makes some things much easier.

1 members found this post helpful.

The terminal, including bash and friends, and python and friends, to get work done.
https://fossbytes.com/a-z-list-linux...ine-reference/
https://www.educba.com/python-commands/

GUI to browse the internet, edit documents, watch videos.

1 members found this post helpful.

GUI for regular daily use. Terminal for problem-solving.

2 members found this post helpful.

They complementary. Of course little precision is needed. Say running twm means I use desktop? But from other hand one can change some window managers into fully featured desktop. But if someone is running Gnome, KDE, Cinnamon, Deepin - then rather not for reason to work with terminal. Time to time may happen. So for me complementary means lightweight desktop or good window manager + intensive use of terminal.

1 members found this post helpful.

I generally use a GUI for most things, but I frequently make use of a terminal window that I always keep open.

The first part of the answer is going to sound really weird. But the command line thinks more like I do. I mean guis are nice, especially when it comes to single use, single purpose, apps. But totally useless when it comes to trying to figure out why something is doing something, what states something is in, or what's really happening underneath the GUI. A GUI fails, quite often because the very same thing that is causing the problem you are having colors the output and objectivity of the GUI you were using, to analyze it. Also there is the problem with the fact that most GUIs attempt to help me. Quite often, their best attempted help, is like having my four-year-old help me in the garage when I'm trying to change my oil. I appreciate their effort but it often causes more work than I originally had to do.

6 members found this post helpful.

Depends what I'm doing. Mostly everything is terminal. Whether it's admin or development. The only time I use a GUI is for web browsing, email or gaming and very seldom the odd bit of graphics editing.

Command-line puppy here.

I use the GUI for web surfing & mail.

A great example of why I hate GUIs. This is now my second attempt at answering the question. Why because when I touch the screen, on the answer before, this GUI decided I needed to go back. Losing my first answer. GUIs lie. They lie by intent. They lie by attempting to be helpful and analyze the data for me, often in a manner, and with an objective that is not the one I seek. Give me the simple basic command line tools. Statically compiled. If needed. And not attempting to analyze the data, just give me the data. Hopefully, I've now got all the GUI spellings accurate. My GUI, had spell checked to a different word every time.

3 members found this post helpful.

Both. I use the terminal for builds, status, file searches, etc., and the GUI for long term Emacs editing sessions (though I use it from the terminal for quick&dirty things like config changes) and the like.