Re: Latest LyX on Latest Cygwin

2005-01-12 Thread Angus Leeming
Jean-Marc Lasgouttes wrote: > Angus> Has a consensus been reached that Kayvan's solution is 'good > Angus> enough'? That's my reading of the conversation that has > Angus> followed, but I'd like an explicit "yes" before tackling the > Angus> GUI stuff. > > Yes, it certainly qualifies for 'good eno

Re: Latest LyX on Latest Cygwin

2005-01-12 Thread Jean-Marc Lasgouttes
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Has a consensus been reached that Kayvan's solution is 'good Angus> enough'? That's my reading of the conversation that has Angus> followed, but I'd like an explicit "yes" before tackling the Angus> GUI stuff. Yes, it certainly qua

Re: Latest LyX on Latest Cygwin

2005-01-12 Thread Angus Leeming
Kayvan A. Sylvan wrote: >> The GUI stuff is icing that will take 10 minutes; I'm happy to do that. >> However, I'd prefer to leave the configure stuff to you. Happy? > Sure. This patch almost works right. LyX now checks the new variable > (which was set by configure) and does the right thing. Has

Re: Latest LyX on Latest Cygwin

2005-01-11 Thread John Weiss
On Mon, Jan 03, 2005 at 01:08:32PM -0800, Kayvan A. Sylvan wrote: > Hmmm... Yes, that can happen. I route around such problems though. > For example: The Acrobat reader program needs dos paths. So, I use > the following shell script (as /usr/local/bin/acroread): > > #!/bin/sh > > if [ $#

Re: Latest LyX on Latest Cygwin

2005-01-07 Thread Kayvan A. Sylvan
On Fri, Jan 07, 2005 at 04:35:38PM +0100, Jean-Marc Lasgouttes wrote: > > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: > > >> Your patch does not sound right. It says that under cygwin, all > >> programs should use dos-style paths. If this is the case, a simple > >> #ifdef __CYGWIN

Re: Latest LyX on Latest Cygwin

2005-01-07 Thread Jean-Marc Lasgouttes
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: >> Your patch does not sound right. It says that under cygwin, all >> programs should use dos-style paths. If this is the case, a simple >> #ifdef __CYGWIN__ could be used to hardcode this into LyX... Kayvan> No, it's the other way ar

Re: Latest LyX on Latest Cygwin

2005-01-03 Thread Kayvan A. Sylvan
On Mon, Jan 03, 2005 at 11:20:22AM +0100, Jean-Marc Lasgouttes wrote: > > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: > > Kayvan> On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote: > >> The GUI stuff is icing that will take 10 minutes; I'm happy to do > >> that. Howeve

Re: Latest LyX on Latest Cygwin

2005-01-03 Thread Jean-Marc Lasgouttes
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: Kayvan> On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote: >> The GUI stuff is icing that will take 10 minutes; I'm happy to do >> that. However, I'd prefer to leave the configure stuff to you. >> Happy? >> Kayvan> Sure.

Re: Latest LyX on Latest Cygwin

2005-01-02 Thread Kayvan A. Sylvan
On Sun, Jan 02, 2005 at 07:42:46PM +, Angus Leeming wrote: > > I don't know the right way to fix this. Please take a look and see > > if you can tackle this little piece in addition to the GUI stff. > > Will do. Many thanks for doing the grunt work. Great. I can do a last minute check on the

Re: Latest LyX on Latest Cygwin

2005-01-02 Thread Angus Leeming
Kayvan A. Sylvan wrote: >> The GUI stuff is icing that will take 10 minutes; I'm happy to do that. >> However, I'd prefer to leave the configure stuff to you. Happy? >> > > Sure. This patch almost works right. LyX now checks the new variable > (which was set by configure) and does the right thing

Re: Latest LyX on Latest Cygwin

