Fix documentation from ')help edit', and running ')edit'
without arguments.

- Qian

diff --git a/src/doc/htex/ug16.htex b/src/doc/htex/ug16.htex
index 98b7dd44..d5a67a43 100644
--- a/src/doc/htex/ug16.htex
+++ b/src/doc/htex/ug16.htex
@@ -870,17 +870,15 @@ Thus
 will place  you in an editor looking at the  file
 {\tt /u/julius/matrix.input}.
 \index{editing files}
-By default, the editor is {\tt vi},
-\index{vi}
-but if you have an EDITOR shell environment variable defined, that editor
-will be used.
+By default, the editor is {\tt less} just for viewing purpose,
+but if you have a shell environment variable FRICASEDITOR defined,
+that editor will be used.
 When \Language{} is running under the X Window System,
 it will try to open a separate {\tt xterm} running your editor if
 it thinks one is necessary.
-\index{Korn shell}
-For example, under the Korn shell, if you issue
+For example, under the Bash shell, if you issue
 \begin{verbatim}
-export EDITOR=emacs
+export FRICASEDITOR=emacs
 \end{verbatim}
 then the emacs
 \index{emacs}
diff --git a/src/interp/i-toplev.boot b/src/interp/i-toplev.boot
index 6aaa8e55..91fea454 100644
--- a/src/interp/i-toplev.boot
+++ b/src/interp/i-toplev.boot
@@ -108,11 +108,11 @@ readSpadProfileIfThere() ==
   file := getEnv('"FRICAS_INITFILE")
   file = '"" => nil
   efile :=
-    make_input_filename(file) => file
+    fn := make_input_filename(file) => fn
     file := ['_.fricas, 'input]
-    make_input_filename(file) => file
+    fn := make_input_filename(file) => fn
     file := ['_.axiom, 'input]
-    make_input_filename(file) => file
+    fn := make_input_filename(file) => fn
     NIL
   efile =>
     $edit_file := efile

--
You received this message because you are subscribed to the Google Groups "FriCAS - 
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/fricas-devel/79c96039-53bf-4974-aba4-cc7ad2bcfcfa%40gmail.com.

Reply via email to