NEWS

Details of most user-visible changes.

Version 3.2

The programmer's manual has been written (at last!).
Undo; devote as much memory as you want to keep track of all modifications to a buffer.
Proper arguments to commands.
Buffer menu for interactive buffer manipulation.
An Emacs-style local variables section can be embedded in a file; replaces the naff `::jade-code::' thing.
`Ctrl-k' works at last.
Now possible to interrupt jade while it's working (i.e. to let you kill infinite loops).
The Help system now has commands to list key bindings, display what is bound to any key sequence.
Use of the Latin-1 character set is now controlled by the minor mode `latin-1-mode'.
Can load, insert and save compressed (compress or gzip) files into/out of buffers transparently when running on Unix.
Transposing commands; `transpose-chars', `transpose-words', `transpose-exps'. Bound to `Ctrl-t', `Meta-t' and `Ctrl-Meta-t' respectively.
Can now run a shell in an editor buffer, very basic (no completion) but it works okay.
Support for using gdb through the shell interface, the current frame's source code is highlighted in a separate window.
`Ctrl-z' moves to `Ctrl-W' so that `Ctrl-z' can (de)iconify the current window
Some programs written for the previous incarnation will need to be altered; all will have to be recompiled. Now I've written the programming manual programs should work 100% (ish) in future revisions.

Version 3.1

Searching is now done through an Emacs'ish incremental search and replacing through a ``query-replace'' command
Now properly supports characters which print as more than one character (ie, proper tabs, ^L, \123, etc..)
Doesn't expand tabs to spaces anymore, this means that loading and saving of largish files is noticeably quicker
Lisp strings can now contain \0 characters, some functions don't handle them properly though. Amongst other things, this means that files containing nuls can be edited without [too many] problems.
Many improvements to the Info viewer, not least, the dir file doesn't have to have a tag-table anymore
Client editing. This lets you load files into a running editor from the command line. For example, if your mailer runs an editor on the message you're writing you can use the client to edit the message in a Jade that you are running.
The buffer prompt's completion is now controllable by the mouse as well as the keyboard. Click the right button to complete the current word. Double-clicking the left mouse button on one of the lines under the `::Completions::' line selects that completion.
text and indented-text major modes
Minor-modes. These provide small variations to the major-modes. For example, `overwrite-mode' makes typed keys overwrite whatever's under the cursor.
On Unix, a tilde (~) in a filename is handled properly in most cases
Files now preserve their access bits when backed up.
Unix version no longer crashes when trying to read a directory which doesn't exist
filling
TAB and Ctrl-TAB have had their actions swapped.
`ESC c' command to capitalise a word
Specifying files on the command line now works
It is now possible to Meta qualify a keypress and it will pretend that you pressed @key{ESC} then the un-Meta'd key.

Version 3.0 (first release since 2.07 back in January '93!)

Scrapped old script language. Replaced by an (almost) standard Lisp system.
Ported to UNIX/X11, but Amigas are still supported.
Much improved redrawing of buffers (it tries harder to only redraw the minimum needed).
Editing modes (included are modes for C, Jade-Lisp and Texinfo) to aid in the editing of certain types of files. For example in c-mode (the mode for editing C source files) the editor will attempt to automatically indent lines the correct amount (although it will occasionally make mistakes).
Lisp module to read Info files with (Info is the GNU way of formatting hypertext manuals). This can be used to read jade's manual from inside the editor.
Online help for functions/variables, etc..
No longer saves preferences to a file, this must be done in Lisp now (or in your .Xdefaults file for X)
Windows are much more flexible in what they show, text files are just a different kind of `buffer'. Any window can display any buffer
Streams. These are a meta-class of Lisp objects which can have stream operations performed on them (ie, read/write). Some objects which can be classed as streams are: buffers, files on disk, strings, user-supplied functions, [book]marks, processes (only in UNIX and only as output streams), etc...
Files can be automatically saved while they are being edited (so that they can be recovered later if necessary)
Scripts (files of Lisp) can be compiled for extra efficiency/speed.
Default keybindings are more Emacs like (in fact, they are totally different from in the last release)
Options such as word-wrap or auto-indent are no longer hardcoded into the editor. Now these have to be done in Lisp.
...