Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I didn't mean to be obscure. It was obvious to me and I thought it
 would be obvious to you that several people could have been steered
 toward using a binary with Cygwin which was certainly is a lot easier than
 building LyX on Cygwin before your very recent major improvement. So
 I didn't elaborate, just kidded Angus in case he was reading. I was happy
 that I got it to work, the solution was so simple. I got around to asking
 what the batfiles did. And the only imperfection that I noticed was that
 Tex Information didn't populate. I tried hacking TeXFiles.sh to no avail.
 It occurs to me that I could just post this paragraph and delete the rest
 of the reply. But I put too much work into it, so it may be a perversion
 that I don't delete it, or at least obsessive compulsive retention. 

Stephen,

I did not mean to imply anything with you, and I was just joking (see
all the smileys?).

That .bat files were the ones I needed to make a native LyX work with
all cygwin apps. What I was trying to say is that, unfortunately, there
exist so many possible configurations (mix of native and cygwin apps,
even different cygwin versions in which a program can be a symlink or
not) that exiting from the three cases I outlined before, leads to such
headaches that it would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language, I am not really
able to convey what I mean...

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:
 
 Never mind about the batfiles. I just saw what python.bat does
 and I'm sure the other batfiles do something useful also which
 I'll discover with some use. I have them in a good spot.

Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.

pdflatex.bat: ditto

python.bat: ditto

xdvi.bat: I needed this because /bin/xdvi is a shell script and so it
is not an executable in the eyes of a native app. Also, xdvi needs X11
to run, so I had to set the DISPLAY variable.

Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.

 I have no more questions and I'm quite happy with Cygwin LyX140
 and the added versatility it offers, all due to your persistent efforts.
 
 Thanks for all the advice and a great CygLyX installer and Howto, 

You're welcome.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Wednesday, March 15, 2006 7:18 AM
Subject: Re: No VIEW-DVI in LyX Win32 Works!



Stephen Harris [EMAIL PROTECTED] writes:


Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.


Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.



I discovered something like this by chance. I was trying to get the
Viewers to be recognized. So I Reconfigured. Before closing I
checked the Viewers and they were all right as rain. But when Lyx
was closed and then opened, those buggers had slunk back into a
state of sin.


Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.



SH: That script is so compact.


Enrico



EF: ...would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language [SH: tongue],
I am not really able to convey what I mean...

SH: Oh, you are quite fluent. And I am displaying a perverse 
(cranky/peevish)
attitude in observing that a tailor who alters garments is not a poetic 
wordsmith.


The fair breeze blew, the white foam flew,
the furrow followed free.  We were the
first that ever burst onto that silent sea.
- Samuel Taylor Cooleridge, The Rhyme of the Ancient Mariner

Idiomatically yours,
Stephen 

Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I didn't mean to be obscure. It was obvious to me and I thought it
 would be obvious to you that several people could have been steered
 toward using a binary with Cygwin which was certainly is a lot easier than
 building LyX on Cygwin before your very recent major improvement. So
 I didn't elaborate, just kidded Angus in case he was reading. I was happy
 that I got it to work, the solution was so simple. I got around to asking
 what the batfiles did. And the only imperfection that I noticed was that
 Tex Information didn't populate. I tried hacking TeXFiles.sh to no avail.
 It occurs to me that I could just post this paragraph and delete the rest
 of the reply. But I put too much work into it, so it may be a perversion
 that I don't delete it, or at least obsessive compulsive retention. 

Stephen,

I did not mean to imply anything with you, and I was just joking (see
all the smileys?).

That .bat files were the ones I needed to make a native LyX work with
all cygwin apps. What I was trying to say is that, unfortunately, there
exist so many possible configurations (mix of native and cygwin apps,
even different cygwin versions in which a program can be a symlink or
not) that exiting from the three cases I outlined before, leads to such
headaches that it would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language, I am not really
able to convey what I mean...

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:
 
 Never mind about the batfiles. I just saw what python.bat does
 and I'm sure the other batfiles do something useful also which
 I'll discover with some use. I have them in a good spot.

Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.

pdflatex.bat: ditto

python.bat: ditto

xdvi.bat: I needed this because /bin/xdvi is a shell script and so it
is not an executable in the eyes of a native app. Also, xdvi needs X11
to run, so I had to set the DISPLAY variable.

Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.

 I have no more questions and I'm quite happy with Cygwin LyX140
 and the added versatility it offers, all due to your persistent efforts.
 
 Thanks for all the advice and a great CygLyX installer and Howto, 

You're welcome.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Wednesday, March 15, 2006 7:18 AM
Subject: Re: No VIEW-DVI in LyX Win32 Works!



Stephen Harris [EMAIL PROTECTED] writes:


Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.


Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.



I discovered something like this by chance. I was trying to get the
Viewers to be recognized. So I Reconfigured. Before closing I
checked the Viewers and they were all right as rain. But when Lyx
was closed and then opened, those buggers had slunk back into a
state of sin.


Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.



SH: That script is so compact.


Enrico



EF: ...would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language [SH: tongue],
I am not really able to convey what I mean...

SH: Oh, you are quite fluent. And I am displaying a perverse 
(cranky/peevish)
attitude in observing that a tailor who alters garments is not a poetic 
wordsmith.


The fair breeze blew, the white foam flew,
the furrow followed free.  We were the
first that ever burst onto that silent sea.
- Samuel Taylor Cooleridge, The Rhyme of the Ancient Mariner

Idiomatically yours,
Stephen 

Re: No VIEW->DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

> I didn't mean to be obscure. It was obvious to me and I thought it
> would be obvious to you that several people could have been steered
> toward using a binary with Cygwin which was certainly is a lot easier than
> building LyX on Cygwin before your very recent major improvement. So
> I didn't elaborate, just kidded Angus in case he was reading. I was happy
> that I got it to work, the solution was so simple. I got around to asking
> what the batfiles did. And the only imperfection that I noticed was that
> Tex Information didn't populate. I tried hacking TeXFiles.sh to no avail.
> It occurs to me that I could just post this paragraph and delete the rest
> of the reply. But I put too much work into it, so it may be a perversion
> that I don't delete it, or at least obsessive compulsive retention. 

Stephen,

I did not mean to imply anything with you, and I was just joking (see
all the smileys?).

That .bat files were the ones I needed to make a native LyX work with
all cygwin apps. What I was trying to say is that, unfortunately, there
exist so many possible configurations (mix of native and cygwin apps,
even different cygwin versions in which a program can be a symlink or
not) that exiting from the three cases I outlined before, leads to such
headaches that it would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language, I am not really
able to convey what I mean...

-- 
Enrico

Re: No VIEW->DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:
> 
> Never mind about the batfiles. I just saw what python.bat does
> and I'm sure the other batfiles do something useful also which
> I'll discover with some use. I have them in a good spot.

Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.

pdflatex.bat: ditto

python.bat: ditto

xdvi.bat: I needed this because /bin/xdvi is a shell script and so it
is not an executable in the eyes of a native app. Also, xdvi needs X11
to run, so I had to set the DISPLAY variable.

Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.

> I have no more questions and I'm quite happy with Cygwin LyX140
> and the added versatility it offers, all due to your persistent efforts.
> 
> Thanks for all the advice and a great CygLyX installer and Howto, 

You're welcome.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32 Works!

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Wednesday, March 15, 2006 7:18 AM
Subject: Re: No VIEW->DVI in LyX Win32 Works!



Stephen Harris <[EMAIL PROTECTED]> writes:


Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.


Let me briefly comment on why I needed them, one by one.

latex.bat: I needed this because /bin/latex was a symlink to /bin/pdftex
and a native LyX would not recognize it as a command. Note that the
problem with symlinks is rather subtle, because they would be recognized
as a command when you reconfigure LyX (as the reconfigure script is run
by sh.exe which is a cygwin app), but trying executing them through a
native app (LyX in this case) does not work, as they are not recognized.



I discovered something like this by chance. I was trying to get the
Viewers to be recognized. So I Reconfigured. Before closing I
checked the Viewers and they were all right as rain. But when Lyx
was closed and then opened, those buggers had slunk back into a
state of sin.


Now, if you delete the symlinks and copy in their place the programs
the symlinks were pointing to, you don't need anymore the .bat files.

You still need the xdvi.bat because /bin/xdvi is a shell script.



SH: That script is so compact.


Enrico



EF: ...would be seen as a perverted attitude to insist on it.
I am sorry that, english not being my mother language [SH: tongue],
I am not really able to convey what I mean...

SH: Oh, you are quite fluent. And I am displaying a perverse 
(cranky/peevish)
attitude in observing that a tailor who alters garments is not a poetic 
wordsmith.


"The fair breeze blew, the white foam flew,
the furrow followed free.  We were the
first that ever burst onto that silent sea."
- Samuel Taylor Cooleridge, The Rhyme of the Ancient Mariner

Idiomatically yours,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

[...]
 SH: So it seems to be working. The good news is that lyx-x11 works
 pretty well. It displays Tex Information whereas lyx-winbin does not.

This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.

[...]
 lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
 made and the correct output quickly flashes on the screen but then
 quits with the error message: winMultiWindowXMsgProcErrorHandler -
 ERROR: BadWindow invalid Window parameter
 I can use Windows ghostview, however.

Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html

[...]
 I can't use any Cygwin helper apps with lyx-winbin. They fail
 with a 'can't open display' whether I have started Xwin or not.
 I don't know if one of those batfiles written as a script would help.

This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try setenv DISPLAY :0 if you use tcsh, or export DISPLAY=':0' if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.

 Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
 work with any Cygwin apps, with or without batfiles, with or
 without startx for Cygwin. It works with Windows apps, as
 expected, but what is the use of using Cygwin for LyX then?
 I have them installed in C:\lyxcyg\bin

It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:

[...]

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.


This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.



SH: It is odd, I moved /.lyx to another folder since Windows doesn't
allow renaming of directories to a .(dot prefix) with Windoes Explorer.

So I did get all of Tex Information displayed with lyx-win and lyx-x11!


[...]

lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow invalid Window parameter
I can use Windows ghostview, however.


Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html



I installed gv and now I have postscript/gv, DVI/xdvi(k) and pdf/xpdf
all working. The only thing I've noticed not quite right in lyx-x11 is that
if I have a menu open like File, if I click on minimize ( - ) LyX minimizes
but leaves the File menu window open and hanging on the desktop.
Easy enough to get around by just clicking on the body of LyX which
closes the File menu drop-down and then minimize works as expected.



[...]

I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.


This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try setenv DISPLAY :0 if you use tcsh, or export DISPLAY=':0' if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.



Yes Indeed. It works from the command line. I was trying to start
lyx-win from a shortcut on the Desktop, which didn't work. But
the desktop shortcut to lyx-x11 does work.


Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin


It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

--
Enrico



I put C:\lyxcyg\bin as the first component of Path prefix. Also of 
Windows PATH. I also have C:\cygwin\bin;C:\cygwin\usr\local\bin;

C:\Cygwin\usr\bin;C:\cygwin\usr\X11R6\bin in the Path Prefix.
Also the batfiles are copied under C:\lyxcyg\bin 


Under File formats I have listed absolute paths like C:\cygwin\bin\xpdf
I ran startx from the the bash shell. I used lyx.exe so I could see the
reports. It does seem like LyX is invoking all the Cygwin apps and
creating output files. But there is no display. And now Tex Information
fails to populate with lyx-1.3.7_win32_setup_v2.

I am making a mistake somewhere because the lyx-winbin works
and lyx-1.3.7_win32_setup_v2 works with Cygwin in two cases.
Anyway, lyx-x11 is working well which is my main concern. I hope 
that Chuck is able to benefit from your batfiles. 


Regards,
Stephen

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:



EF: It works for me with lyx-1.3.7_win32_setup_v2. You should rather put
them in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH 
prefix.


--
Enrico



I made a shortcut to startxwin, which opened in my Home directory.
Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
Tex Information still does not visibly populate, but I'm pretty sure they 
are

indexed. The drop-down box doesn't work right either (with or without
latex.bat). I'm not sure this is what you intended since the batfiles don't 
seem

to be needed and you wouldn't have gone to that trouble without a reason.
I suppose they were for non-X11 functioning. My impression that a WinLyX
binary wouldn't work with Cygwin seems to be wrong.

It must have been something Angus told me ;-)
Stephen 

Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I made a shortcut to startxwin, which opened in my Home directory.
 Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
 This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
 Tex Information still does not visibly populate, but I'm pretty sure they 
 are
 indexed. The drop-down box doesn't work right either (with or without
 latex.bat). I'm not sure this is what you intended since the batfiles don't 
 seem
 to be needed and you wouldn't have gone to that trouble without a reason.
 I suppose they were for non-X11 functioning. My impression that a WinLyX
 binary wouldn't work with Cygwin seems to be wrong.
 
 It must have been something Angus told me 
 Stephen 

Stephen,

I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)

My idea about all these LyX versions was the following:

1) People not even knowing the existence of cygwin should be happy
   with the native LyX version (i.e., that not needing the cygwin dll)
   and all native Windows helper apps.

