Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread Enrico Forestieri
On Tue, Nov 03, 2015 at 08:30:53PM -0500, Richard Heck wrote: > On 11/03/2015 06:38 PM, PhilipPirrip wrote: > >Just curious: what and when executes the code in os_win32.cpp (os_.cpp > >in general). Whatever I did to test the patch, these functions were not > >called. > > The one Enrico modifie

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread Richard Heck
On 11/03/2015 06:38 PM, PhilipPirrip wrote: Just curious: what and when executes the code in os_win32.cpp (os_.cpp in general). Whatever I did to test the patch, these functions were not called. The one Enrico modified is called when you try to view or edit a file that is referenced from

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread PhilipPirrip
Just curious: what and when executes the code in os_win32.cpp (os_.cpp in general). Whatever I did to test the patch, these functions were not called.

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread Scott Kostyshak
On Tue, Nov 03, 2015 at 08:24:49PM +0100, Enrico Forestieri wrote: > On Tue, Nov 03, 2015 at 02:29:32AM -0500, PhilipPirrip wrote: > > On 11/02/2015 03:16 PM, Enrico Forestieri wrote: > > >>>This last observation suggests what is the minimal change to be > > >>>performed, > > >>>i.e., let the late

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread Enrico Forestieri
On Tue, Nov 03, 2015 at 02:29:32AM -0500, PhilipPirrip wrote: > On 11/02/2015 03:16 PM, Enrico Forestieri wrote: > >>>This last observation suggests what is the minimal change to be performed, > >>>i.e., let the latex run work as if the document dir was the current > >>>directory. This means settin

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-03 Thread Stephan Witt
Am 02.11.2015 um 16:44 schrieb Enrico Forestieri : > On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > >> Hi Enrico, thank you for your response. I hope the others will help us >> resolve this too. > > Given the overwhelming amount of replies, I doubt anyone is interested > in thi

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-02 Thread PhilipPirrip
On 11/02/2015 03:16 PM, Enrico Forestieri wrote: This last observation suggests what is the minimal change to be performed, i.e., let the latex run work as if the document dir was the current directory. This means setting the relevant environment variables such that the document dir is also scann

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-02 Thread Scott Kostyshak
On Mon, Nov 02, 2015 at 09:16:41PM +0100, Enrico Forestieri wrote: > On Mon, Nov 02, 2015 at 12:26:36PM -0500, PhilipPirrip wrote: > > > On 11/02/2015 10:44 AM, Enrico Forestieri wrote: > > >On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > > > > > >>Hi Enrico, thank you for your re

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-02 Thread Enrico Forestieri
On Mon, Nov 02, 2015 at 12:26:36PM -0500, PhilipPirrip wrote: > On 11/02/2015 10:44 AM, Enrico Forestieri wrote: > >On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > > > >>Hi Enrico, thank you for your response. I hope the others will help us > >>resolve this too. > > > >Given the o

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-02 Thread PhilipPirrip
On 11/02/2015 10:44 AM, Enrico Forestieri wrote: On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: Hi Enrico, thank you for your response. I hope the others will help us resolve this too. Given the overwhelming amount of replies, I doubt anyone is interested in this matter. Oh

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-02 Thread Enrico Forestieri
On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > Hi Enrico, thank you for your response. I hope the others will help us > resolve this too. Given the overwhelming amount of replies, I doubt anyone is interested in this matter. > I'd rather call this a bug in the script than in se

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-01 Thread Scott Kostyshak
On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > > I hope you all (developers) understand we're grateful users who are paying > it forward by helping you (or trying ourselves to) make LyX better. I don't think there's any doubt about this. Thank you for your time and effort, Philip

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-01 Thread PhilipPirrip
Hi Enrico, thank you for your response. I hope the others will help us resolve this too. I propose another simple test, it will show you that env variables do get set by setProcessEnvironment(). Attaching the modified files. Hope you'll trust me now ;) There is nothing to trust but somethin

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-11-01 Thread PhilipPirrip
Hi Enrico, thank you for your response. I hope the others will help us resolve this too. I propose another simple test, it will show you that env variables do get set by setProcessEnvironment(). Attaching the modified files. Hope you'll trust me now ;) There is nothing to trust but somethin

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-10-31 Thread Enrico Forestieri
On Thu, Oct 29, 2015 at 09:36:24PM -0400, PhilipPirrip wrote: > Thanks for responding, Enrico. I appreciate it! > > > >I am sorry, but it still doesn't work. > >As you can see, now it doesn't work because setProcessEnvironment() is used. > > I don't understand what that script (myprog) is exact

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-10-29 Thread PhilipPirrip
Thanks for responding, Enrico. I appreciate it! I am sorry, but it still doesn't work. As you can see, now it doesn't work because setProcessEnvironment() is used. I don't understand what that script (myprog) is exactly supposed to do, but I believe the problem is in it rather than setProces

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-10-29 Thread PhilipPirrip
Thanks for responding, Enrico. I appreciate it! I am sorry, but it still doesn't work. As you can see, now it doesn't work because setProcessEnvironment() is used. I don't understand what that script (myprog) is exactly supposed to do, but I believe the problem is in it rather than setProces

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

2015-10-29 Thread Enrico Forestieri
On Wed, Oct 28, 2015 at 08:12:44PM -0400, PhilipPirrip wrote: > I've been playing with SystemcallPrivate::startProcess (in Systemcall.cpp) > and latexEnvCmdPrefix (in filetools.cpp), in an attempt to resolve the issue > with missing BIBINPUTS, a 9 year old request at > http://www.lyx.org/trac/ticke