Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Okay, and then in addition to the shell, reference is often made to an editor--usually emacs or vi. How does the "editor" figure in with the shell? You apparently have to have an editor and different shells use different editors, is that correct?
Okay, and then in addition to the shell, reference is often made to an editor--usually emacs or vi. How does the "editor" figure in with the shell? You apparently have to have an editor and different shells use different editors, is that correct?
You do not need different editors in different shells.
I've been using vi(m) ever since I started with computers and used it on hp-ux, solaris, AIX, FTX, and Linux using bash, ksh, sh (real sh, not the linked one) and on a few occasions csh.
The way you navigate on the shell command line (previous command, edit commands, search commands etc) is different. Ksh uses a vi style command line interface, bash does not. But this can be easily changed by editing the shell specific start-up files.
I would like to thank you all for your valuable information. The details are very clear and informative. I currently using Beginning the Linux Command Line By Sander van Vugt. Its good, thanks for sharing the useful information.
Can you explain exactly what is the function of the editor? I constantly see and hear references to it, but I don't understand what it does. I know the choice is between vi(m)
and emacs and arguments about which one is better rival the ferocity of debates over which distro is better! But what does the editor do?
Can you explain exactly what is the function of the editor? I constantly see and hear references to it, but I don't understand what it does. But what does the editor do?
An editor is just a program that you use to create or edit files. It doesn't do anything by itself.
If you are familiar with Windows: Notepad is also an editor (although not a very good one ).
Quote:
Originally Posted by Yuhan
I know the choice is between vi(m) and emacs and arguments about which one is better rival the ferocity of debates over which distro is better!
Although vi(m) and emacs are used a lot, there are many other editors you can use (nano is also used by many). And editors are not distro specific. A distro chooses one to make sure you have one to start with, but you can change the editor you use if you want to do so.
Hmm. So the shell itself cannot create or edit files?
The shell itself cannot do anything by itself. It is a special program that allows you to interact with it by entering certain commands from the keyboard; the shell will execute the commands and display its output on the monitor.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.