> ok to give README a title?
Instead of just a title, give the README a refresh but hopefully
maintain the essence of what was there.
- remove gratuitous ()'s
- change Mg to mg (copy man page spelling since no-where is consistent)
- "there are handling charges for obtaining it"??? Refering to GNU.
- Plus some para wrapping.
ok?
-lum
Index: README
===================================================================
RCS file: /cvs/src/usr.bin/mg/README,v
retrieving revision 1.11
diff -u -p -r1.11 README
--- README 7 Jun 2012 15:15:04 -0000 1.11
+++ README 8 Jun 2012 22:11:16 -0000
@@ -1,29 +1,25 @@
-[This is an edited version of the original mg README, updated slightly to
-reflect changes in the last 20 years.]
+mg README
+---------
+mg is a Public Domain licensed Emacs style editor. It is intended to
+be small, fast, and portable for people who can't (or don't want to)
+run real Emacs for one reason or another. It is "broadly" compatible
+with GNU Emacs because there shouldn't be any reason to learn more
+than one flavor of Emacs. mg was formerly named MicroGnuEmacs, the
+name change was done at the request of Richard Stallman. Emacs is a
+creation of Richard M. Stallman, Chief GNUisance. Emacs and other
+portions of GNU as they are released are essentially free, and so is
+mg (though there may be handling charges for obtaining Emacs).
+
+mg is not associated with the GNU project. The mg authors individually
+may or may not agree with the opinions expressed by Richard Stallman
+in "The GNU Manifesto". Most of mg does not have the copyright
+restrictions present in GNU Emacs. However, some of the system
+dependent modules and the regular expression module do have copyright
+notices. Look at the source code for exact copyright restrictions.
-Mg (mg) is a Public Domain EMACS style editor. It is "broadly"
-compatible with GNU Emacs, the latest creation of Richard M.
-Stallman, Chief GNUisance and inventor of Emacs. GNU Emacs (and other
-portions of GNU as they are released) are essentially free, (there are
-handling charges for obtaining it) and so is Mg. You may never have
-to learn another editor. (But probably will, at least long enough to
-port Mg...) Mg was formerly named MicroGnuEmacs, the name change was
-done at the request of Richard Stallman.
-
-Mg is not associated with the GNU project, and most of it does not
-have the copyright restrictions present in GNU Emacs. (However, some
-of the system dependent modules and the regular expression module do
-have copyright notices. Look at the source code for exact
-copyright restrictions.) The Mg authors individually may or may not
-agree with the opinions expressed by Richard Stallman in "The GNU
-Manifesto".
-
-This program is intended to be a small, fast, and portable editor for
-people who can't (or don't want to) run real Emacs for one reason
-or another. It is compatible with GNU because there shouldn't be
-any reason to learn more than one Emacs flavor.
-
+You may never need to learn another editor apart from mg but probably
+will, at least long enough to port mg...
Beyond the work of Dave Conroy, author of the original public domain
v30, the current version contains the work of:
@@ -36,7 +32,7 @@ v30, the current version contains the wo
[email protected] Stephen Walton
[email protected] Marion Hakanson
-People who have worked on previous versions of Mg:
+People who have worked on previous versions of mg:
[email protected] Dave Brower
@@ -61,30 +57,28 @@ an infinite loop, aborting with a stack
Overwrite mode does not work in macros. (Characters are inserted
rather than overwriting.)
-Dired mode has some problems: Rename does not update the buffer.
+Dired mode has some problems: Rename does not update the buffer.
Doing a dired again will update the buffer (whether it needs it or
not) and will lose any marks for deletion. .. and . are not
-recognized as special cases.
+recognized as special cases.
On systems with 16 bit integers, the kill buffer cannot exceed 32767
bytes.
-Unlike GNU Emacs, Mg's minibuffer isn't multi-line aware and hence
+Unlike GNU Emacs, mg's minibuffer isn't multi-line aware and hence
some commands like "shell-command-on-region" always pop up a buffer to
-display output irrespective of output's size.
+display output irrespective of output's size.
-While navigating source code using Mg's cscope commands, the cursor
-is always at the match location rather than in *cscope* buffer. Mg uses
-the same keybindings of GNU Emacs's xcscope package for it's cscope commands.
-As Mg's keybindings are case-insensitive some of the commands don't have a
-default keybinding.
+While navigating source code using mg's cscope commands, the cursor is
+always at the match location rather than in *cscope* buffer. mg uses
+the same keybindings of GNU Emacs's xcscope package for it's cscope
+commands. As mg's keybindings are case-insensitive some of the
+commands don't have a default keybinding.
New implementation oddities:
insert and define-key are new commands corresponding to the mocklisp
-functions in GNU Emacs. (Mg does not have non-command functions.)
-(Mg's insert will only insert one string.)
-
-The display wrap code does not work at all like that of GNU emacs.
-
+functions in GNU Emacs. (mg does not have non-command functions.)
+(mg's insert will only insert one string.)
+The display wrap code does not work at all like that of GNU emacs.
