Install a txrlisp hard link.

* Makefile (LN): New variable. On platforms where
you can't hard link, this can be replaced with some
other command. Possibly "true" not to have the alternative
executable name created at all.
(HARDLINK): New macro.
(install): Use HARDLINK to create a link named txrlisp
pointing to the same file as txr in the destination
directory.

* txr.c (txr_main): If the executable ends with "lisp"
(or "lisp.exe" on Windows), then default the txr_lisp_p
variable to t, which has the effect as if --lisp had
been processed.

* txr.1: Documented.

1 files changed, 27 insertions, 0 deletions

diff --git a/txr.1 b/txr.1
index 09312ed2..b90aade3 100644
--- a/txr.1
+++ b/txr.1
@@ -501,6 +501,17 @@ description of this mode.  When \*(TX enters interactive mode this
 way, it prints a one-line banner announcing the program name and version,
 and one line of help text instructing the user how to exit.
 
+If \*(TX is invoked under the name
+.codn txrlisp ,
+it behaves as if the
+.code --lisp
+option had been specified before any other option.
+Similarly, if \*(TX is invoked under the name
+.codn txrvm ,
+it behaves as if the
+.code --compiled
+option had been given.
+
 Unless the
 .code -c
 or
@@ -88685,6 +88696,22 @@ directory is a direct subdirectory of the executable directory.
 If one of these structures is not observed, the application
 may fail due to the failure of a library file to load.
 
+If the executable discovers that its name ends in the suffix
+.str lisp
+(or else
+.str lisp.exe
+on the MS Windows platform) then the behavior is as if the
+.code --lisp
+command line option had been given.
+Similarly, if the executable finds that its name ends in
+.str vm
+(or
+.str vm.exe
+on MS Windows)
+it behaves as if the
+.code --compiled
+option had been given.
+
 .coSS Function @ save-exe
 .synb
 .mets (save-exe < path << arg-string )