Re: [patch] move OS dependent code to proper place

2007-01-14 Thread Georg Baum
Am Sonntag, 14. Januar 2007 03:02 schrieb Enrico Forestieri: On Sat, Jan 13, 2007 at 12:36:11PM +0100, Georg Baum wrote: No I don't mean that. I mean useful for cygwin users in general. IIRC I was the only one besides you who had opinions on this patch. I stated two or three times

Re: [patch] move OS dependent code to proper place

2007-01-14 Thread Georg Baum
Am Sonntag, 14. Januar 2007 03:02 schrieb Enrico Forestieri: > On Sat, Jan 13, 2007 at 12:36:11PM +0100, Georg Baum wrote: > > > No I don't mean that. I mean "useful for cygwin users in general". IIRC I > > was the only one besides you who had opinions on this patch. I stated two > > or three

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that through an env variable it is possible to use either posix or windows

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:50:10PM +0100, Georg Baum wrote: Enrico Forestieri wrote: Believe me, external_path could be completely ditched. Please stop talking of external_path. Yesterday you wrote that you don't want to discuss that anymore, and I don't want that either. I gave up

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Abdelrazak Younes
Enrico Forestieri wrote: On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that through an env variable it is possible to use

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 10:03:39AM +0100, Abdelrazak Younes wrote: Enrico Forestieri wrote: On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Georg Baum
Am Samstag, 13. Januar 2007 09:58 schrieb Enrico Forestieri: On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Georg Baum
Am Samstag, 13. Januar 2007 10:00 schrieb Enrico Forestieri: Ok. I'll take into account your lack of sense of humour in the future. It was indeed not clear to me at all that this was intended as a joke. Because it was not the first time you brought up the external_path issue after the initial

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 12:36:11PM +0100, Georg Baum wrote: Am Samstag, 13. Januar 2007 09:58 schrieb Enrico Forestieri: On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 12:36:17PM +0100, Georg Baum wrote: Am Samstag, 13. Januar 2007 10:00 schrieb Enrico Forestieri: Ok. I'll take into account your lack of sense of humour in the future. It was indeed not clear to me at all that this was intended as a joke. Because it was not the

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sun, Jan 14, 2007 at 03:02:26AM +0100, Enrico Forestieri wrote: I attach here a new version of the README.cygwin file intended to replace the existing one. I cannot do it, so someone else will have to. I think that for better compliance with the GPL the patch should be put alongside the

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > as a parameter introducer. To tell you the truth, the cygwin version > > of lyx that I make available for download is patched such that through > > an env variable it is possible to use either posix or

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:50:10PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > Believe me, external_path could be completely ditched. > > Please stop talking of external_path. Yesterday you wrote that you don't > want to discuss that anymore, and I don't want that either. I gave

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Abdelrazak Younes
Enrico Forestieri wrote: On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that through an env variable it is possible to use

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 10:03:39AM +0100, Abdelrazak Younes wrote: > Enrico Forestieri wrote: > > On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: > > > >> Enrico Forestieri wrote: > >> > >>> as a parameter introducer. To tell you the truth, the cygwin version > >>> of lyx that I make

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Georg Baum
Am Samstag, 13. Januar 2007 09:58 schrieb Enrico Forestieri: > On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: > > > Enrico Forestieri wrote: > > > > > as a parameter introducer. To tell you the truth, the cygwin version > > > of lyx that I make available for download is patched such

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Georg Baum
Am Samstag, 13. Januar 2007 10:00 schrieb Enrico Forestieri: > Ok. I'll take into account your lack of sense of humour in the future. It was indeed not clear to me at all that this was intended as a joke. Because it was not the first time you brought up the external_path issue after the

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 12:36:11PM +0100, Georg Baum wrote: > Am Samstag, 13. Januar 2007 09:58 schrieb Enrico Forestieri: > > On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: > > > > > Enrico Forestieri wrote: > > > > > > > as a parameter introducer. To tell you the truth, the

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sat, Jan 13, 2007 at 12:36:17PM +0100, Georg Baum wrote: > Am Samstag, 13. Januar 2007 10:00 schrieb Enrico Forestieri: > > > Ok. I'll take into account your lack of sense of humour in the future. > > It was indeed not clear to me at all that this was intended as a joke. > Because it was

Re: [patch] move OS dependent code to proper place