2005-01-02 Thread Kayvan A. Sylvan
On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote: > > The GUI stuff is icing that will take 10 minutes; I'm happy to do that. > However, I'd prefer to leave the configure stuff to you. Happy? > Sure. This patch almost works right. LyX now checks the new variable (which was set by co

Re: Latest LyX on Latest Cygwin

2005-01-01 Thread Angus Leeming
Kayvan A. Sylvan wrote: > On Fri, Dec 31, 2004 at 04:24:37PM +, Angus Leeming wrote: >> Angus Leeming wrote: >> > Sure. This means that the s/slashify_path/internal_path/ switch was >> > less carefully done that it needed to be. Mea culpa. >> > >> > I'll try and come up with something in the

Re: Latest LyX on Latest Cygwin

2004-12-31 Thread Kayvan A. Sylvan
On Thu, Dec 30, 2004 at 08:42:19AM +0100, Michael Schmitt wrote: > Dear Kayvan, > > I guess you have upgraded from gcc 3.3.1 to 3.3.3, right? All I can say is > that this compiler version does not work and 3.4X neither :-( I can say now that gcc-3.3.3 works fine with the latest Cygwin with the x

Re: Latest LyX on Latest Cygwin

2004-12-31 Thread Kayvan A. Sylvan
On Fri, Dec 31, 2004 at 04:24:37PM +, Angus Leeming wrote: > Angus Leeming wrote: > > Sure. This means that the s/slashify_path/internal_path/ switch was less > > carefully done that it needed to be. Mea culpa. > > > > I'll try and come up with something in the next couple of hours. > > Ok, K

Re: Latest LyX on Latest Cygwin

2004-12-31 Thread Angus Leeming
Angus Leeming wrote: > Sure. This means that the s/slashify_path/internal_path/ switch was less > carefully done that it needed to be. Mea culpa. > > I'll try and come up with something in the next couple of hours. Ok, Kayvan. The problem (I believe) lies in the call to 'MakeLatexName', below, wh

Re: Latest LyX on Latest Cygwin

2004-12-31 Thread Angus Leeming
Kayvan A. Sylvan wrote: > Hi Angus, > > Here is another clue. I ran the lyx executable with strace under Cygwin. > > The output was very interesting and seems to point to an infinite > loop in startup: > > [...] >39 433123 [main] lyx 3884 mount_info::conv_to_posix_path: >conv_to_posix_

Re: Latest LyX on Latest Cygwin

2004-12-30 Thread Kayvan A. Sylvan
Hi Angus, Here is another clue. I ran the lyx executable with strace under Cygwin. The output was very interesting and seems to point to an infinite loop in startup: [...] 39 433123 [main] lyx 3884 mount_info::conv_to_posix_path: conv_to_posix_path (/usr/local/, keep-rel, add-slash) 25

Re: Latest LyX on Latest Cygwin

2004-12-30 Thread Kayvan A. Sylvan
On Thu, Dec 30, 2004 at 08:42:19AM +0100, Michael Schmitt wrote: > Dear Kayvan, > > I guess you have upgraded from gcc 3.3.1 to 3.3.3, right? All I can say is > that this compiler version does not work and 3.4X neither :-( > > Actually, I spent countless days on uncovering and fixing the problem

Re: Latest LyX on Latest Cygwin

2004-12-30 Thread Michael Schmitt
Dear Kayvan, I guess you have upgraded from gcc 3.3.1 to 3.3.3, right? All I can say is that this compiler version does not work and 3.4X neither :-( Actually, I spent countless days on uncovering and fixing the problem but all I found was this email: http://www.cygwin.com/ml/cygwin/2004-09/msg

Re: Latest LyX on Latest Cygwin

2004-12-29 Thread Kayvan A. Sylvan
On Wed, Dec 29, 2004 at 09:40:55PM +, Angus Leeming wrote: > Kayvan A. Sylvan wrote: > > > I'm having the following problem after having upgraded Cygwin to the > > latest and then compiling the latest lyx CVS: > > Hi, Kayvan. > > I've made a lot of little changes recently that may well impac

Re: Latest LyX on Latest Cygwin

2004-12-29 Thread Angus Leeming
Kayvan A. Sylvan wrote: > I'm having the following problem after having upgraded Cygwin to the > latest and then compiling the latest lyx CVS: Hi, Kayvan. I've made a lot of little changes recently that may well impact Cygwin. I'd be suspicious of this mail and the associated patch: [PATCH 13x,