From: Peter Graves <peter@ar...> - 2002-07-11 18:24:33
This morning's 0.15.3+ development snapshot is up:
http://armedbear.org/j-jar.zip (just j.jar)
By request, this snapshot adds support for custom keyword lists for
the various modes.
This feature is mainly useful for languages like Lisp and Scheme that
have a variety of dialects, where you might want to use a custom
keyword list that contains the keywords of the particular dialect
To use a custom keyword list, first prepare the list itself. It should
be an ordinary text file with one keyword per line. For an example of
the format, take a look at src/org/armedbear/j/JavaMode.keywords
(there is such a file for each mode, containing the default keyword
list for that mode).
After you have prepared your custom keyword list, add a line like this
to ~/.j/prefs, pointing to the file you want to use:
LispMode.keywords = /home/peter/lispkeywords
With the current snapshot, it's necessary in most cases to restart j
to pick up the new keywords. (Restarting might not be necessary if the
mode in question has not yet been used in the current session.) In the
near future I'll try to fix things so that restarting is not required.
Internally, the foundation is in place for file-specific keyword
lists, so (in theory, at least) you could have several files open at
once using different versions of Lisp and use a different keyword set
for each file. But this part of the feature isn't implemented yet,
since it also depends on some changes that still need to be made in
j's properties architecture, together with a completely different UI
for the Properties dialog (Alt P) and support for embedding file-
specific preferences as comments in the files themselves.
BTW if you're using Lisp and/or Scheme you might want to try one of
the new parenthesis-highlighting preferences:
highlightMatchingBracket = true
or my personal favorite:
highlightBrackets = true
The names of these preferences refer to "brackets", but they apply to
parentheses and braces too; "highlightMatchingBraceBracketOrParenthesis"
was just too long, even for me.
Thanks for your support.