2) People having cygwin installed but using MikTeX instead of teTeX,
   should be happy with a cygwin version of LyX which uses the native
   Windows graphics (i.e., doesn't need an X-server).

3) People using all cygwin apps (tetex, xdvi, gv, ...) would gain nothing
   from having a cygwin version of LyX using native graphics, as they
   still need launching an X-server. For them, a cygwin LyX/X11 should be
   the right thing.

Given that, it is possible to use a native LyX with all cygwin apps but
you must know what you are doing and a casual user is perhaps overwhelmed
by the task of making it work.

Until now, only a native LyX version was available, so I think it was
worth providing a cleaner solution for people like in 2) or 3) above.

I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW-DVI in LyX Win32 Works!

snip


Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work.



I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

--
Enrico




That is all well and good. I got confused about the purpose of the
batfiles. LyX137v2 works with all cygwin apps and x11 if LyX137
is started from startwinx.bat shell. The batfiles have no apparent
effect whether they are contained in ~/lyx/bin or they are not there.

I had a desktop shortcut linked to ~/lyx/bin/lyx.bat for LyX137.
Double-clicking on the shortcut did not open LyX137 so that
it could use the Cygwin apps. I thought the batfiles were intended
to make LyX137 started from the shortcut work so as to use the
Cygwin apps. But they didn't. So I made a bad assumption and
decided to try to make LyX137 function in the same manner as
lyx-winbin. That worked I assume because it started the Xserver.

So I don't know what the batfiles are for? They are a bit tricky.
I'm wondering why in the past eight months whenever there was
a request from a poster for a version of LyX which worked with
Cygwin, there was no positive response, maybe a suggestion to
try building LyX on Cygwin with complicated terse instructions.

Nobody said run the LyX136or137 binary and choose all Cygwin
apps; you will need these files... LyX will need to be started with an
Xserver, so use startxwin and navigate to your /Lyx/bin and type
lyx.bat. Put such and such in your Path prefix.

Not many instructions are needed and they are easy to follow. This
approach was available before you developed the simplified build
instructions for LyX140. But I didn't read about it in LyX or any of
the other relevant forums. Here is an example of the common perception
of LyX and Cygwin which I used to share and is far from reality.
-

Lyx 1.4 for Windows (comp.text.tex)

have not tried this, but about a year ago it was a real pain to get
lyx on cygwin working.  If this works at all, it is terrific.

Building yourself can be a pain. Even getting a prebuild running using
Cygwin can be terrible since lyx needs so many components, tex, dvips,
acroread, display, eps tools, etc.  If this installer works, I would
take whatever it gives me rather than configure lyx on cygwin myself.
--

But the installer does work with Cygwin, you don't need to build
anything. There are two time-consuming tasks. 1. Downloading and
installing Cygwin which is not that big if you already have a working
version of Cygwin. 2. Figuring out how to start LyX so that it could
make use of the Cygwin apps. Perhaps it should be obvious as it was
to you that lyx-x11 didn't need an Xserver started but that lyx-winbin
did, and so did LyX137v2. But I had forgotten it. Otherwise, using the
binary is easier than your easy Cygwin LyX140 build advice, especially
compared to CygLyx1.3.1 or even 1.3.5. With the help of a short Howto.

Anyway, I never saw using a binary with Cygwin mentioned as a possibility
on the User list or developer although I didn't read all the developer 
posts. So

that is why I am surprised that nobody mentioned a 10 times easier method.
I saw Chuck undertake this task with three days of experience and make
good progress, but he expressed doubts about undertaking the build.

EF: Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work.

SH: They may be a bit daunted but not nearly as aghast as when
they are considering building Cygwin, especially in the past. That
doesn't seem like a reason for nobody at all to mention it here on
the mailing list. The most likely cause for the conspiracy of silence is
that almost noone knew it. Have you ever seen it mentioned?

Well, there may be more to this. I thought the batfiles were meant to
contribute the function of communicating from the native WinLyx
binary and employing the Cygwin apps. Which led me away from
thinking all I needed to do was start LyX in an Xserver shell. I
wasn't trying to be perverse. I just should have asked what purpose
the batfiles were intended to accomplish. It appears to me that they
don't help access the Cygwin Viewers, so they must do something
else. I mistakenly thought they were to enable the Viewers. I was hazy
about how it was to be done, I suspected it was native windows, but
not out of a perverse desire to disenfranchise X11. I

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW-DVI in LyX Win32 Works!




I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)



Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.

I have no more questions and I'm quite happy with Cygwin LyX140
and the added versatility it offers, all due to your persistent efforts.

Thanks for all the advice and a great CygLyX installer and Howto, 

Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

[...]
 SH: So it seems to be working. The good news is that lyx-x11 works
 pretty well. It displays Tex Information whereas lyx-winbin does not.

This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.

[...]
 lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
 made and the correct output quickly flashes on the screen but then
 quits with the error message: winMultiWindowXMsgProcErrorHandler -
 ERROR: BadWindow invalid Window parameter
 I can use Windows ghostview, however.

Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html

[...]
 I can't use any Cygwin helper apps with lyx-winbin. They fail
 with a 'can't open display' whether I have started Xwin or not.
 I don't know if one of those batfiles written as a script would help.

This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try setenv DISPLAY :0 if you use tcsh, or export DISPLAY=':0' if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.

 Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
 work with any Cygwin apps, with or without batfiles, with or
 without startx for Cygwin. It works with Windows apps, as
 expected, but what is the use of using Cygwin for LyX then?
 I have them installed in C:\lyxcyg\bin

It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:

[...]

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.


This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.



SH: It is odd, I moved /.lyx to another folder since Windows doesn't
allow renaming of directories to a .(dot prefix) with Windoes Explorer.

So I did get all of Tex Information displayed with lyx-win and lyx-x11!


[...]

lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow invalid Window parameter
I can use Windows ghostview, however.


Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html



I installed gv and now I have postscript/gv, DVI/xdvi(k) and pdf/xpdf
all working. The only thing I've noticed not quite right in lyx-x11 is that
if I have a menu open like File, if I click on minimize ( - ) LyX minimizes
but leaves the File menu window open and hanging on the desktop.
Easy enough to get around by just clicking on the body of LyX which
closes the File menu drop-down and then minimize works as expected.



[...]

I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.


This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try setenv DISPLAY :0 if you use tcsh, or export DISPLAY=':0' if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.



Yes Indeed. It works from the command line. I was trying to start
lyx-win from a shortcut on the Desktop, which didn't work. But
the desktop shortcut to lyx-x11 does work.


Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin


It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

--
Enrico



I put C:\lyxcyg\bin as the first component of Path prefix. Also of 
Windows PATH. I also have C:\cygwin\bin;C:\cygwin\usr\local\bin;

C:\Cygwin\usr\bin;C:\cygwin\usr\X11R6\bin in the Path Prefix.
Also the batfiles are copied under C:\lyxcyg\bin 


Under File formats I have listed absolute paths like C:\cygwin\bin\xpdf
I ran startx from the the bash shell. I used lyx.exe so I could see the
reports. It does seem like LyX is invoking all the Cygwin apps and
creating output files. But there is no display. And now Tex Information
fails to populate with lyx-1.3.7_win32_setup_v2.

I am making a mistake somewhere because the lyx-winbin works
and lyx-1.3.7_win32_setup_v2 works with Cygwin in two cases.
Anyway, lyx-x11 is working well which is my main concern. I hope 
that Chuck is able to benefit from your batfiles. 


Regards,
Stephen

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:



EF: It works for me with lyx-1.3.7_win32_setup_v2. You should rather put
them in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH 
prefix.


--
Enrico



I made a shortcut to startxwin, which opened in my Home directory.
Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
Tex Information still does not visibly populate, but I'm pretty sure they 
are

indexed. The drop-down box doesn't work right either (with or without
latex.bat). I'm not sure this is what you intended since the batfiles don't 
seem

to be needed and you wouldn't have gone to that trouble without a reason.
I suppose they were for non-X11 functioning. My impression that a WinLyX
binary wouldn't work with Cygwin seems to be wrong.

It must have been something Angus told me ;-)
Stephen 

Re: No VIEW-DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I made a shortcut to startxwin, which opened in my Home directory.
 Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
 This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
 Tex Information still does not visibly populate, but I'm pretty sure they 
 are
 indexed. The drop-down box doesn't work right either (with or without
 latex.bat). I'm not sure this is what you intended since the batfiles don't 
 seem
 to be needed and you wouldn't have gone to that trouble without a reason.
 I suppose they were for non-X11 functioning. My impression that a WinLyX
 binary wouldn't work with Cygwin seems to be wrong.
 
 It must have been something Angus told me 
 Stephen 

Stephen,

I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)

My idea about all these LyX versions was the following:

1) People not even knowing the existence of cygwin should be happy
   with the native LyX version (i.e., that not needing the cygwin dll)
   and all native Windows helper apps.

2) People having cygwin installed but using MikTeX instead of teTeX,
   should be happy with a cygwin version of LyX which uses the native
   Windows graphics (i.e., doesn't need an X-server).

3) People using all cygwin apps (tetex, xdvi, gv, ...) would gain nothing
   from having a cygwin version of LyX using native graphics, as they
   still need launching an X-server. For them, a cygwin LyX/X11 should be
   the right thing.

Given that, it is possible to use a native LyX with all cygwin apps but
you must know what you are doing and a casual user is perhaps overwhelmed
by the task of making it work.

Until now, only a native LyX version was available, so I think it was
worth providing a cleaner solution for people like in 2) or 3) above.

I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

-- 
Enrico

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW-DVI in LyX Win32 Works!

snip


Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work.



I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

--
Enrico




That is all well and good. I got confused about the purpose of the
batfiles. LyX137v2 works with all cygwin apps and x11 if LyX137
is started from startwinx.bat shell. The batfiles have no apparent
effect whether they are contained in ~/lyx/bin or they are not there.

I had a desktop shortcut linked to ~/lyx/bin/lyx.bat for LyX137.
Double-clicking on the shortcut did not open LyX137 so that
it could use the Cygwin apps. I thought the batfiles were intended
to make LyX137 started from the shortcut work so as to use the
Cygwin apps. But they didn't. So I made a bad assumption and
decided to try to make LyX137 function in the same manner as
lyx-winbin. That worked I assume because it started the Xserver.

So I don't know what the batfiles are for? They are a bit tricky.
I'm wondering why in the past eight months whenever there was
a request from a poster for a version of LyX which worked with
Cygwin, there was no positive response, maybe a suggestion to
try building LyX on Cygwin with complicated terse instructions.

Nobody said run the LyX136or137 binary and choose all Cygwin
apps; you will need these files... LyX will need to be started with an
Xserver, so use startxwin and navigate to your /Lyx/bin and type
lyx.bat. Put such and such in your Path prefix.

Not many instructions are needed and they are easy to follow. This
approach was available before you developed the simplified build
instructions for LyX140. But I didn't read about it in LyX or any of
the other relevant forums. Here is an example of the common perception
of LyX and Cygwin which I used to share and is far from reality.
-

Lyx 1.4 for Windows (comp.text.tex)

have not tried this, but about a year ago it was a real pain to get
lyx on cygwin working.  If this works at all, it is terrific.

Building yourself can be a pain. Even getting a prebuild running using
Cygwin can be terrible since lyx needs so many components, tex, dvips,
acroread, display, eps tools, etc.  If this installer works, I would
take whatever it gives me rather than configure lyx on cygwin myself.
--

But the installer does work with Cygwin, you don't need to build
anything. There are two time-consuming tasks. 1. Downloading and
installing Cygwin which is not that big if you already have a working
version of Cygwin. 2. Figuring out how to start LyX so that it could
make use of the Cygwin apps. Perhaps it should be obvious as it was
to you that lyx-x11 didn't need an Xserver started but that lyx-winbin
did, and so did LyX137v2. But I had forgotten it. Otherwise, using the
binary is easier than your easy Cygwin LyX140 build advice, especially
compared to CygLyx1.3.1 or even 1.3.5. With the help of a short Howto.

Anyway, I never saw using a binary with Cygwin mentioned as a possibility
on the User list or developer although I didn't read all the developer 
posts. So

that is why I am surprised that nobody mentioned a 10 times easier method.
I saw Chuck undertake this task with three days of experience and make
good progress, but he expressed doubts about undertaking the build.

EF: Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work.

SH: They may be a bit daunted but not nearly as aghast as when
they are considering building Cygwin, especially in the past. That
doesn't seem like a reason for nobody at all to mention it here on
the mailing list. The most likely cause for the conspiracy of silence is
that almost noone knew it. Have you ever seen it mentioned?

Well, there may be more to this. I thought the batfiles were meant to
contribute the function of communicating from the native WinLyx
binary and employing the Cygwin apps. Which led me away from
thinking all I needed to do was start LyX in an Xserver shell. I
wasn't trying to be perverse. I just should have asked what purpose
the batfiles were intended to accomplish. It appears to me that they
don't help access the Cygwin Viewers, so they must do something
else. I mistakenly thought they were to enable the Viewers. I was hazy
about how it was to be done, I suspected it was native windows, but
not out of a perverse desire to disenfranchise X11. I

