On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote: [...] >> 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. > > EF: 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"? > ------------------------------------------------------------------------ > > [EMAIL PROTECTED] /c > $ cygpath c:\xemtex > c:xemtex > > [EMAIL PROTECTED] /c > $ cygpath c:\xemtex\XemacsBak > c:xemtexXemacsBak > > No slashes, no delimiter.
You forgot the single quotes. In *nix shells the backslash \ is used for quoting the next character, so you have to write it two times or put the path in single (not double) quotes. So, you should write: cygpath 'C:\somepath' or cygpath C:\\somepath The \ can also be used to quote spaces: 'C:\some path with spaces' is as good as C:\\some\ path\ with\ spaces > -------------------------------------------------- > >> I am unable to convert sample.lyx into DVI or dvipdfm which >> I can do in 137 but not in LyX140_pre3 compiled with Mingw. > > I can do both with both a mingw and cygwin build, so it must be > something with your configuration. > >> I did see why Georg thought this was a .bb error, but I copied >> the *.bb to the /c/cygwin/tmp directory after renaming the original >> .bb files to the ones Cygwin was complaining about not finding. >> That doesn't work. So this seems to be a LyX140 problem. > > SH: The file is sample.tex found in C:\texmf\doc\dvipdfm (imported > to LyX) Maybe it is this particular file (not in general) but I can view > the graphics within LyX and convert to DVI with NativeWinLyX137 > but not LyX140_3 or _5 > > These are the error messages produced by the attempted DVI conversion: > LaTeX Error: File '0_cygdrive_c_texmf_doc_dvipdfm_mwicks.bb" not found > LaTeX Error: File '1_cygdrive_c_texmf_doc_dvipdfm_transistor" not found > > I reported this on bugzilla as bug 2299. > http://bugzilla.lyx.org/show_bug.cgi?id=2299 Georg Baum wrote #7: > > "I can reproduce the problem with your file (after getting > the images from the dvipdfm distribution), and I also know > the cause: dvipdfm needs .bb files for all graphics. LyX > simply does not know that and does not copy these files to > the temporary directory where latex and dvipdfm are run. > > This means that LyX 1.4 is currently not able to produce > pdf via dvipdfm if the file contains graphics. LyX 1.3.x > should have the same problem if you are using a temporary > directory. I'll try to fix this for 1.4.1 (or maybe 1.4.1 > if it turns out to be unexpectedly difficult)." end of quote > > ------------------------------------------------------------------------ > > I unchecked 'use Cygwin paths' and couldn't tell any difference > in regard to converting to DVI (or checked for that matter). > > I have /c/texmf/miktex/bin in Path prefix as instructed, maybe > you don't? I also put /c/ImageMagick in Path prefix because I > think the Cygwin ImageMagick might interfere similar to texmf, > and because it is consistent. I think it is safe to put every needed path in path_prefix. I once was concerned about this because I believed that the overall PATH length would have grown despite the fact I already had something in the system PATH. But after having a look at the LyX sources, I saw that it is done in a clever way: if something is already in the system PATH it is not added. So, if you already have an entry in the system PATH, you don't need to put it in path_prefix, but if you put something in path_prefix and it is already in the system PATH, this entry is not duplicated. > There seem to be two differences, maybe due to configuration? > Maybe you could test sample.tex imported to LyX sample.lyx? > C:\texmf\doc\dvipdfm\sample.tex > See if dvipdfm and DVI still work for you or if it is the file itself. I think that Georg is correct. After copying the .bb files to the temporary directory, dvipdfm worked, but I had also to copy there the pdf versions... it seems that LyX fails to recognize that it should convert the eps files to pdf format. No way as regards DVI output, but then I think that that is a dvipdfm specific file. All is ok with 1.3.7. > The other difference is that I have a populated TeX Information > and I can send you a screenshot of it present in CygLyxWin140_5. > I'm wondering if there are differences due to TeTeX vs. Miktex? No, I don't think that's the problem, it must be something else. I have an empty TeX information with both teTeX and MikTeX, and with both 1.3.7 and 1.4.0 but LyX works and so I don't care... it must be something with my environment. > OTOH, if you are tired of this issue, the build is fine, thanks to you. > I've tried to consolidate our recent posts into this one. You're welcome. -- Enrico
