Re: Mayday: problem with french quotation marks

[Karsten Heymann]

Hi Alain,

[EMAIL PROTECTED] schrieb:
 Thanks, it works: I could'nt find the proper item in Preferences, but the
 \usepackage[T1]{fontenc} in the preamble did it.

Here at work (LyX 1.3.4) it is in Edit - Preferences - Outputs -
LaTeX - TeX Encoding (easy, isn't it? ;) )

Yours,
Karsten

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Friday, February 24, 2006 4:33 PM
Subject: Re: LyX on Cygwin



On Fri, 24 Feb 2006 14:13:04 -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.



The good new is that I found the apparent problem. I had tetex-base 
installed for Cygwin. I uninstalled and Reconfigured and I got all

my Viewers displayed. Also Tex Information is populated.


I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.



My favorite test file, sample.lyx, does convert eps and jpeg,


I think that you have a working copy of LyX. You should simply fix
some glitches.
-- Enrico


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 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.

Working pretty good,
Stephen 

Re: LyX on Cygwin

[Enrico Forestieri]

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

Re: LyX on Cygwin

[Enrico Forestieri]

On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
 
 On Fri, 24 Feb 2006 14:13:04 -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.
 
 
 The good new is that I found the apparent problem. I had tetex-base 
 installed for Cygwin. I uninstalled and Reconfigured and I got all
 my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools-preferences
you will find an extra tab Outputs-Paths which is not present in a
non-cygwin build. Try unchecking Use Cygwin-style paths and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.

 I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.
 
 My favorite test file, sample.lyx, does convert eps and jpeg,
 
 I think that you have a working copy of LyX. You should simply fix
 some glitches.
 -- Enrico
 
 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.

Sorry, I don't follow you here.

-- 
Enrico

Re: LyX on Cygwin

[Enrico Forestieri]

Enrico Forestieri [EMAIL PROTECTED] writes:
 
 On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
  
  On Fri, 24 Feb 2006 14:13:04 -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.
  
  
  The good new is that I found the apparent problem. I had tetex-base 
  installed for Cygwin. I uninstalled and Reconfigured and I got all
  my Viewers displayed. Also Tex Information is populated.
 
 I am quite suprprised that it doesn't seem to work with the cygwin tetex.
 I also have MikTeX so I didn't noticed it. However, in Tools-preferences
 you will find an extra tab Outputs-Paths which is not present in a
 non-cygwin build. Try unchecking Use Cygwin-style paths and see what
 happens. I think that LyX is doing strange things as checking it seems
 to produce non-cygwin-style paths while unchecking it, the paths seem to
 be in cygwin-style. The logic seems to be reversed and it is really
 confusing.

I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

-- 
Enrico

Re: Display problems, LyX-Qt on Mac

[noeckel]

On Feb 25, 2006, at 10:08 AM, Anders Ekberg wrote:


Hi Jens,
I can confirm the strange look for me too on pre-4 (Aqua, clean  
install). Two screen shots attached.
Moreover I get errors when trying to preview the files. I think you  
should file a bugzilla report on this. Include lyx-files and  
screenshots. As far as I can judge this seems to be a problem that  
can be reproduced.




Hi Anders,

I've submitted this as Bug 2326.
The viewing of the file is actually no problem - you just have to  
make sure the necessary packages are loaded (e.g., AMS latex and  
wasysym). With that set up properly, the instant preview feature also  
works correctly for these symbols - but as I said earlier, I don't  
really like to use instant preview...


Thanks for confirming this issue,

Jens

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri [EMAIL PROTECTED] writes:


On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:

 On Fri, 24 Feb 2006 14:13:04 -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.


 The good new is that I found the apparent problem. I had tetex-base
 installed for Cygwin. I uninstalled and Reconfigured and I got all
 my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools-preferences
you will find an extra tab Outputs-Paths which is not present in a
non-cygwin build. Try unchecking Use Cygwin-style paths and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.


I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

--
Enrico




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.

--


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.

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.

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?

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.

Regards,
Stephen

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri [EMAIL PROTECTED] writes:




I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

--
Enrico



I reinstalled all the tetex packages and it reproduced the The document
uses a missing TeX class article. error message. It did display the
TeX Information files and paths. I think it was using the previously
generated information made when there was no error message. 


I uninstalled the tetex packages and it now works with or without
/c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths
remained on throughout this.  

Re: LyX on Cygwin

[Enrico Forestieri]

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

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 6:04 PM
Subject: Re: LyX on Cygwin



On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote:

[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



Yes, cygpath 'C:\somepath' produced /c/xemtex.

On my system the .eps files do get converted to .pdf

02/25/2006  07:33 PM  10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps
02/25/2006  07:34 PM   2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf

02/25/2006  07:33 PM   7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps
02/25/2006  07:34 PM   3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf

LyX137 converts something.eps and transistor.eps to something.pdf 
transistor.pdf
But these smaller .pdfs don't get included in the large .pdf which has the 
text in 140


No use to beat a dead horse anymore, I'll find a new one :-)
Stephen

Re: Mayday: problem with french quotation marks

[Karsten Heymann]

Hi Alain,

[EMAIL PROTECTED] schrieb:
 Thanks, it works: I could'nt find the proper item in Preferences, but the
 \usepackage[T1]{fontenc} in the preamble did it.

Here at work (LyX 1.3.4) it is in Edit - Preferences - Outputs -
LaTeX - TeX Encoding (easy, isn't it? ;) )

Yours,
Karsten

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Friday, February 24, 2006 4:33 PM
Subject: Re: LyX on Cygwin



On Fri, 24 Feb 2006 14:13:04 -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.



The good new is that I found the apparent problem. I had tetex-base 
installed for Cygwin. I uninstalled and Reconfigured and I got all

my Viewers displayed. Also Tex Information is populated.


I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.



My favorite test file, sample.lyx, does convert eps and jpeg,


I think that you have a working copy of LyX. You should simply fix
some glitches.
-- Enrico


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 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.

Working pretty good,
Stephen 

Re: LyX on Cygwin

[Enrico Forestieri]

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

Re: LyX on Cygwin

[Enrico Forestieri]

On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
 
 On Fri, 24 Feb 2006 14:13:04 -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.
 
 
 The good new is that I found the apparent problem. I had tetex-base 
 installed for Cygwin. I uninstalled and Reconfigured and I got all
 my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools-preferences
you will find an extra tab Outputs-Paths which is not present in a
non-cygwin build. Try unchecking Use Cygwin-style paths and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.

 I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.
 
 My favorite test file, sample.lyx, does convert eps and jpeg,
 
 I think that you have a working copy of LyX. You should simply fix
 some glitches.
 -- Enrico
 
 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.

Sorry, I don't follow you here.

-- 
Enrico

Re: LyX on Cygwin

[Enrico Forestieri]

Enrico Forestieri [EMAIL PROTECTED] writes:
 
 On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
  
  On Fri, 24 Feb 2006 14:13:04 -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.
  
  
  The good new is that I found the apparent problem. I had tetex-base 
  installed for Cygwin. I uninstalled and Reconfigured and I got all
  my Viewers displayed. Also Tex Information is populated.
 
 I am quite suprprised that it doesn't seem to work with the cygwin tetex.
 I also have MikTeX so I didn't noticed it. However, in Tools-preferences
 you will find an extra tab Outputs-Paths which is not present in a
 non-cygwin build. Try unchecking Use Cygwin-style paths and see what
 happens. I think that LyX is doing strange things as checking it seems
 to produce non-cygwin-style paths while unchecking it, the paths seem to
 be in cygwin-style. The logic seems to be reversed and it is really
 confusing.

I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

-- 
Enrico

Re: Display problems, LyX-Qt on Mac

[noeckel]

On Feb 25, 2006, at 10:08 AM, Anders Ekberg wrote:


Hi Jens,
I can confirm the strange look for me too on pre-4 (Aqua, clean  
install). Two screen shots attached.
Moreover I get errors when trying to preview the files. I think you  
should file a bugzilla report on this. Include lyx-files and  
screenshots. As far as I can judge this seems to be a problem that  
can be reproduced.




Hi Anders,

I've submitted this as Bug 2326.
The viewing of the file is actually no problem - you just have to  
make sure the necessary packages are loaded (e.g., AMS latex and  
wasysym). With that set up properly, the instant preview feature also  
works correctly for these symbols - but as I said earlier, I don't  
really like to use instant preview...


Thanks for confirming this issue,

Jens

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri [EMAIL PROTECTED] writes:


On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:

 On Fri, 24 Feb 2006 14:13:04 -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.


 The good new is that I found the apparent problem. I had tetex-base
 installed for Cygwin. I uninstalled and Reconfigured and I got all
 my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools-preferences
you will find an extra tab Outputs-Paths which is not present in a
non-cygwin build. Try unchecking Use Cygwin-style paths and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.


I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

--
Enrico




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.

--


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.

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.

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?

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.

Regards,
Stephen

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri [EMAIL PROTECTED] writes:




I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the Use Cygwin-style paths check button.

I tested almost everything, so I would say that it works for me.

--
Enrico



I reinstalled all the tetex packages and it reproduced the The document
uses a missing TeX class article. error message. It did display the
TeX Information files and paths. I think it was using the previously
generated information made when there was no error message. 


I uninstalled the tetex packages and it now works with or without
/c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths
remained on throughout this.  

Re: LyX on Cygwin

[Enrico Forestieri]

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

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: Enrico Forestieri [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, February 25, 2006 6:04 PM
Subject: Re: LyX on Cygwin



On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote:

[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



Yes, cygpath 'C:\somepath' produced /c/xemtex.

On my system the .eps files do get converted to .pdf

02/25/2006  07:33 PM  10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps
02/25/2006  07:34 PM   2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf

02/25/2006  07:33 PM   7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps
02/25/2006  07:34 PM   3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf

LyX137 converts something.eps and transistor.eps to something.pdf 
transistor.pdf
But these smaller .pdfs don't get included in the large .pdf which has the 
text in 140


No use to beat a dead horse anymore, I'll find a new one :-)
Stephen

Re: Mayday: problem with french quotation marks

[Karsten Heymann]

Hi Alain,

[EMAIL PROTECTED] schrieb:
> Thanks, it works: I could'nt find the proper item in Preferences, but the
> \usepackage[T1]{fontenc} in the preamble did it.

Here at work (LyX 1.3.4) it is in Edit -> Preferences -> Outputs ->
LaTeX -> TeX Encoding (easy, isn't it? ;) )

Yours,
Karsten

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: "Enrico Forestieri" <[EMAIL PROTECTED]>

To: <[EMAIL PROTECTED]>
Cc: 
Sent: Friday, February 24, 2006 4:33 PM
Subject: Re: LyX on Cygwin



On Fri, 24 Feb 2006 14:13:04 -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.



The good new is that I found the apparent problem. I had tetex-base 
installed for Cygwin. I uninstalled and Reconfigured and I got all

my Viewers displayed. Also Tex Information is populated.


I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.



My favorite test file, sample.lyx, does convert eps and jpeg,


I think that you have a working copy of LyX. You should simply fix
some glitches.
-- Enrico


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 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.

Working pretty good,
Stephen 

Re: LyX on Cygwin

[Enrico Forestieri]

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

Re: LyX on Cygwin

[Enrico Forestieri]

On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
> 
>> On Fri, 24 Feb 2006 14:13:04 -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.
>> 
> 
> The good new is that I found the apparent problem. I had tetex-base 
> installed for Cygwin. I uninstalled and Reconfigured and I got all
> my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools->preferences
you will find an extra tab Outputs->Paths which is not present in a
non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.

>>> I used mount -f C: /c  (not mount -f C: /cygdrive/c ?) as advised.
>> 
>>> My favorite test file, sample.lyx, does convert eps and jpeg,
>> 
>> I think that you have a working copy of LyX. You should simply fix
>> some glitches.
>> -- Enrico
> 
> 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.

Sorry, I don't follow you here.

-- 
Enrico

Re: LyX on Cygwin

[Enrico Forestieri]

Enrico Forestieri <[EMAIL PROTECTED]> writes:
> 
> On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
> > 
> >> On Fri, 24 Feb 2006 14:13:04 -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.
> >> 
> > 
> > The good new is that I found the apparent problem. I had tetex-base 
> > installed for Cygwin. I uninstalled and Reconfigured and I got all
> > my Viewers displayed. Also Tex Information is populated.
> 
> I am quite suprprised that it doesn't seem to work with the cygwin tetex.
> I also have MikTeX so I didn't noticed it. However, in Tools->preferences
> you will find an extra tab Outputs->Paths which is not present in a
> non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what
> happens. I think that LyX is doing strange things as checking it seems
> to produce non-cygwin-style paths while unchecking it, the paths seem to
> be in cygwin-style. The logic seems to be reversed and it is really
> confusing.

I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the "Use Cygwin-style paths" check button.

I tested almost everything, so I would say that it works for me.

-- 
Enrico

Re: Display problems, LyX-Qt on Mac

[noeckel]

On Feb 25, 2006, at 10:08 AM, Anders Ekberg wrote:


Hi Jens,
I can confirm the strange look for me too on pre-4 (Aqua, clean  
install). Two screen shots attached.
Moreover I get errors when trying to preview the files. I think you  
should file a bugzilla report on this. Include lyx-files and  
screenshots. As far as I can judge this seems to be a problem that  
can be reproduced.




Hi Anders,

I've submitted this as Bug 2326.
The viewing of the file is actually no problem - you just have to  
make sure the necessary packages are loaded (e.g., AMS latex and  
wasysym). With that set up properly, the instant preview feature also  
works correctly for these symbols - but as I said earlier, I don't  
really like to use instant preview...


Thanks for confirming this issue,

Jens

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: "Enrico Forestieri" <[EMAIL PROTECTED]>

To: 
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri <[EMAIL PROTECTED]> writes:


On Sat, 25 Feb 2006 04:07:54 -0800, Stephen Harris wrote:
>
>> On Fri, 24 Feb 2006 14:13:04 -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.
>>
>
> The good new is that I found the apparent problem. I had tetex-base
> installed for Cygwin. I uninstalled and Reconfigured and I got all
> my Viewers displayed. Also Tex Information is populated.

I am quite suprprised that it doesn't seem to work with the cygwin tetex.
I also have MikTeX so I didn't noticed it. However, in Tools->preferences
you will find an extra tab Outputs->Paths which is not present in a
non-cygwin build. Try unchecking "Use Cygwin-style paths" and see what
happens. I think that LyX is doing strange things as checking it seems
to produce non-cygwin-style paths while unchecking it, the paths seem to
be in cygwin-style. The logic seems to be reversed and it is really
confusing.


I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the "Use Cygwin-style paths" check button.

I tested almost everything, so I would say that it works for me.

--
Enrico




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.

--


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.

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.

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?

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.

Regards,
Stephen

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: "Enrico Forestieri" <[EMAIL PROTECTED]>

To: 
Sent: Saturday, February 25, 2006 9:46 AM
Subject: Re: LyX on Cygwin



Enrico Forestieri <[EMAIL PROTECTED]> writes:




I tried installing the tetex-base, tetex-bin, and tetex-extra cygwin
packages, reconfigured LyX and everything seems to work as usual.
I did not even had to touch the "Use Cygwin-style paths" check button.

I tested almost everything, so I would say that it works for me.

--
Enrico



I reinstalled all the tetex packages and it reproduced the "The document
uses a missing TeX class "article"." error message. It did display the
TeX Information files and paths. I think it was using the previously
generated information made when there was no error message. 


I uninstalled the tetex packages and it now works with or without
/c/texmf/miktex/bin in the Path prefix statement. Use cygwin-style paths
remained on throughout this.  

Re: LyX on Cygwin

[Enrico Forestieri]

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.

-- 

Re: LyX on Cygwin

[Stephen Harris]

- Original Message - 
From: "Enrico Forestieri" <[EMAIL PROTECTED]>

To: <[EMAIL PROTECTED]>
Cc: 
Sent: Saturday, February 25, 2006 6:04 PM
Subject: Re: LyX on Cygwin



On Sat, 25 Feb 2006 14:42:04 -0800, Stephen Harris wrote:

[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



Yes, cygpath 'C:\somepath' produced /c/xemtex.

On my system the .eps files do get converted to .pdf

02/25/2006  07:33 PM  10,020 1_cygdrive_c_texmf_doc_dvipdfm_transistor.eps
02/25/2006  07:34 PM   2,360 1_cygdrive_c_texmf_doc_dvipdfm_transistor.pdf

02/25/2006  07:33 PM   7,215 2_cygdrive_c_texmf_doc_dvipdfm_something.eps
02/25/2006  07:34 PM   3,284 2_cygdrive_c_texmf_doc_dvipdfm_something.pdf

LyX137 converts something.eps and transistor.eps to something.pdf 
transistor.pdf
But these smaller .pdfs don't get included in the large .pdf which has the 
text in 140


No use to beat a dead horse anymore, I'll find a new one :-)
Stephen