Re: No VIEW-DVI in LyX Win32 Works!

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW-DVI in LyX Win32 Works!




I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)



Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.

I have no more questions and I'm quite happy with Cygwin LyX140
and the added versatility it offers, all due to your persistent efforts.

Thanks for all the advice and a great CygLyX installer and Howto, 

Stephen 

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

[...]
> SH: So it seems to be working. The good news is that lyx-x11 works
> pretty well. It displays Tex Information whereas lyx-winbin does not.

This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.

[...]
> lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
> made and the correct output quickly flashes on the screen but then
> quits with the error message: winMultiWindowXMsgProcErrorHandler -
> ERROR: BadWindow 
> I can use Windows ghostview, however.

Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html

[...]
> I can't use any Cygwin helper apps with lyx-winbin. They fail
> with a 'can't open display' whether I have started Xwin or not.
> I don't know if one of those batfiles written as a script would help.

This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try "setenv DISPLAY :0" if you use tcsh, or "export DISPLAY=':0'" if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.

> Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
> work with any Cygwin apps, with or without batfiles, with or
> without startx for Cygwin. It works with Windows apps, as
> expected, but what is the use of using Cygwin for LyX then?
> I have them installed in C:\lyxcyg\bin

It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen Harris <[EMAIL PROTECTED]> writes:

[...]

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.


This is quite strange, as both share the same user and system dir.
I think that this can happen only if you use tetex with lyx-x11 and
miktex with lyx-win. In this case you will see the TeX Information only
with the first one of the two you used for generating it. Try renaming
~/.lyx as ~/.lyx.save and then launch lyx-win asking for TeX Information.
I suspect that now you will see the TeX Information with lyx-win but not
with lyx-x11.



SH: It is odd, I moved /.lyx to another folder since Windows doesn't
allow renaming of directories to a .(dot prefix) with Windoes Explorer.

So I did get all of Tex Information displayed with lyx-win and lyx-x11!


[...]

lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow 
I can use Windows ghostview, however.


Uhm... this seems to be a X protocol error. May be this URL is useful:
http://www.rahul.net/kenton/perrors.html



I installed gv and now I have postscript/gv, DVI/xdvi(k) and pdf/xpdf
all working. The only thing I've noticed not quite right in lyx-x11 is that
if I have a menu open like File, if I click on minimize ( - ) LyX minimizes
but leaves the File menu window open and hanging on the desktop.
Easy enough to get around by just clicking on the body of LyX which
closes the File menu drop-down and then minimize works as expected.



[...]

I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.


This is because you have not set the DISPLAY variable. If you launch
lyx-winbin through its wrapper (lyx-win) everything should work if you
have Xwin running (lyx-win will not launch it, only lyx-x11 does)
because in this case /etc/lyxprofile gets read and there DISPLAY is set.
Try "setenv DISPLAY :0" if you use tcsh, or "export DISPLAY=':0'" if you
use bash, before launching lyx-winbin from the command line. You can
insert those setting in your $HOME/.tcshrc and $HOME/.bashrc,
respectively, such that you don't have to type them all the time.



Yes Indeed. It works from the command line. I was trying to start
lyx-win from a shortcut on the Desktop, which didn't work. But
the desktop shortcut to lyx-x11 does work.


Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin


It works for me with lyx-1.3.7_win32_setup_v2. You should rather put them
in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH prefix.

--
Enrico



I put C:\lyxcyg\bin as the first component of Path prefix. Also of 
Windows PATH. I also have C:\cygwin\bin;C:\cygwin\usr\local\bin;

C:\Cygwin\usr\bin;C:\cygwin\usr\X11R6\bin in the Path Prefix.
Also the batfiles are copied under C:\lyxcyg\bin 


Under File formats I have listed absolute paths like C:\cygwin\bin\xpdf
I ran startx from the the bash shell. I used lyx.exe so I could see the
reports. It does seem like LyX is invoking all the Cygwin apps and
creating output files. But there is no display. And now Tex Information
fails to populate with lyx-1.3.7_win32_setup_v2.

I am making a mistake somewhere because the lyx-winbin works
and lyx-1.3.7_win32_setup_v2 works with Cygwin in two cases.
Anyway, lyx-x11 is working well which is my main concern. I hope 
that Chuck is able to benefit from your batfiles. 


Regards,
Stephen

Re: No VIEW->DVI in LyX Win32 Works!

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Tuesday, March 14, 2006 4:50 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen Harris <[EMAIL PROTECTED]> writes:



EF: It works for me with lyx-1.3.7_win32_setup_v2. You should rather put
them in ~\LyX\bin or have C:\lyxcyg\bin as the first component of PATH 
prefix.


--
Enrico



I made a shortcut to startxwin, which opened in my Home directory.
Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
Tex Information still does not visibly populate, but I'm pretty sure they 
are

indexed. The drop-down box doesn't work right either (with or without
latex.bat). I'm not sure this is what you intended since the batfiles don't 
seem

to be needed and you wouldn't have gone to that trouble without a reason.
I suppose they were for non-X11 functioning. My impression that a WinLyX
binary wouldn't work with Cygwin seems to be wrong.

It must have been something Angus told me ;-)
Stephen 

Re: No VIEW->DVI in LyX Win32 Works!

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

> I made a shortcut to startxwin, which opened in my Home directory.
> Then a lyxer.bat file to change to C:\lyxcyg\bin\ - lyx.bat
> This starts up LyX137v2, which now uses Cygwins', xdvi, xpdf and gv.
> Tex Information still does not visibly populate, but I'm pretty sure they 
> are
> indexed. The drop-down box doesn't work right either (with or without
> latex.bat). I'm not sure this is what you intended since the batfiles don't 
> seem
> to be needed and you wouldn't have gone to that trouble without a reason.
> I suppose they were for non-X11 functioning. My impression that a WinLyX
> binary wouldn't work with Cygwin seems to be wrong.
> 
> It must have been something Angus told me 
> Stephen 

Stephen,

I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)

My idea about all these LyX versions was the following:

1) People not even knowing the existence of cygwin should be happy
   with the native LyX version (i.e., that not needing the cygwin dll)
   and all native Windows helper apps.

2) People having cygwin installed but using MikTeX instead of teTeX,
   should be happy with a cygwin version of LyX which uses the native
   Windows graphics (i.e., doesn't need an X-server).

3) People using all cygwin apps (tetex, xdvi, gv, ...) would gain nothing
   from having a cygwin version of LyX using native graphics, as they
   still need launching an X-server. For them, a cygwin LyX/X11 should be
   the right thing.

Given that, it is possible to use a native LyX with all cygwin apps but
you must know what you are doing and a casual user is perhaps overwhelmed
by the task of making it work.

Until now, only a native LyX version was available, so I think it was
worth providing a cleaner solution for people like in 2) or 3) above.

I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

-- 
Enrico

Re: No VIEW->DVI in LyX Win32 Works!

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW->DVI in LyX Win32 Works!




Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work.



I would stick with the three cases above only, without taking into
consideration the possibility of using native LyX with all cygwin apps
or, conversely, using a cygwin LyX with all native apps. These cases
would be considered as perversions ;-)

IMHO, of course ;-)

--
Enrico




That is all well and good. I got confused about the purpose of the
batfiles. LyX137v2 works with all cygwin apps and x11 if LyX137
is started from startwinx.bat shell. The batfiles have no apparent
effect whether they are contained in ~/lyx/bin or they are not there.

I had a desktop shortcut linked to ~/lyx/bin/lyx.bat for LyX137.
Double-clicking on the shortcut did not open LyX137 so that
it could use the Cygwin apps. I thought the batfiles were intended
to make LyX137 started from the shortcut work so as to use the
Cygwin apps. But they didn't. So I made a bad assumption and
decided to try to make LyX137 function in the same manner as
lyx-winbin. That worked I assume because it started the Xserver.

So I don't know what the batfiles are for? They are a bit tricky.
I'm wondering why in the past eight months whenever there was
a request from a poster for a version of LyX which worked with
Cygwin, there was no positive response, maybe a suggestion to
try building LyX on Cygwin with complicated terse instructions.

Nobody said run the LyX136or137 binary and choose all Cygwin
apps; you will need these files... LyX will need to be started with an
Xserver, so use startxwin and navigate to your /Lyx/bin and type
lyx.bat. Put such and such in your Path prefix.

Not many instructions are needed and they are easy to follow. This
approach was available before you developed the simplified build
instructions for LyX140. But I didn't read about it in LyX or any of
the other relevant forums. Here is an example of the common perception
of LyX and Cygwin which I used to share and is far from reality.
-

Lyx 1.4 for Windows (comp.text.tex)

"have not tried this, but about a year ago it was a real pain to get
lyx on cygwin working.  If this works at all, it is terrific.

Building yourself can be a pain. Even getting a prebuild running using
Cygwin can be terrible since lyx needs so many components, tex, dvips,
acroread, display, eps tools, etc.  If this installer works, I would
take whatever it gives me rather than configure lyx on cygwin myself."
--

But the installer does work with Cygwin, you don't need to build
anything. There are two time-consuming tasks. 1. Downloading and
installing Cygwin which is not that big if you already have a working
version of Cygwin. 2. Figuring out how to start LyX so that it could
make use of the Cygwin apps. Perhaps it should be obvious as it was
to you that lyx-x11 didn't need an Xserver started but that lyx-winbin
did, and so did LyX137v2. But I had forgotten it. Otherwise, using the
binary is easier than your easy Cygwin LyX140 build advice, especially
compared to CygLyx1.3.1 or even 1.3.5. With the help of a short Howto.

Anyway, I never saw using a binary with Cygwin mentioned as a possibility
on the User list or developer although I didn't read all the developer 
posts. So

that is why I am surprised that nobody mentioned a 10 times easier method.
I saw Chuck undertake this task with three days of experience and make
good progress, but he expressed doubts about undertaking the build.

EF: "Given that, it is possible to use a native LyX with all cygwin apps
but you must know what you are doing and a casual user is perhaps
overwhelmed by the task of making it work."

SH: They may be a bit daunted but not nearly as aghast as when
they are considering building Cygwin, especially in the past. That
doesn't seem like a reason for nobody at all to mention it here on
the mailing list. The most likely cause for the conspiracy of silence is
that almost noone knew it. Have you ever seen it mentioned?

Well, there may be more to this. I thought the batfiles were meant to
contribute the function of communicating from the native WinLyx
binary and employing the Cygwin apps. Which led me away from
thinking all I needed to do was start LyX in an Xserver shell. I
wasn't trying to be perverse. I just should have asked what purpose
the batfiles were intended to accomplish. It appears to me that they
don't help access the Cygwin Viewers, so they must do something
else. I mistakenly thought they were to enable the Viewers. I was hazy
about how it was to be done, I suspected it was native windows, but
n

Re: No VIEW->DVI in LyX Win32 Works!

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Tuesday, March 14, 2006 5:50 PM
Subject: Re: No VIEW->DVI in LyX Win32 Works!




I really appreciate the effort you put in stress-testing the software,
but my brain is really turning into guacamole trying to follow you ;-)



Never mind about the batfiles. I just saw what python.bat does
and I'm sure the other batfiles do something useful also which
I'll discover with some use. I have them in a good spot.

I have no more questions and I'm quite happy with Cygwin LyX140
and the added versatility it offers, all due to your persistent efforts.

Thanks for all the advice and a great CygLyX installer and Howto, 

Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:
 
  I have disinstalled the cygwin tetex packages as I use MikTeX and now
  I don't have a fast internet connection to try it personally. Perhaps
  you can help me in solving this problem? Please, put the following 5 lines
  in a file named test.ltx and then run the cygwin latex.exe on it
  (/bin/latex test.ltx):
 
  \nonstopmode\makeatletter
  \ifx\undefined\documentclass\else
   \message{ThisIsLaTeX2e}
  \fi
  \ at  at end
 
  After you have done it, please paste the output in your reply, such that
  I can have a look at it.
 
 
 Same result from Cygwin shell or Dos shell:
 
 Stephen at Primary /usr/share/texmf
 $ /bin/latex test.ltx
 This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 kpathsea: Running mktexfmt latex.fmt
 /usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
 fmtutil: config file `fmtutil.cnf' not found.
 I can't find the format file `latex.fmt'!

Stephen,

most probably your tetex installation is corrupted. Try reinstalling it.
In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin

latex.bat
88
@echo off
sh.exe -c 'latex %*'
exit
88

pdflatex.bat
88
@echo off
sh.exe -c 'pdflatex %*'
exit
88

python.bat
88
@echo off
sh.exe -c 'python %*'
exit
88

xdvi.bat
88
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
88

Everything works like a charm. The first time I tried View-Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Monday, March 13, 2006 11:30 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Enrico:  most probably your tetex installation is corrupted. Try 
reinstalling it.

In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin



SH: I did a fresh install of Cygwin because latex wasn't working and
I wanted to test the Cygwin Lyx installer that you uploaded. So this
time xpdf, xdvi(k), and latex work from the bash shell. Also I got

--

