aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc/PG-adapting.texi
diff options
context:
space:
mode:
authorGravatar David Aspinall <da@inf.ed.ac.uk>2008-01-14 23:11:30 +0000
committerGravatar David Aspinall <da@inf.ed.ac.uk>2008-01-14 23:11:30 +0000
commitd243de19ec0e5c57e979a34df0229d7fc02f94a5 (patch)
treef92dc169052ab9fc328f30c252277fd54a119cbc /doc/PG-adapting.texi
parent45de9ccaa454c303fdf2289742583a4fd2f0cd26 (diff)
Remove architecture flags. Remove proof-pre-shell-start and proof-mode-for- settings.
Diffstat (limited to 'doc/PG-adapting.texi')
-rw-r--r--doc/PG-adapting.texi77
1 files changed, 5 insertions, 72 deletions
diff --git a/doc/PG-adapting.texi b/doc/PG-adapting.texi
index 48646bc5..49205796 100644
--- a/doc/PG-adapting.texi
+++ b/doc/PG-adapting.texi
@@ -493,49 +493,9 @@ It's important that each of your modes invokes one of the functions
once it has set its configuration variables. These functions
finalize the configuration of the mode.
-For each mode, there is a configuration variable which names it so that
-Proof General can set buffers to the proper mode, or find buffers in
-that mode. These are documented below, and set like this:
-@lisp
- (setq proof-mode-for-script 'myass-mode)
-@end lisp
-where @code{myass-mode} is your major mode for scripts, derived from
-@code{proof-mode}. You must set these variables before the proof shell
-is started; one way to do this is inside a function which is called from
-the hook @code{pre-shell-start-hook}. See the file @file{demoisa.el}
-for details of how to do this.
-
-For future instantiations, it is recommended to follow the standard
-scheme: @code{@var{PA}-mode}, @code{@var{PA}-shell-mode}, etc.
-
-@c TEXI DOCSTRING MAGIC: proof-mode-for-script
-@defvar proof-mode-for-script
-Mode for proof script buffers.@*
-This is used by Proof General to find out which buffers
-contain proof scripts.
-The regular name for this is <PA>-mode. If you use any of the
-convenience macros Proof General provides for defining commands
-etc, then you should stick to this name.
-Suggestion: this can be set in the script mode configuration.
-@end defvar
-@c TEXI DOCSTRING MAGIC: proof-mode-for-shell
-@defvar proof-mode-for-shell
-Mode for proof shell buffers.@*
-Usually customised for specific prover.
-Suggestion: this can be set a function called by @samp{@code{proof-pre-shell-start-hook}}.
-@end defvar
-@c TEXI DOCSTRING MAGIC: proof-mode-for-response
-@defvar proof-mode-for-response
-Mode for proof response buffer (and trace buffer, if used).@*
-Usually customised for specific prover.
-Suggestion: this can be set a function called by @samp{@code{proof-pre-shell-start-hook}}.
-@end defvar
-@c TEXI DOCSTRING MAGIC: proof-mode-for-goals
-@defvar proof-mode-for-goals
-Mode for proof state display buffers.@*
-Usually customised for specific prover.
-Suggestion: this can be set a function called by @samp{@code{proof-pre-shell-start-hook}}.
-@end defvar
+The modes must be named standardly, replacing @code{proof-} with the
+prover's symbol name, @code{@var{PA}-}. See the file @file{demoisa.el}
+for an example of the four calls to @code{define-derived-mode}.
@node Menus and Toolbar and User-level Commands
@chapter Menus, toolbar, and user-level commands
@@ -1987,22 +1947,6 @@ So we select pipes by default if it seems like we're on Solaris.
We do not force pipes everywhere because this risks loss of data.
@end defvar
-@c TEXI DOCSTRING MAGIC: proof-pre-shell-start-hook
-@defvar proof-pre-shell-start-hook
-Hooks run before proof shell is started.@*
-Suggestion: set this to a function which configures just these proof
-shell variables:
-@lisp
- @code{proof-prog-name}
- @code{proof-mode-for-shell}
- @code{proof-mode-for-response}
- @code{proof-mode-for-goals}
- @code{proof-shell-trace-output-regexp}
-@end lisp
-This is the bare minimum needed to get a shell buffer and
-its friends configured in the function @code{proof-shell-start}.
-@end defvar
-
@c TEXI DOCSTRING MAGIC: proof-shell-handle-error-or-interrupt-hook
@defvar proof-shell-handle-error-or-interrupt-hook
Run after an error or interrupt has been reported in the response buffer.@*
@@ -2098,7 +2042,7 @@ the end of the concrete syntax is indicated by @code{pg-subterm-end-char}.
If @samp{@code{pg-subterm-start-char}} is nil, subterm markup is disabled.
-See doc of @samp{@code{pg-goals-analyse-structure}} for more details of
+See doc of @samp{@code{pg-assoc-analyse-structure}} for more details of
subterm and proof-by-pointing markup mechanisms..
@end defvar
@c TEXI DOCSTRING MAGIC: pg-subterm-sep-char
@@ -2630,23 +2574,12 @@ a menu entry, for example. The default value is the string
@node Useful variables
@section Useful variables
-In @file{proof-site}, several architecture flags are defined. These
+In @file{proof-site}, some architecture flags are defined. These
can be used to write conditional pieces of code for different Emacs
and operating systems. They are referred to mainly in
@file{proof-compat} (which helps to keep the architecture and version
dependent code in one place).
-
-@c TEXI DOCSTRING MAGIC: proof-running-on-Emacs21
-@defvar proof-running-on-Emacs21
-Non-nil if Proof General is running on GNU Emacs 21 or later.
-@end defvar
-
-@c TEXI DOCSTRING MAGIC: proof-running-on-XEmacs
-@defvar proof-running-on-XEmacs
-Non-nil if Proof General is running on XEmacs.
-@end defvar
-
@c TEXI DOCSTRING MAGIC: proof-running-on-win32
@defvar proof-running-on-win32
Non-nil if Proof General is running on a win32 system.