I've done some thuggery to produce very rough-cut BitC plugins for vim and
for emacs. They are now in the tree.
VIM:
The easiest way to start using the vim plugin is to add the following to
your .vimrc:
set
runtimepath=$HOME/.vim,$HOME/HG/bitc/src/plugins/vim,$VIMRUNTIME,$HOME/.vim/after
filetype plugin on
You'll want to check what the VIM runtime path is on your system, and of
course you'll need to adjust the path to your repository, but the lines
above worked for me.
Caution! I am NOT a vim user, and definitely not a vim plugin expert. What
you're getting is a quick and dirty attempt after a couple of hours with the
vim developer manual. Hopefully, it's enough to bug you into making it
better and more usable.:-)
EMACS:
In your .emacs (again adjusting paths to suit):
(load-file "~/HG/bitc/src/plugins/emacs/bitc-mode/bitc-mode.el")
(setq auto-mode-alist
(append '(("\\.bitc$" . bitc-mode)
("\\.bits$" . bitc-mode))
auto-mode-alist))
(add-hook 'bitc-mode-hook (lambda ()
(auto-fill-mode 1)))
This mode is a good bit more complete, but it has an unbelievable number of
rough edges. Some of what I did may turn out to be clever in the four-letter
sense. Any language that uses indentation for meaning runs afoul of many of
the conventions for emacs programming modes.
Most notably: indent-region is not implemented and will certainly mangle
your code horribly.
I'm rather more experienced as an emacs-lisp hacker, but there is a hell of
a lot of state and interactions between modes to consider in emacs, and I
don't have the time to chase most of that down. This, at least, is a start.
As always, report your experiences, annoyances, and pleasant surprises -
preferably to the mailing list.
Jonathan
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