[EMAIL PROTECTED] /cygdrive/c/cygwin
$ latex test.ltx
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
file:line:error style messages enabled.
%-line parsing enabled.
entering extended mode
(./test.ltx
LaTeX2e 2003/12/01
Babel v3.8d and hyphenation patterns for american, french, german, 
ngerman,
bahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, 
esperanto,

estonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk,
polish, portuges, romanian, russian, serbian, slovak, slovene, spanish,
swedish, turkish, ukrainian, nohyphenation, loaded.

ThisIsLaTeX2e )
No pages of output.
Transcript written on test.log.

---

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.
lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow invalid Window parameter
I can use Windows ghostview, however.
- 


EF:If you have the cygwin X-server and want to have fun, launch the
X11 version of LyX (lyx-x11). Then, in a terminal window, type lyxclient
and hit the Enter key. Now, in the terminal window from which you
launched lyxclient (you do not have a prompt), try typing file-open
without the quotes...
To quit lyxclient type BYE: in the terminal window.
--

SH: That was fun and worked. ^




latex.bat
88
@echo off
sh.exe -c 'latex %*'
exit
88

pdflatex.bat
88
@echo off
sh.exe -c 'pdflatex %*'
exit
88

python.bat
88
@echo off
sh.exe -c 'python %*'
exit
88

xdvi.bat
88
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
88

Everything works like a charm. The first time I tried View-Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

--
Enrico




I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.

Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin

It was rather clever how you got the LyX installation files
and Aiksaurus to show up in the Cygwin setup, install from
directory. LyX installation is actually quite short if you start
with a working Cygwin installation. I'm going to stick with
the lyx-x11 startup. You must have spent a lot of time on
this and it is the best ever Cygwin installer for Windows.

Time for a vacation,
Stephen

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:
 
  I have disinstalled the cygwin tetex packages as I use MikTeX and now
  I don't have a fast internet connection to try it personally. Perhaps
  you can help me in solving this problem? Please, put the following 5 lines
  in a file named test.ltx and then run the cygwin latex.exe on it
  (/bin/latex test.ltx):
 
  \nonstopmode\makeatletter
  \ifx\undefined\documentclass\else
   \message{ThisIsLaTeX2e}
  \fi
  \ at  at end
 
  After you have done it, please paste the output in your reply, such that
  I can have a look at it.
 
 
 Same result from Cygwin shell or Dos shell:
 
 Stephen at Primary /usr/share/texmf
 $ /bin/latex test.ltx
 This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 kpathsea: Running mktexfmt latex.fmt
 /usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
 fmtutil: config file `fmtutil.cnf' not found.
 I can't find the format file `latex.fmt'!

Stephen,

most probably your tetex installation is corrupted. Try reinstalling it.
In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin

latex.bat
88
@echo off
sh.exe -c 'latex %*'
exit
88

pdflatex.bat
88
@echo off
sh.exe -c 'pdflatex %*'
exit
88

python.bat
88
@echo off
sh.exe -c 'python %*'
exit
88

xdvi.bat
88
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
88

Everything works like a charm. The first time I tried View-Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Monday, March 13, 2006 11:30 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Enrico:  most probably your tetex installation is corrupted. Try 
reinstalling it.

In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin



SH: I did a fresh install of Cygwin because latex wasn't working and
I wanted to test the Cygwin Lyx installer that you uploaded. So this
time xpdf, xdvi(k), and latex work from the bash shell. Also I got

--

[EMAIL PROTECTED] /cygdrive/c/cygwin
$ latex test.ltx
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
file:line:error style messages enabled.
%-line parsing enabled.
entering extended mode
(./test.ltx
LaTeX2e 2003/12/01
Babel v3.8d and hyphenation patterns for american, french, german, 
ngerman,
bahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, 
esperanto,

estonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk,
polish, portuges, romanian, russian, serbian, slovak, slovene, spanish,
swedish, turkish, ukrainian, nohyphenation, loaded.

ThisIsLaTeX2e )
No pages of output.
Transcript written on test.log.

---

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.
lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow invalid Window parameter
I can use Windows ghostview, however.
- 


EF:If you have the cygwin X-server and want to have fun, launch the
X11 version of LyX (lyx-x11). Then, in a terminal window, type lyxclient
and hit the Enter key. Now, in the terminal window from which you
launched lyxclient (you do not have a prompt), try typing file-open
without the quotes...
To quit lyxclient type BYE: in the terminal window.
--

SH: That was fun and worked. ^




latex.bat
88
@echo off
sh.exe -c 'latex %*'
exit
88

pdflatex.bat
88
@echo off
sh.exe -c 'pdflatex %*'
exit
88

python.bat
88
@echo off
sh.exe -c 'python %*'
exit
88

xdvi.bat
88
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
88

Everything works like a charm. The first time I tried View-Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

--
Enrico




I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.

Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin

It was rather clever how you got the LyX installation files
and Aiksaurus to show up in the Cygwin setup, install from
directory. LyX installation is actually quite short if you start
with a working Cygwin installation. I'm going to stick with
the lyx-x11 startup. You must have spent a lot of time on
this and it is the best ever Cygwin installer for Windows.

Time for a vacation,
Stephen

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:
 
> > I have disinstalled the cygwin tetex packages as I use MikTeX and now
> > I don't have a fast internet connection to try it personally. Perhaps
> > you can help me in solving this problem? Please, put the following 5 lines
> > in a file named test.ltx and then run the cygwin latex.exe on it
> > (/bin/latex test.ltx):
> >
> > \nonstopmode\makeatletter
> > \ifx\undefined\documentclass\else
> >  \message{ThisIsLaTeX2e}
> > \fi
> > \end
> >
> > After you have done it, please paste the output in your reply, such that
> > I can have a look at it.
> >
> 
> Same result from Cygwin shell or Dos shell:
> 
> Stephen  Primary /usr/share/texmf
> $ /bin/latex test.ltx
> This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
> kpathsea: Running mktexfmt latex.fmt
> /usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
> fmtutil: config file `fmtutil.cnf' not found.
> I can't find the format file `latex.fmt'!

Stephen,

most probably your tetex installation is corrupted. Try reinstalling it.
In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin

latex.bat
8<8<
@echo off
sh.exe -c 'latex %*'
exit
8<8<

pdflatex.bat
8<8<
@echo off
sh.exe -c 'pdflatex %*'
exit
8<8<

python.bat
8<8<
@echo off
sh.exe -c 'python %*'
exit
8<8<

xdvi.bat
8<8<
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
8<8<

Everything works like a charm. The first time I tried View->Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Monday, March 13, 2006 11:30 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen,

Enrico:  most probably your tetex installation is corrupted. Try 
reinstalling it.

In the meantime I've got a fast connection and tried to install again the
cygwin tetex packages. I can confirm that everything works fine with all
cygwin tools, but I had to put the following .bat files in ~\LyX\bin



SH: I did a fresh install of Cygwin because latex wasn't working and
I wanted to test the Cygwin Lyx installer that you uploaded. So this
time xpdf, xdvi(k), and latex work from the bash shell. Also I got

--

[EMAIL PROTECTED] /cygdrive/c/cygwin
$ latex test.ltx
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
file:line:error style messages enabled.
%&-line parsing enabled.
entering extended mode
(./test.ltx
LaTeX2e <2003/12/01>
Babel  and hyphenation patterns for american, french, german, 
ngerman,
bahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, 
esperanto,

estonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk,
polish, portuges, romanian, russian, serbian, slovak, slovene, spanish,
swedish, turkish, ukrainian, nohyphenation, loaded.

ThisIsLaTeX2e )
No pages of output.
Transcript written on test.log.

---

SH: So it seems to be working. The good news is that lyx-x11 works
pretty well. It displays Tex Information whereas lyx-winbin does not.
lyx-x11 also uses xpdf and xdvi(k) Ok. A Postscript file seems to be
made and the correct output quickly flashes on the screen but then
quits with the error message: winMultiWindowXMsgProcErrorHandler -
ERROR: BadWindow 
I can use Windows ghostview, however.
- 


EF:If you have the cygwin X-server and want to have fun, launch the
X11 version of LyX (lyx-x11). Then, in a terminal window, type lyxclient
and hit the Enter key. Now, in the terminal window from which you
launched lyxclient (you do not have a prompt), try typing "file-open"
without the quotes...
To quit lyxclient type "BYE:" in the terminal window.
--

SH: That was fun and worked. ^




latex.bat
8<8<
@echo off
sh.exe -c 'latex %*'
exit
8<8<

pdflatex.bat
8<8<
@echo off
sh.exe -c 'pdflatex %*'
exit
8<8<

python.bat
8<8<
@echo off
sh.exe -c 'python %*'
exit
8<8<

xdvi.bat
8<8<
@echo off
set DISPLAY=localhost:0.0
sh.exe -c 'xdvi %*'
exit
8<8<

Everything works like a charm. The first time I tried View->Dvi I had
the impression that LyX was hanging, but then I realized that I had
just installed tetex and it was simply busy in generating all the needed
fonts. So, the first time it took almost forever but then xdvi popped up
showing me the dvi.

In conclusion, cygwin helper apps can be used with the native version
of LyX but some of them must be called through a wrapper script. This
happens when either they are symlinks to the real apps or they are shell
scripts, or they need some environment variables to be set (like in the
xdvi case which both is a shell script and needs DISPLAY to be set).

I think I can say that if there is a problem using cygwin apps, this is
due to either a broken installation or misconfiguration.

--
Enrico




I can't use any Cygwin helper apps with lyx-winbin. They fail
with a 'can't open display' whether I have started Xwin or not.
I don't know if one of those batfiles written as a script would help.

Nor does lyx-1.3.7_win32_setup_v2 (which Chuck is using)
work with any Cygwin apps, with or without batfiles, with or
without startx for Cygwin. It works with Windows apps, as
expected, but what is the use of using Cygwin for LyX then?
I have them installed in C:\lyxcyg\bin

It was rather clever how you got the LyX installation files
and Aiksaurus to show up in the Cygwin setup, install from
directory. LyX installation is actually quite short if you start
with a working Cygwin installation. I'm going to stick with
the lyx-x11 startup. You must have spent a lot of time on
this and it is the best ever Cygwin installer for Windows.

Time for a vacation,
Stephen

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]

To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 12:34 AM
Subject: Re: No VIEW-DVI in LyX Win32



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)



You might need instead of  /usr/local/bin:/usr/bin:/usr/X11R6/bin:
/c /usr/local/bin:/c/usr/bin:/c/usr/X11R6/bin:

I am not sure where xdvi.bin is located, maybe under
/c/usr/share/texmf/xdvi 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 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.

Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir C:\Documents and Settings\UserName\Application Data\LyX140

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

C:\Program files\LyX-1.4.0\bin\lyx.exe -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.

 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 )

The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for paths.
With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and /).

The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 3:47 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:


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.


Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir C:\Documents and Settings\UserName\Application Data\LyX140

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

C:\Program files\LyX-1.4.0\bin\lyx.exe -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.



SH: This works and is so much easier it is even convenient!
I entered it on the Target line. Thanks!


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 )


The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for 
paths.

With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and 
/).




I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during sh configure to be not useable. So by
native LyX version, you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

--
Enrico



Well I noticed that latex.exe was rather small and there was a symlink
to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
useable. I noticed you put the new Cygwin LyX140 up for ftp download.

Regards,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks again for the quick response.  I'm flying to the west coast today 
so don't have time to consider your reply in detail right now.  Will look 
at it on the plane and try to answer your questions.

Cheers!

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
lyx-users@lists.lyx.org
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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: Stephen Harris [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 8:07 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Thanks again for the quick response.  I'm flying to the west coast today
so don't have time to consider your reply in detail right now.  Will look
at it on the plane and try to answer your questions.

Cheers!

Chuck



I tried to install that LyX137v2 binary using Cygwin helper apps.
Towards the end when sh configure from ~lyx/resources/lyx runs
I saw a latex.exe not useable message. If that can't be fixed then
quite a few things won't work. It has been raining heavily in Cal.

The rain in spain falls mainly in Santa Cruz,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I tested Chuck's method. He is not getting a DVI viewer because the
 latex.exe is found during sh configure to be not useable. So by
 native LyX version, you don't mean a binary, but that LyX can be
 compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
 The WinLyX binary install bombs for finding xpdf also.

This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
  \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.

Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: /bin/latex test.ltx
3) convert test.ltx to unix line endings with dos2unix text.ltx
4) redo the the check on the converted file: /bin/latex test.ltx

If the line endings style is the problem, the fix is almost trivial.

[...]
 Well I noticed that latex.exe was rather small and there was a symlink
 to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
 pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
 useable. I noticed you put the new Cygwin LyX140 up for ftp download.

No, that could not be the problem as configure was being executed by
the cygwin sh and in this context symlinks are understood. When you
run sh configure symlinks are ok, but when you run the native LyX, it
will not recognize latex.exe if it is a symlink (so, your move is correct).

Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 Well I noticed that latex.exe was rather small and there was a symlink
 to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
 pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
 useable.

A cleaner solution is the following. If programname.exe is a symlink to
a real binary program, then simply create a programname.bat file and put
it in the ~\LyX\bin directory. This directory is always searched first, and
thus when programname is invoked, programname.bat will be used.

The script programname.bat is the following 3 liner (simply replace
programname with the actual name of the program):

@echo off
sh.exe -c %*
exit

This works when the program is invoked without explicitely giving an
extension, i.e., programname arg1 ... instead of programname.exe arg1...,
as programname.bat is spotted first. Then, when sh is called to execute
the command, it will look for a program whose name is programname.exe and
will spot the right one. As sh understands symlinks, there is no problem
if programname.exe is a symlink. That's all.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:


2) The View/DVI menu entry is missing.

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


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.


I posted this before but didn't see a reply:  Is Edit-Preferences-File 
formats-DVI-Viewer set to xdvi, and is the path to xdvi (presumably 
the cygwin bin directory) included in Edit-Preferences-Paths-PATH 
prefix?  That should be all it takes.


/Paul

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 9:10 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:


I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during sh configure to be not useable. So by
native LyX version, you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
 \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.



Same result from Cygwin shell or Dos shell:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

---
same file but named testdos.ltx made from Notepad
[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!



Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: /bin/latex test.ltx
3) convert test.ltx to unix line endings with dos2unix text.ltx
4) redo the the check on the converted file: /bin/latex test.ltx

If the line endings style is the problem, the fix is almost trivial.



The results are the same testing from Cygwin shell and Dos shell
on test.ltx or testdos.ltx, converted by dos2unix or not:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

So I checked to see that I had fmtutil.cnf and latex.fmt. I did.
So I copied fmtutil.cnf into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. Same result as above.
Then I copied latex.fmt into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. This time I got a different result:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
---! Must increase the hyph_size
(Fatal format file error; I'm stymied)

Same result on the Notepad produced (identical) testdos.ltx from Dos.


Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

--
Enrico



Perhaps Chuck will comment on whether his system reports a useable latex.
Your file is still in Incoming, I suppose, I can't see it.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

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
lyx-users@lists.lyx.org
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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: Stephen Harris [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 10:03 PM
Subject: Re: No VIEW-DVI in LyX Win32



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.



Yap is a DVI viewer. I was showing my settings. I meant for you to
replace Yap with Xdvi, or if it was empty, to insert xdvi as your Viewer.
xdvi is a file in Cygwin and I suggested if there was a problem, to use
the full path to xdvi, something like 
(cygdrive)/c/cygwin/location/of/file/xdvi

modify,apply,save. Sometimes you have to Reconfigure. Like Paul said.


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.



During the installation it asks for gswin32c, used for ghostscript,
and that file is contained in a Windows distro of ghostscript, but
I didn't find that file in the Cygwin installation. Adobe Reader is
a Windows program and normally works with WinLyX137v2.
Likewise Ghostscript8.51 and Ghostgum. The pdf viewer that
comes with Cygwin is xpdf.


I will try to put together a how-to when (if) I get this working.

Thanks for the help.

Chuck



You are welcome, good luck. You made more progress than I did.
I think my Cygwin installation may be corrupted by old installations
and my Latex seems not to be working outside of LyX.

Regards,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]

To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 12:34 AM
Subject: Re: No VIEW-DVI in LyX Win32



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)



You might need instead of  /usr/local/bin:/usr/bin:/usr/X11R6/bin:
/c /usr/local/bin:/c/usr/bin:/c/usr/X11R6/bin:

I am not sure where xdvi.bin is located, maybe under
/c/usr/share/texmf/xdvi 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 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.

Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir C:\Documents and Settings\UserName\Application Data\LyX140

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

C:\Program files\LyX-1.4.0\bin\lyx.exe -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.

 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 )

The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for paths.
With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and /).

The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 3:47 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:


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.


Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir C:\Documents and Settings\UserName\Application Data\LyX140

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

C:\Program files\LyX-1.4.0\bin\lyx.exe -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.



SH: This works and is so much easier it is even convenient!
I entered it on the Target line. Thanks!


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 )


The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for 
paths.

With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and 
/).




I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during sh configure to be not useable. So by
native LyX version, you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

--
Enrico



Well I noticed that latex.exe was rather small and there was a symlink
to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
useable. I noticed you put the new Cygwin LyX140 up for ftp download.

Regards,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks again for the quick response.  I'm flying to the west coast today 
so don't have time to consider your reply in detail right now.  Will look 
at it on the plane and try to answer your questions.

Cheers!

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
lyx-users@lists.lyx.org
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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: Stephen Harris [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 8:07 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Thanks again for the quick response.  I'm flying to the west coast today
so don't have time to consider your reply in detail right now.  Will look
at it on the plane and try to answer your questions.

Cheers!

Chuck



I tried to install that LyX137v2 binary using Cygwin helper apps.
Towards the end when sh configure from ~lyx/resources/lyx runs
I saw a latex.exe not useable message. If that can't be fixed then
quite a few things won't work. It has been raining heavily in Cal.

The rain in spain falls mainly in Santa Cruz,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 I tested Chuck's method. He is not getting a DVI viewer because the
 latex.exe is found during sh configure to be not useable. So by
 native LyX version, you don't mean a binary, but that LyX can be
 compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
 The WinLyX binary install bombs for finding xpdf also.

This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
  \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.

Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: /bin/latex test.ltx
3) convert test.ltx to unix line endings with dos2unix text.ltx
4) redo the the check on the converted file: /bin/latex test.ltx

If the line endings style is the problem, the fix is almost trivial.

[...]
 Well I noticed that latex.exe was rather small and there was a symlink
 to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
 pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
 useable. I noticed you put the new Cygwin LyX140 up for ftp download.

No, that could not be the problem as configure was being executed by
the cygwin sh and in this context symlinks are understood. When you
run sh configure symlinks are ok, but when you run the native LyX, it
will not recognize latex.exe if it is a symlink (so, your move is correct).

Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris [EMAIL PROTECTED] writes:

 Well I noticed that latex.exe was rather small and there was a symlink
 to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
 pdfetex.exe to latex.exe but the binary LyX still found latex.exe not
 useable.

A cleaner solution is the following. If programname.exe is a symlink to
a real binary program, then simply create a programname.bat file and put
it in the ~\LyX\bin directory. This directory is always searched first, and
thus when programname is invoked, programname.bat will be used.

The script programname.bat is the following 3 liner (simply replace
programname with the actual name of the program):

@echo off
sh.exe -c %*
exit

This works when the program is invoked without explicitely giving an
extension, i.e., programname arg1 ... instead of programname.exe arg1...,
as programname.bat is spotted first. Then, when sh is called to execute
the command, it will look for a program whose name is programname.exe and
will spot the right one. As sh understands symlinks, there is no problem
if programname.exe is a symlink. That's all.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:


2) The View/DVI menu entry is missing.

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


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.


I posted this before but didn't see a reply:  Is Edit-Preferences-File 
formats-DVI-Viewer set to xdvi, and is the path to xdvi (presumably 
the cygwin bin directory) included in Edit-Preferences-Paths-PATH 
prefix?  That should be all it takes.


/Paul

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

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

To: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 9:10 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen Harris [EMAIL PROTECTED] writes:


I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during sh configure to be not useable. So by
native LyX version, you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
 \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.



Same result from Cygwin shell or Dos shell:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

---
same file but named testdos.ltx made from Notepad
[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!



Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: /bin/latex test.ltx
3) convert test.ltx to unix line endings with dos2unix text.ltx
4) redo the the check on the converted file: /bin/latex test.ltx

If the line endings style is the problem, the fix is almost trivial.



The results are the same testing from Cygwin shell and Dos shell
on test.ltx or testdos.ltx, converted by dos2unix or not:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

So I checked to see that I had fmtutil.cnf and latex.fmt. I did.
So I copied fmtutil.cnf into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. Same result as above.
Then I copied latex.fmt into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. This time I got a different result:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
---! Must increase the hyph_size
(Fatal format file error; I'm stymied)

Same result on the Notepad produced (identical) testdos.ltx from Dos.


Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

--
Enrico



Perhaps Chuck will comment on whether his system reports a useable latex.
Your file is still in Incoming, I suppose, I can't see it.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

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
lyx-users@lists.lyx.org
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: lyx-users@lists.lyx.org
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

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: Stephen Harris [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Sunday, March 12, 2006 10:03 PM
Subject: Re: No VIEW-DVI in LyX Win32



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.



Yap is a DVI viewer. I was showing my settings. I meant for you to
replace Yap with Xdvi, or if it was empty, to insert xdvi as your Viewer.
xdvi is a file in Cygwin and I suggested if there was a problem, to use
the full path to xdvi, something like 
(cygdrive)/c/cygwin/location/of/file/xdvi

modify,apply,save. Sometimes you have to Reconfigure. Like Paul said.


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.



During the installation it asks for gswin32c, used for ghostscript,
and that file is contained in a Windows distro of ghostscript, but
I didn't find that file in the Cygwin installation. Adobe Reader is
a Windows program and normally works with WinLyX137v2.
Likewise Ghostscript8.51 and Ghostgum. The pdf viewer that
comes with Cygwin is xpdf.


I will try to put together a how-to when (if) I get this working.

Thanks for the help.

Chuck



You are welcome, good luck. You made more progress than I did.
I think my Cygwin installation may be corrupted by old installations
and my Latex seems not to be working outside of LyX.

Regards,
Stephen 

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

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: <lyx-users@lists.lyx.org>
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 

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: "Stephen Harris" <[EMAIL PROTECTED]>

To: "Charles Schulz" <[EMAIL PROTECTED]>
Cc: <lyx-users@lists.lyx.org>
Sent: Sunday, March 12, 2006 12:34 AM
Subject: Re: No VIEW->DVI in LyX Win32



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)



You might need instead of  /usr/local/bin:/usr/bin:/usr/X11R6/bin:
/c /usr/local/bin:/c/usr/bin:/c/usr/X11R6/bin:

I am not sure where xdvi.bin is located, maybe under
/c/usr/share/texmf/xdvi 

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

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

Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir "C:\Documents and Settings\UserName\Application Data\LyX140"

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

"C:\Program files\LyX-1.4.0\bin\lyx.exe" -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.

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

The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for paths.
With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and /).

The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Sunday, March 12, 2006 3:47 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen Harris <[EMAIL PROTECTED]> writes:


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.


Stephen,

coexistence of both 1.3.7 and 1.4.0 on Windows is easier than on Linux
because the only conflict is the userdir. You can solve this only problem
simply renaming the 1.4.0 userdir as
C:\Documents and Settings\UserName\Application Data\LyX140
and then adding the following switch to your shortcuts or .bat files
invoking LyX 1.4.0:

-userdir "C:\Documents and Settings\UserName\Application Data\LyX140"

doing so, LyX will look there for its files. Try issuing the following
command from a terminal:

"C:\Program files\LyX-1.4.0\bin\lyx.exe" -userdir C:/MyLyX140dir

and you will see that LyX will even create C:/MyLyX140dir if it does
not exists, autoreconfiguring itself.



SH: This works and is so much easier it is even convenient!
I entered it on the Target line. Thanks!


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 )


The native LyX version can be used with all Cygwin apps. Whatever you
can do with a native app you can do the same and more with a Cygwin one.
For example, Cygwin apps understand both native and posix syntax for 
paths.

With a Cygwin app you can indifferently use C:\aspell\lib or C:/aspell/lib
or /cygdrive/c/aspell/lib or even C:\aspell/lib (note the mixup of \ and 
/).




I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during "sh configure" to be "not useable". So by
"native LyX version", you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


The only problem I face is when a Cygwin app is a symlink to a real
binary program, as in this case native (and even MSYS) apps do not
understand symlinks. The solution in this case is really simple: create
a .bat script with the same name which simply calls the real binary
program.

--
Enrico



Well I noticed that latex.exe was rather small and there was a symlink
to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
pdfetex.exe to latex.exe but the binary LyX still found latex.exe "not
useable". I noticed you put the new Cygwin LyX140 up for ftp download.

Regards,
Stephen 

Re: No VIEW->DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks again for the quick response.  I'm flying to the west coast today 
so don't have time to consider your reply in detail right now.  Will look 
at it on the plane and try to answer your questions.

Cheers!

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
<lyx-users@lists.lyx.org>
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: <lyx-users@lists.lyx.org>
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 p

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: "Charles Schulz" <[EMAIL PROTECTED]>

To: "Stephen Harris" <[EMAIL PROTECTED]>
Cc: <lyx-users@lists.lyx.org>
Sent: Sunday, March 12, 2006 8:07 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen,

Thanks again for the quick response.  I'm flying to the west coast today
so don't have time to consider your reply in detail right now.  Will look
at it on the plane and try to answer your questions.

Cheers!

Chuck



I tried to install that LyX137v2 binary using Cygwin helper apps.
Towards the end when "sh configure" from ~lyx/resources/lyx runs
I saw a latex.exe "not useable" message. If that can't be fixed then
quite a few things won't work. It has been raining heavily in Cal.

The rain in spain falls mainly in Santa Cruz,
Stephen 

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

> I tested Chuck's method. He is not getting a DVI viewer because the
> latex.exe is found during "sh configure" to be "not useable". So by
> "native LyX version", you don't mean a binary, but that LyX can be
> compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
> The WinLyX binary install bombs for finding xpdf also.

This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
  \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.

Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: "/bin/latex test.ltx"
3) convert test.ltx to unix line endings with "dos2unix text.ltx"
4) redo the the check on the converted file: "/bin/latex test.ltx"

If the line endings style is the problem, the fix is almost trivial.

[...]
> Well I noticed that latex.exe was rather small and there was a symlink
> to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
> pdfetex.exe to latex.exe but the binary LyX still found latex.exe "not
> useable". I noticed you put the new Cygwin LyX140 up for ftp download.

No, that could not be the problem as configure was being executed by
the cygwin sh and in this context symlinks are understood. When you
run "sh configure" symlinks are ok, but when you run the native LyX, it
will not recognize latex.exe if it is a symlink (so, your move is correct).

Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Stephen Harris <[EMAIL PROTECTED]> writes:

> Well I noticed that latex.exe was rather small and there was a symlink
> to pdfetex.exe. So I tried to tried deleting latex.exe and then copying
> pdfetex.exe to latex.exe but the binary LyX still found latex.exe "not
> useable".

A cleaner solution is the following. If programname.exe is a symlink to
a real binary program, then simply create a programname.bat file and put
it in the ~\LyX\bin directory. This directory is always searched first, and
thus when programname is invoked, programname.bat will be used.

The script programname.bat is the following 3 liner (simply replace
programname with the actual name of the program):

@echo off
sh.exe -c %*
exit

This works when the program is invoked without explicitely giving an
extension, i.e., "programname arg1 ..." instead of "programname.exe arg1...",
as programname.bat is spotted first. Then, when sh is called to execute
the command, it will look for a program whose name is programname.exe and
will spot the right one. As sh understands symlinks, there is no problem
if programname.exe is a symlink. That's all.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:


2) The View/DVI menu entry is missing.

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


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.


I posted this before but didn't see a reply:  Is Edit->Preferences->File 
formats->DVI->Viewer set to xdvi, and is the path to xdvi (presumably 
the cygwin bin directory) included in Edit->Preferences->Paths->PATH 
prefix?  That should be all it takes.


/Paul

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

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

To: <lyx-users@lists.lyx.org>
Sent: Sunday, March 12, 2006 9:10 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen Harris <[EMAIL PROTECTED]> writes:


I tested Chuck's method. He is not getting a DVI viewer because the
latex.exe is found during "sh configure" to be "not useable". So by
"native LyX version", you don't mean a binary, but that LyX can be
compiled under Cygwin to use Qt3 and Cygwin LyX helpers?
The WinLyX binary install bombs for finding xpdf also.


This is ridiculous ... here the configure script is trying to ascertain
if the latex.exe is version 2e, which obviously the cygwin version is,
but it fails to recognize it. This means that the check for latex2e in
configure must be changed accordingly.

I have disinstalled the cygwin tetex packages as I use MikTeX and now
I don't have a fast internet connection to try it personally. Perhaps
you can help me in solving this problem? Please, put the following 5 lines
in a file named test.ltx and then run the cygwin latex.exe on it
(/bin/latex test.ltx):

\nonstopmode\makeatletter
\ifx\undefined\documentclass\else
 \message{ThisIsLaTeX2e}
\fi
\@@end

After you have done it, please paste the output in your reply, such that
I can have a look at it.



Same result from Cygwin shell or Dos shell:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

---
same file but named testdos.ltx made from Notepad
[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!



Another point which may be important is that the configure script has
DOS style line endings and this can be the reason for the failed test.
So, proceed in this way:
1) Use notepad (not a cygwin text editor) to create test.ltx
2) perform the check from a cygwin shell: "/bin/latex test.ltx"
3) convert test.ltx to unix line endings with "dos2unix text.ltx"
4) redo the the check on the converted file: "/bin/latex test.ltx"

If the line endings style is the problem, the fix is almost trivial.



