LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
LinkBack Search this Thread
Old 02-16-2009, 03:18 AM   #1
Fred Caro
Member
 
Registered: May 2007
Posts: 645

Rep: Reputation: 56
command line//text editor


Dear Sirs/Madams,
at the risk of sounding very thick, what is the point of having a text editor when you have a comprehensive command line?
How does the next line command work in vi or does it not exist?

Roy.
 
Old 02-16-2009, 04:14 AM   #2
linuxlover.chaitanya
Senior Member
 
Registered: Apr 2008
Location: Nagpur, India
Distribution: Cent OS 5/6, Ubuntu Server 10.04
Posts: 4,615

Rep: Reputation: Disabled
What do you exactly mean? Are you trying to compare bash and vi?
 
Old 02-16-2009, 04:48 AM   #3
Junior Hacker
Senior Member
 
Registered: Jan 2005
Location: North America
Distribution: Debian testing Mandriva Ubuntu
Posts: 2,687

Rep: Reputation: 59
Vi is not installed anymore on any modern Linux, vi improved (vim) is now installed by default. Take a look at your package manager, vi is probably not on the list. But for the old geeks, you can still use vi in commands as vim is backwards compatible.
To start a new line, put cursor on the line above where you want to add a new line in the file, hit the "o" key, this will put you in insert mode on a new line.
If you have a full version of vim installed, you can type: vim tutor in a terminal to take a half hour course on using vim.
These are the man pages for vim which does the same only more comprehensive and not so easy to understand for a vi newbie compared to the tutor.
These are stock quotes for man vim.
 
Old 02-16-2009, 11:05 AM   #4
bach-fiend
LQ Newbie
 
Registered: Feb 2009
Location: St Paul, Minnesota, USA
Distribution: Redhat Fedora 10; someday planet CCRMA
Posts: 11

Rep: Reputation: 0
Whenever I do anything that is big (eg long command line(s) etc) or that I might want to look back on (eg email replies) I put it in a file first using emacs (or vim). I find this the most robust way to look back at what I actually said when things don't work as I expect. And I used to be quite proficient at the [korn then bash] shells, but still find that there are typos and other mistakes I have trouble seeing. Rather than sit there fighting the computer, I sometimes set the troublesome code aside for a few hours (or days).

Because I live in Emacs most of the time, I've never bothered learning command history, all the cool things you can do with (!) history substitution, etc. I just don't need them much.
 
Old 02-18-2009, 10:55 AM   #5
Fred Caro
Member
 
Registered: May 2007
Posts: 645

Original Poster
Rep: Reputation: 56
junior

Thanks for your reply, it has saved me a lot of time and motion.
If I can appeal to your good nature further; why does a text editor operate differently to a word processor, when a text editor is, presumably, meant to be a simplification.

Fred.
 
Old 02-18-2009, 11:20 AM   #6
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
Quote:
Originally Posted by Fred Caro View Post
why does a text editor operate differently to a word processor, when a text editor is, presumably, meant to be a simplification.
Have you not just answered your own question there?
 
Old 02-18-2009, 11:23 AM   #7
rtrahan
Member
 
Registered: Jan 2009
Location: Georgia
Distribution: OpenSuse Fedora
Posts: 64

Rep: Reputation: 17
A text editor does not use the same functions as a full word processor because of the manner in which it is saved. A text editor does not allow you to change font styles, insert pictures, etc. It is processed as ASCII language with no characters such as -> return or ...carriage space, etc. It is only text. That is why it is used for running commands and for programming, the interpretor or compiler cannot read all of the formatting characters used in a word processing programs, it is only text.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Command-line output to GUI text editor hex1a4 Linux - General 2 04-10-2008 11:49 AM
Enhanced command line text editor netsoft2005 Linux - Software 2 07-14-2005 07:42 AM
Mandrake 9.1 installed command line text editor plexi100 Linux - Newbie 1 11-07-2003 10:25 PM
VI text editor in command line InSane103 Linux - Software 4 07-09-2003 09:04 PM
vi as Command Line Editor taz75 Linux - Newbie 8 01-04-2002 01:30 PM


All times are GMT -5. The time now is 05:48 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration