Editor Wars!


View Poll Results: What is your favorite editor?
vi ( or a clone thereof ) 27 77.14%
emacs 3 8.57%
notepad.exe 3 8.57%
Other visual editor (In a GUI environment) 2 5.71%
Other 0 0%
ed / ex 0 0%
edlin.exe 0 0%
pico 0 0%
Voters: 35. This poll is closed

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Editor Wars!
# 15  
Old 02-04-2002
With regard to the sidebar on MSWORD and the news article, here is my reply, as requested:

Quote:
It is not important what I think, what is important is what the people whom I communicate (and work with) think and use. I must communicate in formats that they use in their business operations. For most large companies, that means: MSWORD, ASCII, ASCII/HTML, POWERPOINT, EXCEL, PDF, FLASH. Most of these formats are vendor proprietary and they all are 'de facto' standards in the business world. I don't dictate to people how to commuicate, I accept and create communications in their format because the goal is to [I] communicate[I]. I don't think it is wise to allow personal bias to stand in the way of communications.
I'm not a supporter of (IT) religious wars and jihads either and don't find any userfulness in them. Bashing products and companies has little value. If two people want to communicate using the "foo" format, then that is their choice, freedom and right. Cooperation is based on mutual gain. Obviously applications like MSWORD, PPT, and XLS have a broad base of users who like to use them.... they do have a choice, many choices.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

2. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set... (6 Replies)
Discussion started by: aarora_98
6 Replies

3. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

Hi, I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question. How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'? As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
Login or Register to Ask a Question
HISTORY(5)							File Formats Manual							HISTORY(5)

NAME
history - record of current and recently expired Usenet articles DESCRIPTION
The file /var/lib/news/history keeps a record of all articles currently stored in the news system, as well as those that have been received but since expired. In a typical production environment, this file will be many megabytes. The file consists of text lines. Each line corresponds to one article. The file is normally kept sorted in the order in which articles are received, although this is not a requirement. Innd(8) appends a new line each time it files an article, and expire(8) builds a new version of the file by removing old articles and purging old entries. Each line consists of two or three fields separated by a tab, shown below as : <Message-ID> date <Message-ID> date files The Message-ID field is the value of the article's Message-ID header, including the angle brackets. The date field consists of three sub-fields separated by a tilde. All sub-fields are the text representation of the number of seconds since the epoch -- i.e., a time_t; see gettimeofday(2). The first sub-field is the article's arrival date. If copies of the article are still present then the second sub-field is either the value of the article's Expires header, or a hyphen if no expiration date was speci- fied. If an article has been expired then the second sub-field will be a hyphen. The third sub-field is the value of the article's Date header, recording when the article was posted. The files field is a set of entries separated by one or more spaces. Each entry consists of the name of the newsgroup, a slash, and the article number. This field is empty if the article has been expired. For example, an article cross-posted to comp.sources.unix and comp.sources.d that was posted on February 10, 1991 (and received three min- utes later), with an expiration date of May 5, 1991, could have a history line (broken into two lines for display) like the following: <312@litchi.foo.com> 666162000~673329600~666162180 comp.sources.unix/1104 comp.sources.d/7056 In addition to the text file, there is a dbz(3z) database associated with the file that uses the Message-ID field as a key to determine the offset in the text file where the associated line begins. For historical reasons, the key includes the trailing byte (which is not stored in the text file). HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.12, dated 1996/09/06. SEE ALSO
dbz(3z), expire(8), innd(8), news-recovery(8). HISTORY(5)