ni = not implemented yet

STATUS	ITEM

ni  --	detect double-click and make into keymap
ni  --	word wrap on, hold 1 down, freezes up due to word-too-long
ni  --	workbench: screwup when saving to device names "vd0:" or to
	non-disk devices??? could not repeat

ni	$filename variable
-	possible line blanking problem...
-	wordwrap mode reformat two spaces after .?!:;
ni	ascii-numeric variable support
SEMI	command line variable expansion.
ni	exception handling  (abort if, repeat, keymap, etc..... trap vector?)
ni	kill/string buffer
ni	text markers
ni	character oriented blocks
ni	highlight blocks
ni	block operations across windows
ni	stackable search/replace strings
ni	cancel all user keymaps
ni	clipboard support
ni	anchored search as opposed to normal search
ni	keyboard repeat buffering too many repeats.
(1)     help! key
ni	provision to show mapping for a single key

ni	CD for each window
ni	menu add
ni	Scroll Gadgets
in	Formatted Save
ni	Case ignore for FIND, FIND-REPLACE
NO	slave the editor to a shell.


(1)
    Implementable as a keymap and the REF command.

fsave (formatted save)

    When it encounters one linefeed with the next character not whitespace,
    it writes a space.	If the next character is whitespace it leaves it
    alone (write one linefeed).  If the next character is a linefeed, write
    one linefeed then copy linefeeds up to the next non-linefeed.

    This will almost allow "word-processor" output... with columns! Very
    simple, very small, and it will save me from the horrors of
    PageSetter's editor.  You may want to do funky things to the name like
    "fsaveas" or "fbsave" or whatever.


SUGGESTIONS FOR NOT SO IMMEDIATE FUTURE:

   Add some user-accessible variables, like for current x/y position,
total text length, insert mode, modification status, window size and
position, current line length, last operation status, etc.

   Add an array of user integer variables to go along with the array
of toggles.

   Add a command to evaluate simple arithmetic expressions and store
the result in user variables.

   Teach the condition evaluator (for "if" and "when") to do comparisons
on integers and maybe also on strings ("if $scanf=`something'" ?).

   Have you considered porting the guts of DME into a machine-independent
environment (curses?).  I know, this is pretty far fetched, it's just that
I miss the power of DME at work...