caps as meta editor Files

About Bitwrot:

This editor tries for modelessness by using uppercase letters for the commands.

The modes wherein the file text is not shown:
    Help mode.  Enter with <escape>, exit with <back>.

The modes wherein a command needs additional user input to complete:
   -- 1 cursor command uses 2 chars to identify the target.
   -- alternative commands start with <A>.
   -- script commands start with <B> because cmdbat is shorter than cmdscript.

The other <A> to <Z> are single key commands.
Some may use additional input but get it from the surrounding text.
(The command to set hidden state info wants its own textline.)

The hidden state info includes:
-- auto-incrementing enumerator for lists.
-- search template.
-- robot keystroke list.
-- paste buffer, but access not currently implemented except by pasting it onto your document.


TRADE-OFFS
-- Bitwrot is an ascii-centric editor.
++ Bitwrot has a repeat-me robot function that helps with repetitive editting.
    A typical use would be word replacement, where at each seek <N>ext the user chooses to replace or not.
++ Directories can be edit stations.
    Bitwrot has a 2 keystroke command to access local file bitwrotdirc.
    bitwrotdirc is intended as a place to save file names for easy access.
++ All the memory bitwrot will use is allocated up front, only a window into larger files is kept in the buffer memory
-- Bitwrot leaves interim files laying around the directory where it is invoked; bitwrot-bounce, bitwrot-milestone.
++ Bitwrot can invoke bitwrot scripts by name.
    Bitwrot scripts can do more than a lot of pre-canned typing for you.
    Bitwrot has many commands to empower its scripts.
    This includes nestable script blocks that only run if the scriptflag is set.
    The scriptflag can be set or cleared upon successful searches
    or upon the text at the cursor matching
    or upon missing the search pattern
    or upon other tests.
-- You must create bitwrotscripts.txt and write the scripts to be able to use them.
++ Bitwrot users can do smart editting without the separate learning curve of sed.
-- Scripts using bitwrot tend to be more verbose than scripts using sed.
++ Bitwrot runs bitwrot-script on start-up so a shell script can prep that and invoke bitwrot as a smart editor.
-- Bitwrot lacks any import and export between its yank and your system's inter-app clipboard.
++ Bitwrot has a command to build any specific byte so output not limited to keyboard.
-- Specific bytes would have different meaning to non-ascii systems.

ONLY MY MOTHER LOVES ME:
Text cannot be rage-written in uppercase but must be gone back over; a chance to edit down the tone.
    -- a command to leave a case_mark, which gets eaten when used.
    -- a command to UPPERCASE all letters from the first case_mark on the current textline up to the next case_mark or end of line.
    -- a command to lowercase all letters from the first case_mark on the current textline up to the next case_mark or end of line.
    -- a command to Titlecase at the first case_mark on the current textline then lowercase up to the next case_mark or end of line.

Bitwrot runs in a terminal.  Bitwrot moved to an X display for a while, but
too often I was editting files before starting X.

 -----------------------------------------------------------

The history is now separate as it is so huge.

After a rash of early names bitwrot was released as "ced" until I finally noticed that name was taken.
Then it was "cim" for caps-is-meta; but that is also a name collision.
I now call it "bitwrot" as in "what hath bits wrought?".


LICENSE:
Bitwrot is released under GPLv3 to get it on SourceForge.
I should start a company that sells binaries for linux
but develop them on linux with bizarre file systems and character encodings.
I can distribute the source in my native format, but no one else can read it.
Just kidding.