# HG changeset patch # User wenzelm # Date 1456423728 -3600 # Node ID 62c03eb38e49636f30555abea3d6cf89470f0c8b # Parent 1abd90afe3871e950a69d9cf8c8a892488214c5e isabelle_scala_script is usually found by PATH; diff -r 1abd90afe387 -r 62c03eb38e49 NEWS --- a/NEWS Thu Feb 25 18:08:23 2016 +0100 +++ b/NEWS Thu Feb 25 19:08:48 2016 +0100 @@ -156,6 +156,10 @@ *** System *** +* The Isabelle system environment always ensures that the main +executables are found within the PATH: isabelle, isabelle_process, +isabelle_scala_script. + * SML/NJ is no longer supported. diff -r 1abd90afe387 -r 62c03eb38e49 src/Doc/System/Scala.thy --- a/src/Doc/System/Scala.thy Thu Feb 25 18:08:23 2016 +0100 +++ b/src/Doc/System/Scala.thy Thu Feb 25 19:08:48 2016 +0100 @@ -77,11 +77,7 @@ text \ The executable @{executable "$ISABELLE_HOME/bin/isabelle_scala_script"} allows to run Isabelle/Scala source files stand-alone programs, by using a - suitable ``hash-bang'' line and executable file permissions. - - The subsequent example assumes that the main Isabelle binaries have been - installed in some directory that is included in @{setting PATH} (see also - @{tool "install"}): + suitable ``hash-bang'' line and executable file permissions. For example: @{verbatim [display] \#!/usr/bin/env isabelle_scala_script @@ -89,8 +85,12 @@ Console.println("browser_info = " + options.bool("browser_info")) Console.println("document = " + options.string("document"))\} - Alternatively the full @{file "$ISABELLE_HOME/bin/isabelle_scala_script"} - may be specified in expanded form. + This assumes that the executable may be found via the @{setting PATH} from + the process environment: this is the case when Isabelle settings are active, + e.g.\ in the context of the main Isabelle tool wrapper + \secref{sec:isabelle-tool}. Alternatively, the full @{file + "$ISABELLE_HOME/bin/isabelle_scala_script"} may be specified in expanded + form. \ end