The results are the same testing from Cygwin shell and Dos shell
on test.ltx or testdos.ltx, converted by dos2unix or not:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex testdos.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea: Running mktexfmt latex.fmt
/usr/bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `latex.fmt'!

So I checked to see that I had fmtutil.cnf and latex.fmt. I did.
So I copied fmtutil.cnf into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. Same result as above.
Then I copied latex.fmt into the /usr/share/texmf directory and
tried /bin/latex test.ltx again. This time I got a different result:

[EMAIL PROTECTED] /usr/share/texmf
$ /bin/latex test.ltx
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
---! Must increase the hyph_size
(Fatal format file error; I'm stymied)

Same result on the Notepad produced (identical) testdos.ltx from Dos.


Yes, I have uploaded a cygwin package for LyX 1.4.0 to
ftp.devel.lyx.org/pub/incoming but it is not downloadable from there,
so someone must move it to a suitable place.

--
Enrico



Perhaps Chuck will comment on whether his system reports a "useable latex".
Your file is still in Incoming, I suppose, I can't see it.

Regards,
Stephen

Re: No VIEW->DVI in LyX Win32

[Charles Schulz]

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
<lyx-users@lists.lyx.org>
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: <lyx-users@lists.lyx.org>
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/mikt

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: "Charles Schulz" <[EMAIL PROTECTED]>

To: "Stephen Harris" <[EMAIL PROTECTED]>
Cc: <lyx-users@lists.lyx.org>
Sent: Sunday, March 12, 2006 10:03 PM
Subject: Re: No VIEW->DVI in LyX Win32



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



Yap is a DVI viewer. I was showing my settings. I meant for you to
replace Yap with Xdvi, or if it was empty, to insert xdvi as your Viewer.
xdvi is a file in Cygwin and I suggested if there was a problem, to use
the full path to xdvi, something like 
(cygdrive)/c/cygwin/location/of/file/xdvi

modify,apply,save. Sometimes you have to Reconfigure. Like Paul said.


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.



During the installation it asks for gswin32c, used for ghostscript,
and that file is contained in a Windows distro of ghostscript, but
I didn't find that file in the Cygwin installation. Adobe Reader is
a Windows program and normally works with WinLyX137v2.
Likewise Ghostscript8.51 and Ghostgum. The pdf viewer that
comes with Cygwin is xpdf.


I will try to put together a how-to when (if) I get this working.

Thanks for the help.

Chuck



You are welcome, good luck. You made more progress than I did.
I think my Cygwin installation may be corrupted by old installations
and my Latex seems not to be working outside of LyX.

Regards,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
 I'd assumed that this was because it couldn't find the DVI convert 
helper.  And this because I either don't have the needed helper on my 
system, or I messed up when configuring the system.  I've spent some time 
trying to hack the configuration files to try to get LyX to link to xdvi 
with no success.  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?.  I guess the response I was expecting to the inquiry was 
something like LyX Win32 is built assuming DVI renderer xxx.  You need to 
get xxx from yyy and make LyX aware of it by zzz.

So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log 
into qtwin as anonymous.  So I down loaded the source from the sourceforge 
web site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't 
of interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.
Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a 
reply to your note.

Is there a simple path to getting the DVI rendering working which 
doesn't require rebuilding LyX and qt3?

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/10/2006 03:40 PM
Please respond to
Stephen Harris


To
lyx-users@lists.lyx.org, Charles Schulz/Watson/[EMAIL PROTECTED]
cc

Subject
Re: No VIEW-DVI in LyX Win32







- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW-DVI in LyX Win32


I have installed LyX Win32 on an XP machine including cygwin.  I chose to
 get all the necessary prerequisite stuff through cygwin rather than 
having
 the install script download it (they all end up in $cygwin/bin).  I have
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path. When
 I try going through the tutorial and follow the My first LyX document!
 example, I'm hung up at producing a DVI version since there is not
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

 Any help will be greatly appreciated.

 Chuck


Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz

To: Stephen Harris
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 3:19 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
I'd assumed that this was because it couldn't find the DVI convert helper. 
And this because I either don't have the needed helper on my system, or I 
messed up when configuring the system.  I've spent some time trying to hack 
the configuration files to try to get LyX to link to xdvi with no success. 
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?.  I guess the response 
I was expecting to the inquiry was something like LyX Win32 is built 
assuming DVI renderer xxx.  You need to get xxx from yyy and make LyX aware 
of it by zzz.


So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log into 
qtwin as anonymous.  So I down loaded the source from the sourceforge web 
site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't of 
interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.

Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a reply 
to your note.


Is there a simple path to getting the DVI rendering working which doesn't 
require rebuilding LyX and qt3?


Chuck
---

There used to be a LyX version built for Cygwin and you could download
and install it like Tetex or other Cygwin programs along with dependencies.

The Cygwin LyX was removed from the download programs months ago,
which made me speculate on what/where you got your LyX version, because
http://www.cygwin.com/

What Isn't Cygwin?
* Cygwin is not a way to run native linux apps on Windows. You have to 
rebuild

your application from source if you want it to run on Windows.

* Cygwin is not a way to magically make native Windows apps aware of UNIX 
functionality, like signals, ptys, etc. Again, you need to build your apps 
from source

if you want to take advantage of Cygwin functionality.
-

So I've used Claus Hentschel's port to Cygwin. But I see he has taken down 
his
instructions. Also Cygwin LyX and recently Enrico's method to install Cygwin 
LyX.
I had misgivings about your method but am not an authority. Cygwin LyX is 
very
rarely used and I only know of two experts. I've never seen a prior problem 
like

your reported for Cygwin.

The instructions are for using Msys which has its own versions of sh.exe and
sed.exe which are used for executing scripts and I've seen LyX installations 
for

native windows LyX fail because Cygwin was before Msys in the path and the
wrong versions of either/or sh.exe or sed.exe were invoked.

I don't know if that is a factor in the reverse situation. I think Enrico 
mentioned

Python and a symlink because I _think_ there is a Python script which reads
the Tetex or Miktex directory and populates Tex Information. And also I
think an sh script that sets up your Viewers and Path_prefix. The recent LyX
versions use Qt3 and are called native Windows versions, they don't use X11.

There is no assumption made that they will work on Cygwin and you will find
nothing in the documentation that says they can. ImageMagick is a LyX helper
program. When I recently built LyX140x using Enrico's instructions I had the
Cygwin version installed and the Windows version of ImageMagick installed.
I had to remove the Cygwin version in order for the Windows version to work.
I don't mean that Cygwin's version wouldn't work with Cygwin. So I gathered
that you might have installed Windows versions of programs that were not
compiled for Cygwin. I haven't seen this recommended in print. Sometimes
one encounters subtle conflicts with paths with spaces, a semi-colon 
delimiter

vs a colon delimiter and forward slashes vs. backward slashes.

Anyway, this is the long answer which boils down to I haven't seen your
approach supported in print. Therefore there is no documented way to
troubleshoot this problem. I don't think it is an exact analogy of the 
problem

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]

To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW-DVI in LyX Win32

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




They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using

Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros run 
on Windows/Cygwin

and that some features or all features would work of an incompatible binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:
 
 Is there a simple path to getting the DVI rendering working which 
 doesn't require rebuilding LyX and qt3?

I am currently putting together a cygwin package for LyX. When finished,
I'll upload it to a public place for downloads. If you are interested in
using cygwin tools (xdvi, in particular) you will be glad to know that I
am packaging two flavors of LyX, one using the native GUI and the other X11.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

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.

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

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.

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.

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

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/11/2006 12:49 PM
Please respond to
Stephen Harris


To
Charles Schulz/Watson/[EMAIL PROTECTED]
cc
lyx-users@lists.lyx.org
Subject
Re: No VIEW-DVI in LyX Win32







- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]
To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW-DVI in LyX Win32

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



They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use 
X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using
Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros 
run 
on Windows/Cygwin
and that some features or all features would work of an incompatible 
binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:

 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.

LyX looks for the following programs xdvi windvi yap kdvi in that order.
It simply checks that an executable named like that exists in the PATH and
it picks up the first one it finds.

The results are then stored in ~\LyX\Resources\lyx\lyxrc.defaults where
a line

\viewer dvi xdvi

is put *if* xdvi is spotted. If your xdvi is not found, than either it is not
seen as an executable or it is not in your PATH.

If from a terminal you do

   cd C:/Program files/LyX/Resources/lyx
   sh configure

you can follow the entire process, and if you scroll back the window you
can see when it is looking for xdvi. If it is not found, you would see
other checks for windvi, yap, and kdvi.

HTH

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
 I'd assumed that this was because it couldn't find the DVI convert 
helper.  And this because I either don't have the needed helper on my 
system, or I messed up when configuring the system.  I've spent some time 
trying to hack the configuration files to try to get LyX to link to xdvi 
with no success.  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?.  I guess the response I was expecting to the inquiry was 
something like LyX Win32 is built assuming DVI renderer xxx.  You need to 
get xxx from yyy and make LyX aware of it by zzz.

So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log 
into qtwin as anonymous.  So I down loaded the source from the sourceforge 
web site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't 
of interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.
Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a 
reply to your note.

Is there a simple path to getting the DVI rendering working which 
doesn't require rebuilding LyX and qt3?

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/10/2006 03:40 PM
Please respond to
Stephen Harris


To
lyx-users@lists.lyx.org, Charles Schulz/Watson/[EMAIL PROTECTED]
cc

Subject
Re: No VIEW-DVI in LyX Win32







- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW-DVI in LyX Win32


I have installed LyX Win32 on an XP machine including cygwin.  I chose to
 get all the necessary prerequisite stuff through cygwin rather than 
having
 the install script download it (they all end up in $cygwin/bin).  I have
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path. When
 I try going through the tutorial and follow the My first LyX document!
 example, I'm hung up at producing a DVI version since there is not
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

 Any help will be greatly appreciated.

 Chuck


Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz

To: Stephen Harris
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 3:19 AM
Subject: Re: No VIEW-DVI in LyX Win32



Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
I'd assumed that this was because it couldn't find the DVI convert helper. 
And this because I either don't have the needed helper on my system, or I 
messed up when configuring the system.  I've spent some time trying to hack 
the configuration files to try to get LyX to link to xdvi with no success. 
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?.  I guess the response 
I was expecting to the inquiry was something like LyX Win32 is built 
assuming DVI renderer xxx.  You need to get xxx from yyy and make LyX aware 
of it by zzz.


So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log into 
qtwin as anonymous.  So I down loaded the source from the sourceforge web 
site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't of 
interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.

Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a reply 
to your note.


Is there a simple path to getting the DVI rendering working which doesn't 
require rebuilding LyX and qt3?


Chuck
---

There used to be a LyX version built for Cygwin and you could download
and install it like Tetex or other Cygwin programs along with dependencies.

The Cygwin LyX was removed from the download programs months ago,
which made me speculate on what/where you got your LyX version, because
http://www.cygwin.com/

What Isn't Cygwin?
* Cygwin is not a way to run native linux apps on Windows. You have to 
rebuild

your application from source if you want it to run on Windows.

* Cygwin is not a way to magically make native Windows apps aware of UNIX 
functionality, like signals, ptys, etc. Again, you need to build your apps 
from source

if you want to take advantage of Cygwin functionality.
-

So I've used Claus Hentschel's port to Cygwin. But I see he has taken down 
his
instructions. Also Cygwin LyX and recently Enrico's method to install Cygwin 
LyX.
I had misgivings about your method but am not an authority. Cygwin LyX is 
very
rarely used and I only know of two experts. I've never seen a prior problem 
like

your reported for Cygwin.

The instructions are for using Msys which has its own versions of sh.exe and
sed.exe which are used for executing scripts and I've seen LyX installations 
for

native windows LyX fail because Cygwin was before Msys in the path and the
wrong versions of either/or sh.exe or sed.exe were invoked.

I don't know if that is a factor in the reverse situation. I think Enrico 
mentioned

Python and a symlink because I _think_ there is a Python script which reads
the Tetex or Miktex directory and populates Tex Information. And also I
think an sh script that sets up your Viewers and Path_prefix. The recent LyX
versions use Qt3 and are called native Windows versions, they don't use X11.

There is no assumption made that they will work on Cygwin and you will find
nothing in the documentation that says they can. ImageMagick is a LyX helper
program. When I recently built LyX140x using Enrico's instructions I had the
Cygwin version installed and the Windows version of ImageMagick installed.
I had to remove the Cygwin version in order for the Windows version to work.
I don't mean that Cygwin's version wouldn't work with Cygwin. So I gathered
that you might have installed Windows versions of programs that were not
compiled for Cygwin. I haven't seen this recommended in print. Sometimes
one encounters subtle conflicts with paths with spaces, a semi-colon 
delimiter

vs a colon delimiter and forward slashes vs. backward slashes.

Anyway, this is the long answer which boils down to I haven't seen your
approach supported in print. Therefore there is no documented way to
troubleshoot this problem. I don't think it is an exact analogy of the 
problem

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]

To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW-DVI in LyX Win32

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




They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using

Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros run 
on Windows/Cygwin

and that some features or all features would work of an incompatible binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:
 
 Is there a simple path to getting the DVI rendering working which 
 doesn't require rebuilding LyX and qt3?

I am currently putting together a cygwin package for LyX. When finished,
I'll upload it to a public place for downloads. If you are interested in
using cygwin tools (xdvi, in particular) you will be glad to know that I
am packaging two flavors of LyX, one using the native GUI and the other X11.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Charles Schulz]

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.

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

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.

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.

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

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/11/2006 12:49 PM
Please respond to
Stephen Harris


To
Charles Schulz/Watson/[EMAIL PROTECTED]
cc
lyx-users@lists.lyx.org
Subject
Re: No VIEW-DVI in LyX Win32







- Original Message - 
From: Stephen Harris [EMAIL PROTECTED]
To: Charles Schulz [EMAIL PROTECTED]
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW-DVI in LyX Win32

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



They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use 
X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using
Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros 
run 
on Windows/Cygwin
and that some features or all features would work of an incompatible 
binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:

 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.

LyX looks for the following programs xdvi windvi yap kdvi in that order.
It simply checks that an executable named like that exists in the PATH and
it picks up the first one it finds.

The results are then stored in ~\LyX\Resources\lyx\lyxrc.defaults where
a line

\viewer dvi xdvi

is put *if* xdvi is spotted. If your xdvi is not found, than either it is not
seen as an executable or it is not in your PATH.

If from a terminal you do

   cd C:/Program files/LyX/Resources/lyx
   sh configure

you can follow the entire process, and if you scroll back the window you
can see when it is looking for xdvi. If it is not found, you would see
other checks for windvi, yap, and kdvi.

HTH

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Charles Schulz]

Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
 I'd assumed that this was because it couldn't find the DVI convert 
helper.  And this because I either don't have the needed helper on my 
system, or I messed up when configuring the system.  I've spent some time 
trying to hack the configuration files to try to get LyX to link to xdvi 
with no success.  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?".  I guess the response I was expecting to the inquiry was 
something like "LyX Win32 is built assuming DVI renderer xxx.  You need to 
get xxx from yyy and make LyX aware of it by zzz."

So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log 
into qtwin as anonymous.  So I down loaded the source from the sourceforge 
web site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't 
of interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.
Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a 
reply to your note.

Is there a "simple" path to getting the DVI rendering working which 
doesn't require rebuilding LyX and qt3?

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/10/2006 03:40 PM
Please respond to
"Stephen Harris"


To
<lyx-users@lists.lyx.org>, Charles Schulz/Watson/[EMAIL PROTECTED]
cc

Subject
Re: No VIEW->DVI in LyX Win32







- Original Message - 
From: "Charles Schulz" <[EMAIL PROTECTED]>
To: <lyx-users@lists.lyx.org>
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW->DVI in LyX Win32


>I have installed LyX Win32 on an XP machine including cygwin.  I chose to
> get all the necessary prerequisite stuff through cygwin rather than 
having
> the install script download it (they all end up in $cygwin/bin).  I have
> added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path. When
> I try going through the tutorial and follow the "My first LyX document!"
> example, I'm hung up at producing a DVI version since there is not
> VIEW->DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
> checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.
>
> Any help will be greatly appreciated.
>
> Chuck
>

Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz

To: Stephen Harris
Cc: lyx-users@lists.lyx.org
Sent: Saturday, March 11, 2006 3:19 AM
Subject: Re: No VIEW->DVI in LyX Win32



Stephen,

Thanks for the reply.  However, I'm somewhat confused.  My current 
installation of LyX works just fine except I don't have the DVI rendering. 
I'd assumed that this was because it couldn't find the DVI convert helper. 
And this because I either don't have the needed helper on my system, or I 
messed up when configuring the system.  I've spent some time trying to hack 
the configuration files to try to get LyX to link to xdvi with no success. 
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?".  I guess the response 
I was expecting to the inquiry was something like "LyX Win32 is built 
assuming DVI renderer xxx.  You need to get xxx from yyy and make LyX aware 
of it by zzz."


So I tried Enrico's instructions first and ran into the following issues:
The sourceforge cvs repository seems to be broken.  It won't let me log into 
qtwin as anonymous.  So I down loaded the source from the sourceforge web 
site, noticing that this was qt-3 not qt3.
The patch file mostly works except for some #includes in one file which I 
fixed up, and an #ifdef associated with multi head monitors which aren't of 
interest to me anyway.
Make fails because undeclared function wcsncpy in qprinter_win.cpp.  Also 
warns about /* within a comment so I'm guessing that this is a result of 
another patch incompatibility.  Note: the patch file does not touch 
qprint_win.cpp.

Gave up on this path.

Looked at Kayvan's suggestions for X11 build of LyX 1.4 which requires a 
down level of the gcc compiler and asked myself if I wanted to start down 
another path which will probably have problems and decided to write a reply 
to your note.


Is there a "simple" path to getting the DVI rendering working which doesn't 
require rebuilding LyX and qt3?


Chuck
---

There used to be a LyX version built for Cygwin and you could download
and install it like Tetex or other Cygwin programs along with dependencies.

The Cygwin LyX was removed from the download programs months ago,
which made me speculate on what/where you got your LyX version, because
http://www.cygwin.com/

What Isn't Cygwin?
* "Cygwin is not a way to run native linux apps on Windows. You have to 
rebuild

your application from source if you want it to run on Windows.

* Cygwin is not a way to magically make native Windows apps aware of UNIX 
functionality, like signals, ptys, etc. Again, you need to build your apps 
from source

if you want to take advantage of Cygwin functionality."
-

So I've used Claus Hentschel's port to Cygwin. But I see he has taken down 
his
instructions. Also Cygwin LyX and recently Enrico's method to install Cygwin 
LyX.
I had misgivings about your method but am not an authority. Cygwin LyX is 
very
rarely used and I only know of two experts. I've never seen a prior problem 
like

your reported for Cygwin.

The instructions are for using Msys which has its own versions of sh.exe and
sed.exe which are used for executing scripts and I've seen LyX installations 
for

native windows LyX fail because Cygwin was before Msys in the path and the
wrong versions of either/or sh.exe or sed.exe were invoked.

I don't know if that is a factor in the reverse situation. I think Enrico 
mentioned

Python and a symlink because I _think_ there is a Python script which reads
the Tetex or Miktex directory and populates Tex Information. And also I
think an sh script that sets up your Viewers and Path_prefix. The recent LyX
versions use Qt3 and are called native Windows versions, they don't use X11.

There is no assumption made that they will work on Cygwin and you will find
nothing in the documentation that says they can. ImageMagick is a LyX helper
program. When I recently built LyX140x using Enrico's instructions I had the
Cygwin version installed and the Windows version of ImageMagick installed.
I had to remove the Cygwin version in order for the Windows version to work.
I don't mean that Cygwin's version wouldn't work with Cygwin. So I gathered
that you might have installed Windows versions of programs that were not
compiled for Cygwin. I haven't seen this recommended in print. Sometimes
one encounters subtle conflicts with paths with spaces, a semi-colon 
delimiter

vs a colon delimiter and forward slashes vs. backward slashes.

Anyway, this is the long answer which boils down to I haven't seen your
approach supported in print. Therefore there is no documented way to
troubleshoot this pr

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: "Stephen Harris" <[EMAIL PROTECTED]>

To: "Charles Schulz" <[EMAIL PROTECTED]>
Cc: <lyx-users@lists.lyx.org>
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW->DVI in LyX Win32


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




They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using

Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros run 
on Windows/Cygwin

and that some features or all features would work of an incompatible binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz <[EMAIL PROTECTED]> writes:
 
> Is there a "simple" path to getting the DVI rendering working which 
> doesn't require rebuilding LyX and qt3?

I am currently putting together a cygwin package for LyX. When finished,
I'll upload it to a public place for downloads. If you are interested in
using cygwin tools (xdvi, in particular) you will be glad to know that I
am packaging two flavors of LyX, one using the native GUI and the other X11.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Charles Schulz]

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.

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

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.

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.

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

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/11/2006 12:49 PM
Please respond to
"Stephen Harris"


To
Charles Schulz/Watson/[EMAIL PROTECTED]
cc
<lyx-users@lists.lyx.org>
Subject
Re: No VIEW->DVI in LyX Win32







- Original Message - 
From: "Stephen Harris" <[EMAIL PROTECTED]>
To: "Charles Schulz" <[EMAIL PROTECTED]>
Cc: <lyx-users@lists.lyx.org>
Sent: Saturday, March 11, 2006 8:28 AM
Subject: Re: No VIEW->DVI in LyX Win32


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



They wouldn't. Where and what binary distribution did you find intended to
be installed with Cygwin? The current Windows binary versions don't use 
X11.
I've not hear of a Linux binary that works (like an rpm). That would be 
handy,
as from time to time people ask about the possibility of installing LyX 
using
Cygwin. The Cygwin LyX X11 version for Windows needs to be built. I
don't think the Cygwin Tetex latex.exe is compatible with the Miktex 
latex.exe.
I tried to use Xemtex (another distro) latex.exe with LyX and I got an 
error.
I think any binary distro built for Cygwin would have the capability of 
running the tutorial. That is not the same as saying all binary distros 
run 
on Windows/Cygwin
and that some features or all features would work of an incompatible 
binary.

There is almost always a Readme which tells which platforms are supported
at the website where you download the binary. Did it say Cygwin? I think
the assumption you are making is more likely your uninvestigated surmise.

Keep it simple,
Stephen 

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz <[EMAIL PROTECTED]> writes:

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

LyX looks for the following programs "xdvi windvi yap kdvi" in that order.
It simply checks that an executable named like that exists in the PATH and
it picks up the first one it finds.

The results are then stored in ~\LyX\Resources\lyx\lyxrc.defaults where
a line

\viewer dvi "xdvi"

is put *if* xdvi is spotted. If your xdvi is not found, than either it is not
seen as an executable or it is not in your PATH.

If from a terminal you do

   cd "C:/Program files/LyX/Resources/lyx"
   sh configure

you can follow the entire process, and if you scroll back the window you
can see when it is looking for xdvi. If it is not found, you would see
other checks for windvi, yap, and kdvi.

HTH

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW-DVI in LyX Win32



I have installed LyX Win32 on an XP machine including cygwin.  I chose to
get all the necessary prerequisite stuff through cygwin rather than having
the install script download it (they all end up in $cygwin/bin).  I  have
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
I try going through the tutorial and follow the My first LyX document!
example, I'm hung up at producing a DVI version since there is not
VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

Any help will be greatly appreciated.

Chuck



Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:
I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
get all the necessary prerequisite stuff through cygwin rather than having 
the install script download it (they all end up in $cygwin/bin).  I  have 
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
I try going through the tutorial and follow the My first LyX document! 
example, I'm hung up at producing a DVI version since there is not 
VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.


Any help will be greatly appreciated.

Chuck

If self-replicating chemicals had as hard a time reaching maturity as good 
ideas, this planet would still be lifeless. Robert Qualkinbush




I'm assuming here that you installed 1.3.7 and not the preliminary 
version of 1.4.0.


Does LyX know that xdvi is your viewer of choice?  Go to 
Edit-Preferences-File formats, highlight DVI, and if necessary add 
xdvi to the Viewer field.  (You should also do the same for the DraftDVI 
format, which is DVI minus the pretty pictures.)  After filling in the 
Viewer field, click Modify and then Save.


If that doesn't get DVI (and DraftDVI) onto the View menu, we can plumb 
deeper.


/Paul

Re: No VIEW-DVI in LyX Win32

[Wolfram Heider]

Am Freitag, 10. März 2006 16:55 schrieb Charles Schulz:
 I have installed LyX Win32 on an XP machine including cygwin.  I chose to
 get all the necessary prerequisite stuff through cygwin rather than having
 the install script download it (they all end up in $cygwin/bin).  I  have
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
 I try going through the tutorial and follow the My first LyX document!
 example, I'm hung up at producing a DVI version since there is not
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

 Any help will be greatly appreciated.

 Chuck

 If self-replicating chemicals had as hard a time reaching maturity as good
 ideas, this planet would still be lifeless. Robert Qualkinbush


Maybe, you will have to reconfigure via the tools-menu and then restart lyx.

Wolfram Heider

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:
 
 I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
 get all the necessary prerequisite stuff through cygwin rather than having 
 the install script download it (they all end up in $cygwin/bin).  I  have 
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
 I try going through the tutorial and follow the My first LyX document! 
 example, I'm hung up at producing a DVI version since there is not 
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

If you mean the Windows system PATH then you should use the native
syntax, i.e., you should add C:\cygwin\bin and C:\cygwin\usr\X11R6\bin
to the environment (change C:\cygwin with your actual cygwin root path).

However, I suggest that you use the PATH prefix method.
In Edit-Preferences-Paths (or Tools-Preferences-Paths in 1.4.0) add
cygwin_root\bin and cygwin_root\usr\X11R6\bin to PATH prefix,
replacing cygwin_root with whatever appropriate in your case (most
probably C:\cygwin). Remember to use ; as a path separator and then
reconfigure LyX.

If you run LyX from a terminal, you can monitor the procedure and will
see if xdvi is spotted.

A last note: If you use python from cygwin, be warned that python.exe
is a symlink to the real python and native Windows programs do not
understand symlinks. For example in my case I have:

$ ls -l /bin/python.exe
lrwxrwxrwx 1 ef users 13 Dec  9 04:20 /bin/python.exe - python2.4.exe

so I use the following python.bat script (put it in ~\LyX\bin)

888
@echo off
python2.4 %*
exit
888

Needless to say that all of this only applies to a native LyX version.

-- 
Enrico

Re: No VIEW-DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: Charles Schulz [EMAIL PROTECTED]

To: lyx-users@lists.lyx.org
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW-DVI in LyX Win32



I have installed LyX Win32 on an XP machine including cygwin.  I chose to
get all the necessary prerequisite stuff through cygwin rather than having
the install script download it (they all end up in $cygwin/bin).  I  have
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
I try going through the tutorial and follow the My first LyX document!
example, I'm hung up at producing a DVI version since there is not
VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

Any help will be greatly appreciated.

Chuck



Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW-DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:
I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
get all the necessary prerequisite stuff through cygwin rather than having 
the install script download it (they all end up in $cygwin/bin).  I  have 
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
I try going through the tutorial and follow the My first LyX document! 
example, I'm hung up at producing a DVI version since there is not 
VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.


Any help will be greatly appreciated.

Chuck

If self-replicating chemicals had as hard a time reaching maturity as good 
ideas, this planet would still be lifeless. Robert Qualkinbush




I'm assuming here that you installed 1.3.7 and not the preliminary 
version of 1.4.0.


Does LyX know that xdvi is your viewer of choice?  Go to 
Edit-Preferences-File formats, highlight DVI, and if necessary add 
xdvi to the Viewer field.  (You should also do the same for the DraftDVI 
format, which is DVI minus the pretty pictures.)  After filling in the 
Viewer field, click Modify and then Save.


If that doesn't get DVI (and DraftDVI) onto the View menu, we can plumb 
deeper.


/Paul

Re: No VIEW-DVI in LyX Win32

[Wolfram Heider]

Am Freitag, 10. März 2006 16:55 schrieb Charles Schulz:
 I have installed LyX Win32 on an XP machine including cygwin.  I chose to
 get all the necessary prerequisite stuff through cygwin rather than having
 the install script download it (they all end up in $cygwin/bin).  I  have
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
 I try going through the tutorial and follow the My first LyX document!
 example, I'm hung up at producing a DVI version since there is not
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

 Any help will be greatly appreciated.

 Chuck

 If self-replicating chemicals had as hard a time reaching maturity as good
 ideas, this planet would still be lifeless. Robert Qualkinbush


Maybe, you will have to reconfigure via the tools-menu and then restart lyx.

Wolfram Heider

Re: No VIEW-DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz [EMAIL PROTECTED] writes:
 
 I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
 get all the necessary prerequisite stuff through cygwin rather than having 
 the install script download it (they all end up in $cygwin/bin).  I  have 
 added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
 I try going through the tutorial and follow the My first LyX document! 
 example, I'm hung up at producing a DVI version since there is not 
 VIEW-DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
 checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

If you mean the Windows system PATH then you should use the native
syntax, i.e., you should add C:\cygwin\bin and C:\cygwin\usr\X11R6\bin
to the environment (change C:\cygwin with your actual cygwin root path).

However, I suggest that you use the PATH prefix method.
In Edit-Preferences-Paths (or Tools-Preferences-Paths in 1.4.0) add
cygwin_root\bin and cygwin_root\usr\X11R6\bin to PATH prefix,
replacing cygwin_root with whatever appropriate in your case (most
probably C:\cygwin). Remember to use ; as a path separator and then
reconfigure LyX.

If you run LyX from a terminal, you can monitor the procedure and will
see if xdvi is spotted.

A last note: If you use python from cygwin, be warned that python.exe
is a symlink to the real python and native Windows programs do not
understand symlinks. For example in my case I have:

$ ls -l /bin/python.exe
lrwxrwxrwx 1 ef users 13 Dec  9 04:20 /bin/python.exe - python2.4.exe

so I use the following python.bat script (put it in ~\LyX\bin)

888
@echo off
python2.4 %*
exit
888

Needless to say that all of this only applies to a native LyX version.

-- 
Enrico

Re: No VIEW->DVI in LyX Win32

[Stephen Harris]

- Original Message - 
From: "Charles Schulz" <[EMAIL PROTECTED]>

To: 
Sent: Friday, March 10, 2006 7:55 AM
Subject: No VIEW->DVI in LyX Win32



I have installed LyX Win32 on an XP machine including cygwin.  I chose to
get all the necessary prerequisite stuff through cygwin rather than having
the install script download it (they all end up in $cygwin/bin).  I  have
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
I try going through the tutorial and follow the "My first LyX document!"
example, I'm hung up at producing a DVI version since there is not
VIEW->DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

Any help will be greatly appreciated.

Chuck



Enrico Forestieri wrote this Howto using Qt3.
He is active on this list so perhaps will see your post
and be more helpful. This approach worked out quite well.
http://wiki.lyx.org/LyX/LyXOnCygwin

SH: I asked Kayvan Sylvan about this (using X11) and he replied:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg45585.html
There is a make file included with that post.

Regards,
Stephen

Re: No VIEW->DVI in LyX Win32

[Paul A. Rubin]

Charles Schulz wrote:
I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
get all the necessary prerequisite stuff through cygwin rather than having 
the install script download it (they all end up in $cygwin/bin).  I  have 
added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
I try going through the tutorial and follow the "My first LyX document!" 
example, I'm hung up at producing a DVI version since there is not 
VIEW->DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.


Any help will be greatly appreciated.

Chuck

If self-replicating chemicals had as hard a time reaching maturity as good 
ideas, this planet would still be lifeless. Robert Qualkinbush




I'm assuming here that you installed 1.3.7 and not the preliminary 
version of 1.4.0.


Does LyX know that xdvi is your viewer of choice?  Go to 
Edit->Preferences->File formats, highlight DVI, and if necessary add 
xdvi to the Viewer field.  (You should also do the same for the DraftDVI 
format, which is DVI minus the pretty pictures.)  After filling in the 
Viewer field, click Modify and then Save.


If that doesn't get DVI (and DraftDVI) onto the View menu, we can plumb 
deeper.


/Paul

Re: No VIEW->DVI in LyX Win32

[Wolfram Heider]

Am Freitag, 10. März 2006 16:55 schrieb Charles Schulz:
> I have installed LyX Win32 on an XP machine including cygwin.  I chose to
> get all the necessary prerequisite stuff through cygwin rather than having
> the install script download it (they all end up in $cygwin/bin).  I  have
> added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When
> I try going through the tutorial and follow the "My first LyX document!"
> example, I'm hung up at producing a DVI version since there is not
> VIEW->DVI menu item.  It isn't greyed out, it just doesn't exist.  I've
> checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.
>
> Any help will be greatly appreciated.
>
> Chuck
>
> If self-replicating chemicals had as hard a time reaching maturity as good
> ideas, this planet would still be lifeless. Robert Qualkinbush


Maybe, you will have to reconfigure via the tools-menu and then restart lyx.

Wolfram Heider

Re: No VIEW->DVI in LyX Win32

[Enrico Forestieri]

Charles Schulz <[EMAIL PROTECTED]> writes:
> 
> I have installed LyX Win32 on an XP machine including cygwin.  I chose to 
> get all the necessary prerequisite stuff through cygwin rather than having 
> the install script download it (they all end up in $cygwin/bin).  I  have 
> added $cygwin/bin and $cygwin/usr/X11R6/bin to my environment path.  When 
> I try going through the tutorial and follow the "My first LyX document!" 
> example, I'm hung up at producing a DVI version since there is not 
> VIEW->DVI menu item.  It isn't greyed out, it just doesn't exist.  I've 
> checked that $cygwin/usr/X11R6/bin/xdvi.exe exists.

If you mean the Windows system PATH then you should use the native
syntax, i.e., you should add C:\cygwin\bin and C:\cygwin\usr\X11R6\bin
to the environment (change C:\cygwin with your actual cygwin root path).

However, I suggest that you use the PATH prefix method.
In Edit->Preferences->Paths (or Tools->Preferences->Paths in 1.4.0) add
\bin and \usr\X11R6\bin to PATH prefix,
replacing  with whatever appropriate in your case (most
probably C:\cygwin). Remember to use ; as a path separator and then
reconfigure LyX.

If you run LyX from a terminal, you can monitor the procedure and will
see if xdvi is spotted.

A last note: If you use python from cygwin, be warned that python.exe
is a symlink to the real python and native Windows programs do not
understand symlinks. For example in my case I have:

$ ls -l /bin/python.exe
lrwxrwxrwx 1 ef users 13 Dec  9 04:20 /bin/python.exe -> python2.4.exe

so I use the following python.bat script (put it in ~\LyX\bin)

8<8<8<
@echo off
python2.4 %*
exit
8<8<8<

Needless to say that all of this only applies to a native LyX version.

-- 
Enrico