Stephen, Haven't used ghostcript from within LyX, so this might be another thing that is broken.
Ya, I had the missing layout problem also. Was able to fix that, I think that updating the path environment variable and rerunning ./configure was what fixed that. >SH: Under File formats->DVI->Viewer->Yap >You want xdvi to be there. If I have a problem I use >the absolute path. But I've seen it recommended to add >the helper app to Paths->Path prefix >You should have several entries generated there, mine reads >/usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/Imagemagick/:/c/texmf/miktex/bin >:/c/reader7/Reader:/c/gs/gs8.51/bin/:/c/ghostgum/gsview (in one line) Don't fully understand. In the "File formats" usder the DVI format, I have a "Viewer" field, but I don't know what you mean by "Viewer->Yap". Later: Made some significant progress. Seemed to be principally using the Edit->Reconfigure which I hadn't noticed before. Have the conversion menu items now, some of which work. What I learned: 1) I am running the Win32 version of LyX. 2) The paths in Edit->Preferences need to be in Windows format. 3) Not all of the Cygwin helpers launch correctly from WinLyX (yet). Will experiment more on this. Actually LyX is working much better now. I wasn't getting WYSIWYG, so had to do the DVI - LaTeX - xdvi thing to see fomatted view. Also getting TOC's now. I was able to get PDF view working by hacking Adobe Reader in as one of the viewers. xdvi doesn't launch correctly at this time, and trying to launch gv causes an illegal instruction exception. I will try to put together a how-to when (if) I get this working. Thanks for the help. Chuck If self-replicating chemicals had as hard a time reaching maturity as good ideas, this planet would still be lifeless. Robert Qualkinbush "Stephen Harris" <[EMAIL PROTECTED]> 03/12/2006 03:34 AM To Charles Schulz/Watson/[EMAIL PROTECTED] cc <[email protected]> Subject Re: No VIEW->DVI in LyX Win32 Hello Charles, I'm going to put replies interspersed within your post. ----- Original Message ----- From: "Charles Schulz" <[EMAIL PROTECTED]> To: "Stephen Harris" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Saturday, March 11, 2006 9:00 PM Subject: Re: No VIEW->DVI in LyX Win32 > Stephen, > > Once again thanks for continuing the conversation. The LyX I'm using is > installed by 'lyx-1.3.7 win32 setup v2.exe' which I got from the binaries > directory on the French LyX mirror (ftp://ftp.lip6.fr/pub/lyx/). I > followed the install wizard except, as I stated before, when the wizard > wanted to get some support package (LaTeX, Python, etc.) I had cygwin > install the equivalent package and pointed the wizard to that binary. > After resolving all the missing pieces according to the wizard, the > installation seemed to go flawlessly and LyX came right up. I have only > run across two issues: > 1) The cygwin X11 binary directory wasn't on my XP environment path so LyX > wasn't able to find X11 graphics dlls for displaying embedded images. > Adding the path to the XP environment and redoing ./configure in > Resources/lyx solved this problem nicely. > 2) The View/DVI menu entry is missing. > ---------------------------------------------------------------- SH: I'm a bit surprised that this worked so well. However, Enricos's build allowed using Tetex instead of the native Windows Miktex. Anyway I may be able to test some of this. You have no problem with ghostscript? Here is a list of my Viewers: DVI, PDF (dvipdfm), PDF (pdflatex), PDF (ps2pdf), Postscript. When my Latex install has been wrong, when I open splash.lyx I got got an error messasge about 'missing article.cls, LyX will not be able to convert', and there will be no DVI viewer. Since you did not report this error message, it is more likely that the script which builds your Viewers or converters is not working right. Under LyX->Edit-> Preferences->File formats->Viewer->/c/ghostgum/gsview/gsview32 Sometimes the Viewers or File formats are blank or not the right one. In this example I used the absolute path. Cygwin would need a /cygdrive but I got a tip from Enrico: ------ "I see that you use /cygdrive/c to access drive C:. If you issue the following command (you need to do it only once as the results are stored in a mount table): mount -f C: /c then you can write /c/path instead of /cygdrive/c/path to access the windows C:\path." ------- SH: Under File formats->DVI->Viewer->Yap You want xdvi to be there. If I have a problem I use the absolute path. But I've seen it recommended to add the helper app to Paths->Path prefix You should have several entries generated there, mine reads /usr/local/bin:/usr/bin:/usr/X11R6/bin:/c/Imagemagick/:/c/texmf/miktex/bin :/c/reader7/Reader:/c/gs/gs8.51/bin/:/c/ghostgum/gsview (in one line) LyX uses Path_prefix to append directories to the Windows PATH statement without duplicating, for LyX's own use. The journey to perfecting Enrico's instructions for installing Cygwin Lyx is located in the thread Re: LyX on Cygwin and can be found in the User archives. It consists mainly of my mistakes and Enrico's corrections. When changing a setting remember to use Apply/Modify and Save. Sometimes Reconfigure is needed. Or just close and re-open Lyx. Moving on to Converters... What is under Latex -> DVI? I have latex $$i. Since I am using Windows native, some of these may not be equivalent on Cygwin. > I'm currently using LyX on the system since I was able to find an out of > band work around by exporting the LaTeX source, using LaTeX (the version I > got from cygwin) to render it to DVI, and displaying it using xdvi (also > from cygwin). The only complaint I have with this, other than the > inconvenience, is that TOC's don't get generated. This is likely just my > limited experience with LyX (I started using it Thursday). > Remarkable progress! > You are right, I'm making some blind assumptions about what is causing the > missing menu entry. I don't really know why the menu entry isn't there, I > just thought it likely that its absence was due to my hack of the install > process, and LyX is looking for a resource that it can't find on my system > and therefore not populating the menu. If I knew what resource LyX is > looking for when it is deciding to populate the DVI entry on the menu, > then I can get what it wants and probably make it happy by fooling around > with paths and rerunning the configuration. > SH: I didn't realize you meant "its absence was due to my hack of the install process, and LyX is looking for a resource that it can't find on my system.." I thought you meant that I was implying the binary didn't have this feature. Whereas I meant the binary had the feature but it wasn't available on Cygwin, because the binary wasn't built and tested for Cygwin, which largely agrees with the meaning of your paragraph immediately above, but not below. >>CS: Your suggestion that I follow either Enrico's or Kayvan's instructions >> implies that the binary distribution I'm using was built without this >> feature. This begs the question "Why would anyone distribute a version > of a program which cannot even run the included tutorial?". No, it doesn't imply that, it implies that the binary certainly has this feature for appropriate platforms, probably not on Cygwin. > I would prefer not to rebuild LyX for two reasons: > 1) I prefer to leave that to the experts as they will more readily notice > things that go wrong and will have some idea of how to fix them. > 2) I'm interested in LyX as a user and therefore have little motivation to > learn about the details of how it is written and built. > I agree with this. > You may reasonably ask why I chose to pull cygwin packages rather than > just let the wizard do it's thing. The reason is stability of my machine. > I use cygwin everyday and trust it to be stable. The cygwin people work > to make sure that the packages work well together and the upgrade path is > automated. If I download a lot of packages from individual developments > I'm not as confident that the versions I have on my system will play well > together. > > Chuck > The native versions of Lyx for 137 and 140 appear to conflict up in C:\Documents and Settings\UserName\Application Data\LyX where preferences are stored. There is no conflict with native WinLyX and CygLyX because CygLyx has its preferences stored down in C:\Cygwin. But I am using all Windows native programs. Maybe there would be an insurmountable conflict if both the Win and Cygwin versions of ImageMagick were used for instance. But I think maybe Enrico has this working (unless he is using all Cygwin helper apps :-)) If anybody knew your approach of using the 137binary with Cygwin would work (without some hidden flaws), I never saw it in print and that is why I thought it would have to be built. I guess the thing to do now is check your Viewers, File formats, Converters and Path_prefix. Your approach would certainly be convenient for a lot of Cygwin users. What light breaks in yon horizon, Stephen