2007-01-13 Thread Enrico Forestieri
On Sun, Jan 14, 2007 at 03:02:26AM +0100, Enrico Forestieri wrote: > I attach here a new version of the README.cygwin file intended to > replace the existing one. I cannot do it, so someone else will have to. I think that for better compliance with the GPL the patch should be put alongside the

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: Many parts of the LyX code depend on the fact that we use internal paths only. Therefore we should fix the external inset to not call external_path when building the to_file name. It would be nice if you

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 03:55:01PM +0100, Georg Baum wrote: Enrico Forestieri wrote: On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: Many parts of the LyX code depend on the fact that we use internal paths only. Therefore we should fix the external inset to not call

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: Believe me, external_path could be completely ditched. Please stop talking of external_path. Yesterday you wrote that you don't want to discuss that anymore, and I don't want that either. I gave up trying to understand how it behaves now a long time ago, and I don't

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that through an env variable it is possible to use either posix or windows style paths. Making a binary created from patched sources

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: Enrico Forestieri wrote: as a parameter introducer. To tell you the truth, the cygwin version of lyx that I make available for download is patched such that through an env variable it is possible to use either posix or windows

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:50:10PM +0100, Georg Baum wrote: Enrico Forestieri wrote: Believe me, external_path could be completely ditched. Please stop talking of external_path. Yesterday you wrote that you don't want to discuss that anymore, and I don't want that either. I gave up

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: > On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: > >> Many parts of the LyX code depend on the fact that we use internal paths >> only. Therefore we should fix the external inset to not call >> external_path when building the to_file name. It would be nice

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 03:55:01PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: > > > >> Many parts of the LyX code depend on the fact that we use internal paths > >> only. Therefore we should fix the external inset to not

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: > Believe me, external_path could be completely ditched. Please stop talking of external_path. Yesterday you wrote that you don't want to discuss that anymore, and I don't want that either. I gave up trying to understand how it behaves now a long time ago, and I don't

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Georg Baum
Enrico Forestieri wrote: > as a parameter introducer. To tell you the truth, the cygwin version > of lyx that I make available for download is patched such that through > an env variable it is possible to use either posix or windows style > paths. Making a binary created from patched sources

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:55:20PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > as a parameter introducer. To tell you the truth, the cygwin version > > of lyx that I make available for download is patched such that through > > an env variable it is possible to use either posix or

Re: [patch] move OS dependent code to proper place

2007-01-12 Thread Enrico Forestieri
On Fri, Jan 12, 2007 at 05:50:10PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > Believe me, external_path could be completely ditched. > > Please stop talking of external_path. Yesterday you wrote that you don't > want to discuss that anymore, and I don't want that either. I gave up

[patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
The attached patch avoids the need to differentiate the kind of path style returned by external_path on cygwin depending on whether Qt/X11 or Qt/Win is used for building. It also avoids an ugly #ifdef and solves a bug related to including something through the external material inset (this bug

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Georg Baum
Enrico Forestieri wrote: The attached patch avoids the need to differentiate the kind of path style returned by external_path on cygwin depending on whether Qt/X11 or Qt/Win is used for building. It also avoids an ugly #ifdef and solves a bug related to including something through the

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 06:39:56PM +0100, Georg Baum wrote: Enrico Forestieri wrote: The attached patch avoids the need to differentiate the kind of path style returned by external_path on cygwin depending on whether Qt/X11 or Qt/Win is used for building. It also avoids an ugly

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Georg Baum
Enrico Forestieri wrote: It goes in the following way. Symptom: When using the external inset to include an xfig file, after View-DVI an error dialog appears telling that the .pstex_t file is missing. Running by hand the fig2pstex.py script, all necessary files are regularly produced, but

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: Many parts of the LyX code depend on the fact that we use internal paths only. Therefore we should fix the external inset to not call external_path when building the to_file name. It would be nice if you could do that. I really don't

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: Many parts of the LyX code depend on the fact that we use internal paths only. Therefore we should fix the external inset to not call external_path when building the to_file name. It would be nice if you could do that. I did that,

[patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
The attached patch avoids the need to differentiate the kind of path style returned by external_path on cygwin depending on whether Qt/X11 or Qt/Win is used for building. It also avoids an ugly #ifdef and solves a bug related to including something through the external material inset (this bug

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Georg Baum
Enrico Forestieri wrote: > The attached patch avoids the need to differentiate the kind of path > style returned by external_path on cygwin depending on whether Qt/X11 > or Qt/Win is used for building. > > It also avoids an ugly #ifdef and solves a bug related to including > something through

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 06:39:56PM +0100, Georg Baum wrote: > Enrico Forestieri wrote: > > > The attached patch avoids the need to differentiate the kind of path > > style returned by external_path on cygwin depending on whether Qt/X11 > > or Qt/Win is used for building. > > > > It also avoids

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Georg Baum
Enrico Forestieri wrote: > It goes in the following way. > > Symptom: When using the external inset to include an xfig file, after > View->DVI an error dialog appears telling that the .pstex_t file is > missing. Running by hand the fig2pstex.py script, all necessary files > are regularly

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: > Many parts of the LyX code depend on the fact that we use internal paths > only. Therefore we should fix the external inset to not call external_path > when building the to_file name. It would be nice if you could do that. I really

Re: [patch] move OS dependent code to proper place

2007-01-11 Thread Enrico Forestieri
On Thu, Jan 11, 2007 at 08:19:05PM +0100, Georg Baum wrote: > Many parts of the LyX code depend on the fact that we use internal paths > only. Therefore we should fix the external inset to not call external_path > when building the to_file name. It would be nice if you could do that. I did that,