Mercurial > octave-nkf

comparison liboctave/pathsearch.cc @ 3833:f3278ec3ccb7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[project @ 2001-05-17 12:31:52 by jwe]
author jwe
date Thu, 17 May 2001 12:31:52 +0000
parents 5a2c5361dbf1
children 414e694c9e6a
comparison
equal deleted inserted replaced
3832:39aee8115584 3833:f3278ec3ccb7
27 #include <cstdlib> 27 #include <cstdlib>
28 28
29 #include <string> 29 #include <string>
30 30
31 #include "lo-utils.h" 31 #include "lo-utils.h"
32 #include "oct-env.h"
32 #include "oct-kpse.h" 33 #include "oct-kpse.h"
33 #include "pathsearch.h" 34 #include "pathsearch.h"
34 #include "str-vec.h" 35 #include "str-vec.h"
35 #include "str-vec.h" 36 #include "str-vec.h"
36 37
134 135
135 void 136 void
136 dir_path::set_program_name (const std::string& nm) 137 dir_path::set_program_name (const std::string& nm)
137 { 138 {
138 ::octave_kpse_set_progname (nm.c_str ()); 139 ::octave_kpse_set_progname (nm.c_str ());
140
141 // Calling kpse_set_progname has the unfortunate side-effect of
142 // exporting the following variables. We make them empty here so
143 // that they will not interfere with TeX, if it is run as a
144 // subprocess of Octave.
145 //
146 // XXX FIXME XXX -- is there a reasonable way to actually remove
147 // them from the environment?
148
149 octave_env::putenv ("SELFAUTOLOC", "");
150 octave_env::putenv ("SELFAUTODIR", "");
151 octave_env::putenv ("SELFAUTOPARENT", "");
152 octave_env::putenv ("TEXMFDBS", "");
139 } 153 }
140 154
141 void 155 void
142 dir_path::init (void) 156 dir_path::init (void)
143 { 157 {