Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
It seems that most hardcore Linux users like to get their hands dirty in a terminal window rather than relying too much on graphical tools. I'm wondering... how far do you take it?
1. Do you use a graphical file manager/browser or do everything from the command line? If you're moving/copying several files involving long pathnames and filenames, do you type everything out or "cheat" and use an app in X?
2. For the developers out there, when editing code do you use a graphical editor with nice syntax highlighting or do you prefer command-line editors.
3. And finally, speaking of command-line editors... does anyone really use vi/vim for all text editing? I understand the importance of knowing how to use it in case you're on a machine that doesn't have the more user-friendly editors, but it seems like it just takes too long to accomplish a task that way (what with jumping back and forth to the esc button, etc.).
1) It depends on what I'm doing, so I use both... But my KDE always has several terms open I still tend to install rpms and edit configs and many thing at CLI level. But I also do a lot with filemanagers. Some things are easier one way and others are easier the other way... With auto completion the long filenames don't matter much and I hit Tab a lot I use wget, ps aux and kill and rpm and jed/vi, etc...
2) Don't code much these days but the little I've done has bee both in CLI and gui.
3) I found jed years ago and it's the first thing I add to all my installs I tend to use vi when I have to - it's all I got on the smoothie box I don't mind vi tho. I'm just more used to jed and find it quicker.
1) always in command line. i just dont see the point of a file manager draw pictures of your files for you. tab completion takes care of long filenames. its a lot faster once you get used to it.
2) vim.
3) vim. once you get used to it, editing with vim is a lot faster than an "easy" text editor.
I should say one of the reasons I use a guio= filemanager rather than cli would be for something like digital photos. In KDE i get a preview thumnail of each pix, so then I easily can pick the ones I want to copy or archive or whatever. But if I'm shifting whole directories around I might use cli, depending on my mood
1) Yup, I do all file moving and application launching from a terminal (tab completion is a beautiful thing, as is the {a, b, c} syntax in Bash). I used to be a diehard KDE (and Konqueror) fan, but i recently bought a 500MHz laptop, and installed Fluxbox, and ever since I've been using the command line for most things (KDE and Gnome both take a long time to start on machines as slow as my laptop). When you're dealing with sequentially numbered Kismet dumps and large numbers of similarly named files, the shell is much faster than a GUI file manager. Scripting is also essential to get any repetitive work done fast. The file previews are useful in Konqueror, though, as is the ability to create image galleries. I use kuickshow to view photos (PgUp and PgDn / mouse wheel to move between images in the same directory. Nice).
2) I use Emacs for coding (Java and shell mostly), and I'm usually in Fluxbox, so I suppose I'm half way between GUI and text. I use the Emacs navigation keys almost exclusively (Ctrl-N, Ctrl-P etc) instead ofthe mouse, so it's pretty much the same experience as being in text mode. Emacs does highlight syntax for me in colour though.
3) I also use Emacs for all text (and someties non-text) editing. Emacs can deal with displaying binary data without falling over, and I find the commands a lot faster to use than Vi's. (No constant switching modes with esc). I use my Caps-lock key as a Control key, which makes life a lot easier on the fingers using the Emacs commands. The ability to have multiple files open and displayed in Emacs is great too; I don't know if this is possible in Vi.
After a while not using GUI tools all the time, you start to become very efficient on the command line. Installing Fluxbox, and using the command line for most things has actually enhanced my Linux experience a lot - the sed, awk and grep utilities are really essential once you know how to wield them. I don't really miss GUI tools and file browsers on my newly aquired old laptop, and I'm actually considering using Fluxbox as my desktop on my main machine too. I'll keep KDE around to impress the Linux doubters, though.
I'm not a guru, or even hardcore...wasn't going to post until I read #3. I use Vim for everything text. It's better than anything else I've tried, IMO.
As far as using commandline, I'm sorta halfway between that and GUI. I prefer having an X window manager running because I think browsing the web with links is crap, and I use Gimp a lot. But for a lot of other tasks I prefer commands, or at least terminal-based applications (like mc, mpg321, dekagen, bitchx, mutt, etc)
Yep. I don't use a gui when I'm working on my printer / mp3 server either I just telnet in and do what I have to do... There's not a lot of point on a server... Mind you the smoothie box has a webadmin so the kids can connect to the web easily...
Of course on the main box I haven't used cli to browse the web since the old days (much) and I haven't found a cli gimp replacement
OK. I really need to lock up my desktop to protect it from my kids.
In the KDE there is a button on the tastbar. What is the command for it? Can I lock my screen from fluxbox?
This is needed for the survival of this system - there are plenty of little hazards on and under the table.
3. And yes if I am on a Linux box I use vi unless I'm doing something where it needs text formatting. Biggest problem is when you go to a GUI word processor and keep trying to hit ESC. You can type a lot faster when one hand isn't on a mouse...
Originally posted by jrdioko
1. Do you use a graphical file manager/browser or do everything from the command line? If you're moving/copying several files involving long pathnames and filenames, do you type everything out or "cheat" and use an app in X?
I do these things in an xterminal, and I make lots of
use of tab-expansion and bash-automated-completion
(for instance for scp-ing stuff to other hosts)...
Quote:
2. For the developers out there, when editing code do you use a graphical editor with nice syntax highlighting or do you prefer command-line editors.
I use emacs in both the shell and the GUI, with syntax-highlighting
in both environments ;)
Quote:
3. And finally, speaking of command-line editors... does anyone really use vi/vim for all text editing? I understand the importance of knowing how to use it in case you're on a machine that doesn't have the more user-friendly editors, but it seems like it just takes too long to accomplish a task that way (what with jumping back and forth to the esc button, etc.).
I know the basics of vi (enough to do crontab :}) but
can't stand it, I REALLY use emacs for all editing. My CV,
for instance, is hand-coded HTML, done in Emacs ... as
for the "seems like it just takes too long" I'd probably
have to say that I'm almost certain that I can beat you
to most tasks when you use the mouse ;)
And since someone mentioned the term word processor:
Quote:
Code:
"Uncle Cosmo ... why do they call this a word processor?"
"It's simple, Skyler ... you've seen what food processors do to food,
right?"
-- MacNelley, "Shoe"
1.mainly command line with wildcards of course
2.i prefer syntax highlighting coding is hard enough :-P
3. i use vi and vim alot when admining servers and if x-server isnt up. Very useful to know. I wouldnt choose it for programming though. VI=virtually impossible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.