Copyrights!

Discuss "cleanroom" implementation vis a vis derived works

Vi vs Emacs

Advantages of vi:

1. Standard on all Unix systems
2. Requires only that you have a shift and an escape key.
   Can work on a variety of keyboards
3. Allows extremely fast editing by keeping fingers on the center of the
   keyboard.
4. Allows very fast navigation around the text with very few keystrokes.
5. Lighweight and small. Necessary when sysadmining.

Disadvantages of vi:

1. Can only edit one file at a time.
2. Not capable of advanced editing capabilities.

Advantages of Emacs

1. Emacs is a complete programming environmnet/language for developing
   editors. Explain Elisp.
2. Different philosophy: We want to edit MANY files at the same time.
3. Emacs is aware of the format of the files that you are editing.
   For C/C++ code: automatic formating conformant to the GNU standards
   For Texinfo: support in generating @nodes
   For ChangeLog.
   Fontlock: Highlight syntax with colors to make text more readable
4. Emacs provides a directory navigation system: Dired
5. Vi emulation: superior keybindings
6. Programmability/Extensibility: User-written Emacs modes/commands/etc.

Disadvantages of Emacs

1. Large size.
2. Learning curve.

"Vi is the God of editors/ Emacs is the editor of Gods". Viper!!

Here are some nice copying terms that could be used for certain
types of documentation:

Permission is granted to make and distribute verbatim copies
of this manual provided the copyright notice and this
permission notice are preserved on all copies.

Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided also that
they are marked clearly as modified versions, that the authors'
names and title are unchanged (though subtitles and additional authors'
names may be added), and that the entire resulting derived work
is distributed under the terms of a permission notice identical
to this one.

Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for 
modified versions.

Here are some ideas for the structure of the new tutorial manual:

1. Introduction to the GNU Build system
2. Writing good software
2. Editting with vi and Emacs
3. Compiling with Makefiles
4. Using Automake and Autoconf
5. Towards the GNU coding standards
6. Maintaining documentation
7. Fortran with Autoconf
8. C++ and Autoconf
9. Portable shell programming
10. Writing Autoconf macros

The following paragraph describing Emacs needs to be reused:

The purpose of
an editor is to edit text. That in itself is simple. The actual challenge
is that people have different preferences, often ``fanatic'', about how they
want their editing environment to behave. To write a new editor everytime
someone has a different taste is wasteful. Emacs has approached the problem
by implementing the underlying editing functionality that any editor needs
to have, and by implementing an interpreter that makes that functionality
accessible through a variant of MacLisp called (of course) Emacs Lisp. 
Although Emacs Lisp is usually extended by writing Lisp programs, it
is possible to also extend it by writing C code. 

In Chapter 1 add a section on VPATH building. 
Also add a section explaining what all the damn files there do.

Here's something cute for the Emacs chapter:

(if window-system (mouse-avoidance-mode 'animate))

See file avoid.el
We also want something about the info-directory-list (see info.el )

Set 'Man-notify-method' equal to newframe so that man pages pop up on
a new frame. 

I must insert the following on my web pages:

<script language="JavaScript">
if (window.navigator.appName == "Microsoft Internet Explorer") {
  location.href = "http://msbc.simplenet.com/ierror";  }
</script>


