5 Feb 00:02
WinExe on UNC Paths
Les Bell <lesbell <at> lesbell.com.au>
2010-02-04 23:02:25 GMT
2010-02-04 23:02:25 GMT
I'm using GLE (http://glx.sourceforge.net/) to graph some data and save in .eps format for incorporation into LaTeX documents. In order to integrate it into WinEdt, I'm using Emilio Torres's macro, GleExecute.edt, (from http://glx.sourceforge.net/downloads/downloads.html). However, it failed when I tried to run it on some of my data, and after a bit of debugging effort (I'm completely new to WinEdt macros) I discovered that WinExe doesn't seem to like UNC (Uniform Naming Convention) network share names. Modifying the WinExe Properties flags to turn off "Detached process" and "Run in the background", I get a CMD.EXE window with the following message File not found: 'exp0.gle' '\\Fulbert\les\Macquarie\Writings\Dynamics of Bayesian Trust Models' CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. Press any key to continue . . . Opening my .gle file as 'H:\Macquarie\Writings\Dynamics of Bayesian Trust Models\exp0.gle', the macro works fine. I expect the problem is with the Directory parameter However, I noticed that my .tex files are opened using UNC pathnames, and LaTex, pdfLaTeX, etc. all work fine. Examining the LaTeX.edt macro, I'm not seeing anything different that allows the WinExe call in it to work on UNC pathnames, while the one in GleExecute.edt fails. The original code is LetReg(3, 'c:\Program Files\Gle4\bin\gle.exe "%n.gle"'); [...] WinExe('','%!3 ',> '%p','Gle ...',011110,1,'','%p\%n.log',''); although I've currently modified it to: WinExe('','%!3','%P','Gle ...',00000110,1,'','%p\%n.log','%p\%n.log',11); while debugging. What's the secret to getting WinExe to work with UNC pathnames? Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144
RSS Feed