diff options
author | 2006-04-26 22:33:54 +0000 | |
---|---|---|
committer | 2006-04-26 22:33:54 +0000 | |
commit | d74950e260914b56787138cca662ada9170533d8 (patch) | |
tree | 16a9f9fc6aebc8c4111ec0c70ab11fca4c6b40d7 /doc | |
parent | 8ba99b2013e0f62c9117fc79364630ff1fbec585 (diff) |
Modified documentation abou file variables to be compliant with new
xxx-prog-args variabel.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/ProofGeneral.texi | 22 |
1 files changed, 14 insertions, 8 deletions
diff --git a/doc/ProofGeneral.texi b/doc/ProofGeneral.texi index 144525f7..c87f855b 100644 --- a/doc/ProofGeneral.texi +++ b/doc/ProofGeneral.texi @@ -3134,7 +3134,7 @@ when a file is loaded. Those values are written as a list at the end of the file. For example, in projects involving multiple directories, it is often -useful to set the variables @code{proof-prog-name} and +useful to set the variables @code{proof-prog-name}, @code{proof-prog-args} and @code{compile-command} for each file. Here is an example for Coq users: for the file @file{.../dir/bar/foo.v}, if you want Coq to be started with the path @code{.../dir/theories/} added in the libraries path @@ -3142,27 +3142,32 @@ with the path @code{.../dir/theories/} added in the libraries path @lisp (* - Local Variables: - coq-prog-name: "coqtop -emacs -I ../theories" - End: +*** Local Variables: *** +*** coq-prog-name: "coqtop" *** +*** coq-prog-args: ("-emacs" "-I" "../theories") *** +*** End: *** *) @end lisp That way the good command is called when the scripting starts in -@file{foo.v}. Notice that the command argument @code{"-I ../theories"} +@file{foo.v}. Notice that the command argument @code{"-I" "../theories"} is specific to the file @file{foo.v}, and thus if you set it via the configuration tool, you will need to do it each time you load this file. On the contrary with this method, Emacs will do this operation -automatically when loading this file. +automatically when loading this file. Please notice that all the strings +above should never contain spaces see documentation of variables +@code{proof-prog-name} and @code{proof-prog-args}. Extending the previous example, if the makefile for @file{foo.v} is located in directory @file{.../dir/}, you can add the right compile -command: +command. And if you want a non standard coq executable to be used, here +is what you should put in variables: @lisp (* Local Variables: - coq-prog-name: "coqtop -emacs -full -I ../theories" + coq-prog-name: "../../coqsrc/bin/coqtop" + coq-prog-args: "-emacs" "-I" "../theories" compile-command: "make -C .. -k bar/foo.vo" End: *) @@ -3176,6 +3181,7 @@ any other buffer local variable. @inforef{File Variables, + @node Using abbreviations @section Using abbreviations |