From 2dad869969276edbe077c7576959a37692e0c12c Mon Sep 17 00:00:00 2001 From: David Aspinall Date: Tue, 27 Oct 1998 12:16:12 +0000 Subject: Priority changes --- todo | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/todo b/todo index 2371f9f6..f51f13d4 100644 --- a/todo +++ b/todo @@ -48,20 +48,6 @@ C byte-compilation: check that byte compilation (and compiled code!) works for both varieties of Emacs. Add instructions to INSTALL on how to byte compile. (1hr) -D proof-site (da): I think it would be nice to change the architecture - to make customization for new provers much easier. - The standard use of 'define-derived-mode' could be invoked - automatically in proof-site, and we could easily get away from the - kludge of proof-config-done and friends. - (Compare this to the way font-lock works automatically for XEmacs - when the right variable name is set, but for FSF Emacs you have - to write something special). - The objection to doing this is based on the idea that we should use - an object-like inheritance mechanism to define the new modes. - But if this is forgone, it might even be possible to add - support for new assistants entirely via the customize mechanism, - without any knowledge of elisp apart from regular expressions! - C Remove .gif, .jpg, .xpm, .xbm files from the CVS repository. Add .cvsignore's for them instead. Disadvantage: developers will need to have the Gimp installed to build them via 'make images' @@ -259,6 +245,20 @@ C Make completion more generic. For Isabelle and Lego, we can build a completion table by querying the process, which is better than messing with tags. +X proof-site (da): I think it would be nice to change the architecture + to make customization for new provers much easier. + The standard use of 'define-derived-mode' could be invoked + automatically in proof-site, and we could easily get away from the + kludge of proof-config-done and friends. + (Compare this to the way font-lock works automatically for XEmacs + when the right variable name is set, but for FSF Emacs you have + to write something special). + The objection to doing this is based on the idea that we should use + an object-like inheritance mechanism to define the new modes. + But if this is forgone, it might even be possible to add + support for new assistants entirely via the customize mechanism, + without any knowledge of elisp apart from regular expressions! + X Support a history of proof commands, with a "redo" command to redo undo-to-point or sequences of toolbar undo's. -- cgit v1.2.3