summaryrefslogtreecommitdiff
path: root/Build
diff options
context:
space:
mode:
authorPiotr Strzelczyk <piotr@eps.gda.pl>2011-09-08 07:58:03 +0000
committerPiotr Strzelczyk <piotr@eps.gda.pl>2011-09-08 07:58:03 +0000
commitfcdd2276b91dc500e22d134c31b4ca8c69b737a0 (patch)
tree7c50537f61d5893de754413760ebea7f5dbe4caa /Build
parentb9c987a4b8e70893e054f4fc3df135a3e7a0d46c (diff)
runscript: missing local keyword and some doc tweaks
git-svn-id: svn://tug.org/texlive/trunk@23871 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build')
-rw-r--r--Build/source/texk/texlive/w32_wrapper/readme.txt12
-rw-r--r--Build/source/texk/texlive/w32_wrapper/runscript.tlu14
2 files changed, 11 insertions, 15 deletions
diff --git a/Build/source/texk/texlive/w32_wrapper/readme.txt b/Build/source/texk/texlive/w32_wrapper/readme.txt
index a5b1e530d5f..6f8d7c3eef9 100644
--- a/Build/source/texk/texlive/w32_wrapper/readme.txt
+++ b/Build/source/texk/texlive/w32_wrapper/readme.txt
@@ -18,8 +18,8 @@
The script wrapping machinery is not limited to scripts shipped with
TeX Live. You can also use it for script programs from manually
- installed packages, which should minimize the problems when using
- them with TeX Live.
+ installed packages. This should minimize problems when using them
+ with TeX Live.
First, make sure that there is an interpreter program available on
your system for the script you want to use. Interpreters for Perl
@@ -68,9 +68,7 @@
If you prefer to call the script program simply by its name, copy
and rename bin/win32/runscript.exe to <script-name>.exe and put it
- in bin/win32/ directory of your TeX Live installation or, if you
- don't have the write permissions there, somewhere else on the search
- path.
+ somewhere on the search path.
Wrapper structure
@@ -100,12 +98,12 @@
The launcher script knows, which variant has been used to invoke it
based on the sentinel argument. The lack of this argument means
- that it was invoked in a standard way, i.e. through texlua.exe.
+ that it was invoked in a standard way, i.e., through texlua.exe.
All the hard work of locating a script/program to execute happens
in the launcher script. The located script/program is always
executed directly by spawning its interpreter (or binary) in a new
- process. The system shell (cmd.exe) is never called (except for
+ process. The system shell (cmd.exe) is never called (except for
batch scripts, of course). If the located script happens to be
a (tex)lua script, it is loaded and called internally from within
this script, i.e. no new process is spawned. Execution is done
diff --git a/Build/source/texk/texlive/w32_wrapper/runscript.tlu b/Build/source/texk/texlive/w32_wrapper/runscript.tlu
index 7a47e2685ad..98a4b5d7528 100644
--- a/Build/source/texk/texlive/w32_wrapper/runscript.tlu
+++ b/Build/source/texk/texlive/w32_wrapper/runscript.tlu
@@ -29,8 +29,8 @@ local helpstr = [[
The script wrapping machinery is not limited to scripts shipped with
TeX Live. You can also use it for script programs from manually
- installed packages, which should minimize the problems when using
- them with TeX Live.
+ installed packages. This should minimize problems when using them
+ with TeX Live.
First, make sure that there is an interpreter program available on
your system for the script you want to use. Interpreters for Perl
@@ -79,9 +79,7 @@ local helpstr = [[
If you prefer to call the script program simply by its name, copy
and rename bin/win32/runscript.exe to <script-name>.exe and put it
- in bin/win32/ directory of your TeX Live installation or, if you
- don't have the write permissions there, somewhere else on the search
- path.]]
+ somewhere on the search path.]]
local docstr = [[
@@ -113,12 +111,12 @@ local docstr = [[
The launcher script knows, which variant has been used to invoke it
based on the sentinel argument. The lack of this argument means
- that it was invoked in a standard way, i.e. through texlua.exe.
+ that it was invoked in a standard way, i.e., through texlua.exe.
All the hard work of locating a script/program to execute happens
in the launcher script. The located script/program is always
executed directly by spawning its interpreter (or binary) in a new
- process. The system shell (cmd.exe) is never called (except for
+ process. The system shell (cmd.exe) is never called (except for
batch scripts, of course). If the located script happens to be
a (tex)lua script, it is loaded and called internally from within
this script, i.e. no new process is spawned. Execution is done
@@ -443,7 +441,7 @@ local scripts4tlperl = {
}
local try_extern_perl = (kpse.var_value('TEXLIVE_WINDOWS_TRY_EXTERNAL_PERL') == '1') and
not (guimode or is_restricted_progname or scripts4tlperl[progname])
-PERLEXE = try_extern_perl and search_path('perl.exe', PATH)
+local PERLEXE = try_extern_perl and search_path('perl.exe', PATH)
if not PERLEXE then
PERLEXE = TEXDIR..'/tlpkg/tlperl/bin/perl.exe'
os.setenv('PERL5LIB', TEXDIR..'/tlpkg/tlperl/lib')