The best way to set up the system to use vedemacs is to
make yourself a "vedinit.p" file in your home directory.
This is a POP-11 file (having the extension ".p"). In
that file you should put the line
uses vedemacs;
This will ensure that vedemacs, which is a POP-11 program
that customises VED by redoing key-bindings and adding a
few facilities, is loaded every time you start up Poplog.
I would also recommend that you rebind vedautowrite:
50->vedautowrite;
or make use of ved_autosave.
You can further customise your system by using the
"define key" capability of VED. See HELP DK. Note that
vedemacs is not a full emulation of emacs. The differences
will no doubt irritate you, but I trust you can live
with them.
The best way for a beginner to use Poplog to work
on LISP under X is to read a LISP file into a VED
buffer and use the "Compile" menu to load all
or part of the file. Note that VED, unlike Emacs
decides what language a file is written in purely
by the file extension. ".lsp" certainly works,
and I believe that ".lisp" is generally acceptable.
Note that the "@" character has a special meaning
in clisp, namely to provide access to POP-11 variable
bindings. You may have to put:
(set-syntax-from-char #\@ #\a)
in your init.lsp file if your programs use "@" as a part of
an identifier. Incidentally, there's no difference between
compiling and interpreting in Poplog's clisp. All code is
compiled always.
Finally you should note that there's a difference in computational
model between the use of VED and Emacs for developing programs.
Emacs normally interacts with a language system that is running as
a separate process, while VED interacts with language systems
(POP-11, LISP, Prolog, SML) which are running within the
same process. So the VED-clisp relationship is more like
the relationship between Emacs and Emacs-lisp.
And finally - I find the "immediate mode" (<enter> im) capability
of VED to be handy.
Robin
|