From: Peter Graves <peter@ar...> - 2002-09-23 02:39:15
Tonight's 0.16.4+ development snapshot is up:
http://armedbear.org/j.zip (source and documentation)
http://armedbear.org/j-jar.zip (just j.jar)
I'm tempted to call this a release candidate for 0.17.0, but you never
I've reworked the register stuff a bit.
1. Register names are now limited to lower case letters, a-z. The
other naming possibilities are reserved for other features in the
2. The command "copyToRegister" has been renamed "saveToRegister".
Among other things, "saveToRegister" hints at the persistent
nature of j's registers.
3. As an experiment, I've introduced the concept of command
abbreviations. In particular, saveToRegister can be invoked as
"sr", insertRegister as "ir", and listRegisters as "lr".
So now you can do, for example, Alt X, "ir c" to insert register
"c" at the current location of the caret.
The rationale is, the abbreviations don't eat much, they're not
too hard to remember (at least the ones I've defined so far), and
we're running out of sane default key mappings.
The command abbreviation experiment may not work out in the end,
although at the moment I don't see why it wouldn't. Let me know if
you have any thoughts on the subject.
4. The listRegisters buffer now updates automatically after you do
clearRegister or saveToRegister. (It should also update
automatically after you do editRegister and save your changes, but
that functionality isn't there yet. Tomorrow is another day.)
In addition, the JPDA debugger (Alt X, "jdb") has improved a bit:
1. The "locals" command calls toString() (in effect) on the
variables it displays, for more informative output.
2. The "print" and "locals" commands now display all the elements
3. There's now a "restart" command, which does what its name
suggests, to save you the bother of closing the jdb control dialog
and re-invoking jdb.
4. The initial dialog does a bit of sanity checking on the class
path and source path, so if you specify a path that doesn't exist,
you'll be given a timely opportunity to correct your mistake.
Unfortunately there's still no documentation for jdb, but other than
that (and its current inability to attach to an already-running
process), jdb is almost at the point where it will become an official
feature. I use it every day, myself.
Thanks for your support.