On Fri, 24 Feb 2006 19:52:13 -0800, Stephen Harris wrote:

[...] 
>>>                          The Tex Information produces a
>>> window but it contains no information.
>>
>> Yes, I also see this, but then this also happens with 1.3.7.
>>
> 
> Perhaps normal for Cygwin/Linux but you can see all these
> files and their paths with Uwe or Angus native LyXwin. Or
> with Mingw build of LyX1.4.0_pre3. It is how I used to check
> that LyX communicated with Miktex:texmf

Really? It is empty for me with those versions, too, but LyX works
perfectly.

>>> I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.
>>
>> Correct. To see if that works try "ls /c" in a cygwin shell.
>>
> 
> Yes I see lots of my stuff. When I use File->Open it still
> displays the path in terms of /cygdrive/c/ which makes me nervous.

That's strange, indeed. I get "/cygdrive/c" converted to "/c" when I type
it in the text input area in File->Open. Try the following command and
see what output it gives:

  cygpath 'C:\somepath'

Does it says "/cygdrive/c/somepath" or "/c/somepath"?

[...]
>>> The Working directory automatically generated by LyX is
>>> C:/Cygwin/.xemacs
>>
>> Uh? It seems that you have not set the HOME variable. LyX/Cygwin uses
>> HOME instead of USERPROFILE. Perhaps I should patch the sources such
>> that USERPROFILE is used as a fallback if HOME is not set.
>> For the moment, you can fix this by adding the HOME var in the same
>> way you add the PATH var but in the user section. Set HOME to a folder
>> of your choice and then try launching LyX with the option "-dbg init"
>> to see what it thinks your home_dir is.
>>
> 
> I used to have Xemacs for Cygwin installed. I set the HOME variable
> to C:\Cygwin\.xemacs for it. I now have another version of Xemacs set
> to HOME there also so if I change it I have to move init.el files etc.

Ok, you set it that way. No need to change it.

[...]
>> As I noted above, always use posix syntax in path_prefix, so
>> write that as /c/texmf/miktex/bin:/c/reader7/etc
>> The ':' char must only be used as a separator.
>> Please try the following as path_prefix (I am assuming that your
>> AcroRd32.exe is in C:\reader7\Reader\acrord32 and that you issued
>> the "mount -f C: /c" command)
>>
>>
> /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/texmf/miktex/bin:/c/reader7/Reader/ac
> ord32
>>
> 
> Oops. No acrord32 is short for the acrord32.exe I just noticed this
> after trying it and it failed. So I tried :/c/reader7/Reader/ which didn't
> work. I just tried it without the trailing slash /, and it didn't work.

oh... Remember that only directories should be listed in path_prefix.

> I start LyX with an icon linked to C:\cygwin\usr\local\bin\LyX-1.4.0.exe
> and it gives me an error message "Locale en_US could not be set"
> which has never mattered in the past. My language is set to English in LyX.
> The Locale error follows after the "LyX will not be able to produce output."

Yes, this is normal. For some reason en_US is not present in cygwin.

[...]
> I've watched Reconfigure process. It says yes to finding pdflatex
> and acrord32 and gsview32. I don't have any Viewers, no DVI or
> Postscript. I added :/c/gs/gs8.51/bin:/c/ghostgum/gsview to Path
> prefix and turned on Instant Preview. No previewers. Before when
> I had this problem I ran sh configure from lyx/resources/lyx I'll
> give that -dbg init a try before closing. yes my hom_dir is .xemacs
> ctrl-d applied to splash.lyx says "No information for exporting the
> format DVI." Something is causing that 'missing TeX class "article"
> 
> -dbg init partial output [I tried exporting from the LyX command line.]
> ----------------------------------------
> No information for exporting the format DVI.
> Error: Couldn't export file
> ----------------------------------------
> No information for exporting the format DVI.
> Error: Couldn't export file
> ----------------------------------------
> No information for exporting the format LaTeX.
> sh: -c: line 0: syntax error near unexpected token `&'
> sh: -c: line 0: `( /c/texmf/miktex/bin/latex.exe ) <  &'
> Error: Couldn't export file
> ----------------------------------------

Hmmm... I really have no clue to it...

-- 
Enrico



Reply via email to