[posted and mailed]
"Jim Reid" <[EMAIL PROTECTED]> wrote in news:3F0D53F1.31565.A9979
@localhost:
>
> Anyway, dead cat territory,
Best kind. :-) (I'm a dog person.)
> I tried from the command line "lyx -dbg
> 3" and everything works. Himm. However "lyx" behaves the same
> as double clicking the .exe. Making a shortcut with the -dbg 3
> switch also doesn't work (It has read the -dbg 3 switch as the helpful
> shell window appears).
Well, that's unusually peculiar, even by Windows standards. You're
saying that 'lyx -dbg 3' on a command line works (meaning latex runs when
you View->DVI), but lyx on a command line (without the arguments) can't
get latex to run properly?
For the shortcut, did you put the '-dbg 3' on the "target" line of the
shortcut ('path\lyx.exe -dbg 3' all on one line)? And does the shortcut
start in the same directory in which you were opening the command window?
(Not that I think that would account for the systems, but when fishing I
favor a big net.)
The shortcut (with the debug options) behaving differently from the
command line (with debug options) might suggest either a difference in
the environment variables the two are using or a difference in what
account is running the program (assuming you're in a multiuser version of
Windows that cares about user accounts -- I don't think you specified
your OS version), but that would not explain why lyx on the command line
without debug options would fail. The debug options making a difference
on the command line might mean that something is missing (or ignored) in
the environment that is being supplied internally (or paid attention to)
in debug mode, but that wouldn't explain the shortcut failing.
Best bet is probably to ask Ruurd Reitsma about it.
What happens if you make shortcut run a batch file that starts LyX in
debug mode? Any joy on the viewing?
-- Paul
