> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> What about the case when LyX is being run from the build
Angus> directory? In such a case, adding the directory containing the
Angus> LyX binary to the PATH is pointless. How about:
[snip]
Yes, this seems very good.
Angus> It'll b
Jean-Marc Lasgouttes wrote:
> Angus> Both Lars and you seem to be arguing that we shouldn't have a
> Angus> LyXRC::path_prefix variable. I fail to see why this suggestion
> Angus> is generating so much discussion. It's simple and it'll work.
>
> No, I am arguing that, besides this path_prefix vari
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Both Lars and you seem to be arguing that we shouldn't have a
Angus> LyXRC::path_prefix variable. I fail to see why this suggestion
Angus> is generating so much discussion. It's simple and it'll work.
No, I am arguing that, besides
Jean-Marc Lasgouttes wrote:
> Angus> To recap, on Windows we attempt to execute the lib/configure
> Angus> script as system("start /min sh /configure");
> Angus> which fails because J:\MinSys\bin isn't in the cmd.exe's path.
>
> And is it supposed to be in there with a proper installation? I see
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> To recap, on Windows we attempt to execute the lib/configure
Angus> script as system("start /min sh /configure");
Angus> which fails because J:\MinSys\bin isn't in the cmd.exe's path.
And is it supposed to be in there with a proper
Jose' Matos wrote:
>> Incidentally, José, I understand that Windows users are having
>> difficulty launching lyx2lyx because it doesn't have a ".py" extension
>> and because Windows doesn't search the first line of the script for
>> "#! /bin/env python"
>
> What do you suggest?
Invoke lyx2lyx a
On Friday 07 January 2005 20:15, Angus Leeming wrote:
>
> Ok, that's reasonable too. Do we need PYTHON_PATH as well, for lyx2lyx?
>
> Incidentally, José, I understand that Windows users are having difficulty
> launching lyx2lyx because it doesn't have a ".py" extension and because
> Windows doesn't
Lars Gullik Bjønnes wrote:
> | To recap, on Windows we attempt to execute the lib/configure script as
> | system("start /min sh /configure");
>
> coudn't we just call
>
> system("start /min J:\MinSys\bin/sh lyxdir>/configure");
>
> ??
>
> Where "J:\MinSys\bin\sh
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
There is also the option of not altering the PATH at all and just call
teh binary with a full path.
>>>
>> | Sure, but that won't help me find sh.exe if LyX is installed at
>> | C:\Program Files\LyX\bin and sh.exe is
Lars Gullik Bjønnes wrote:
>>> There is also the option of not altering the PATH at all and just call
>>> teh binary with a full path.
>>
> | Sure, but that won't help me find sh.exe if LyX is installed at
> | C:\Program Files\LyX\bin and sh.exe is in J:\MinSys\bin
>>
> | I do think that a LyXRC va
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
Rather than hard-code these weird and wonderful additions to PATH, why
don't we define a new LyXRC variable "path_prefix" which will be
prepended to the existing PATH variable when LyX is initialised.
>>>
>> | Wh
Lars Gullik Bjønnes wrote:
>>> Rather than hard-code these weird and wonderful additions to PATH, why
>>> don't we define a new LyXRC variable "path_prefix" which will be
>>> prepended to the existing PATH variable when LyX is initialised.
>>
> | Why not require that people set PATH correctly? I fa
Georg Baum <[EMAIL PROTECTED]> writes:
| Angus Leeming wrote:
>
>> Rather than hard-code these weird and wonderful additions to PATH, why
>> don't we define a new LyXRC variable "path_prefix" which will be prepended
>> to the existing PATH variable when LyX is initialised.
>
| Why not require that
Angus Leeming wrote:
> At the moment, Mac users have their PATH modified so:
>
> string oldpath = GetEnv("PATH");
> string newpath = "PATH=" + oldpath + ":" + binpath + ":";
> newpath +=
>
"/sw/bin:/usr/local/bin:/usr/local/teTeX/bin/powerpc-apple-darwin-current";
> PutEnv(newpath);
> lyxerr
Georg Baum wrote:
>> Rather than hard-code these weird and wonderful additions to PATH, why
>> don't we define a new LyXRC variable "path_prefix" which will be
>> prepended to the existing PATH variable when LyX is initialised.
>
> Why not require that people set PATH correctly? I fail to see why
On Jan 7, 2005, at 10:39 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On Dec 10, 2004, at 9:49 AM, Jean-Marc Lasgouttes wrote:
However, a possibility would be to remove all this special code for
LyX/Mac in the startup code, and replace it with setti
Angus Leeming wrote:
> Rather than hard-code these weird and wonderful additions to PATH, why
> don't we define a new LyXRC variable "path_prefix" which will be prepended
> to the existing PATH variable when LyX is initialised.
Why not require that people set PATH correctly? I fail to see why set
Jean-Marc Lasgouttes wrote:
> Bennett, I never answered to this message because Angus was busy
> butchering the init process at the same time... Nevertheless, the
> scripts are sound. I propose we return to that when Angus' work has
> landed.
>
> Angus, do you think that we should unconditionally
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On Dec 10, 2004, at 9:49 AM, Jean-Marc Lasgouttes wrote:
>> However, a possibility would be to remove all this special code for
>> LyX/Mac in the startup code, and replace it with setting user- and
>> lyx-dir from the script.
Be
On Dec 10, 2004, at 9:49 AM, Jean-Marc Lasgouttes wrote:
However, a possibility would be to remove all this special code for
LyX/Mac in the startup code, and replace it with setting user- and
lyx-dir from the script.
I've done this -- or at least tried to. (I'm not sure if I've cleaned
up lyx_main
On Dec 8, 2004, at 12:20 PM, Jean-Marc Lasgouttes wrote:
In 1.3.x, it is in LyX::init, where you find around line 398 of
lyx_main.C
string oldpath = GetEnv("PATH");
string newpath = "PATH=" + oldpath + ":" + binpath + ":";
newpath +=
"/sw/bin:/usr/local/bin:/usr/local/teTeX/bin/powerpc-appl
On Dec 9, 2004, at 8:51 AM, Jean-Marc Lasgouttes wrote:
I suspect that gcc 3.x should now compile lyx 1.3.x. I have removed
all reference to pragma interface/implementation which were a problem
with gcc/cygwin, so you may want to give it a try.
I've tried it, and it doesn't work, giving what I vagu
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Well, it's not simply an issue with Qt. I use Qt 3.3.3 for
Bennett> both LyX 1.4.0 and 1.3.x (though compiled with gcc-3.3 and
Bennett> 2.98, respectively since gcc-3.x doesn't compile LyX 1.3.x on
Bennett> the Mac). And using th
On Dec 8, 2004, at 4:02 PM, Andreas Vox wrote:
Jean-Marc writes:
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On the other hand, although LyX 1.4.0 can be started from the
Bennett> command line, it remains in the background and refuses to
Bennett> take focus; hence straightf
Jean-Marc writes:
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On the other hand, although LyX 1.4.0 can be started from the
Bennett> command line, it remains in the background and refuses to
Bennett> take focus; hence straightforward debugging is pretty much
Bennett> imposs
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> On the other hand, although LyX 1.4.0 can be started from the
Bennett> command line, it remains in the background and refuses to
Bennett> take focus; hence straightforward debugging is pretty much
Bennett> impossible as it is. (C
On Nov 16, 2004, at 1:21 PM, Ronald Florence wrote:
Jean-Marc Lasgouttes wrote:
It seems that it is possible to set environment variables (like PATH
maybe) of an application in its info.plist, using the LSElement key,
as described here:
http://developer.apple.com/documentation/MacOSX/Conceptual/
B
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> This is a very good idea, with only one "gotcha" that I could
Ronald> see:
Ronald> "These environment variables are set only for applications
Ronald> launched through Launch Services. If you run your executable
Ronald> directly
Jean-Marc Lasgouttes wrote:
It seems that it is possible to set environment variables (like PATH
maybe) of an application in its info.plist, using the LSElement key,
as described here:
http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Concepts/EnvironmentVars.html
http://de
Bennett,
It seems that it is possible to set environment variables (like PATH
maybe) of an application in its info.plist, using the LSElement key,
as described here:
http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Concepts/EnvironmentVars.html
http://developer.apple.com
30 matches
Mail list logo
