Re: [rework docs] first snapshot of Userguide available

Uwe Stöhr wrote: So it shouldn't be problematic to put the documentation under the GFDL if we want that. But, and this is a big but, any licence change requires the agreement of all major contributers. So, if you want to change the docs licence to the GFDL, then you'll have to start contacting

[PATCH 13x] inputing files with spaces

Jean-Marc, here's a backport of the 1.4.x changes to enable the user to specify a file whose name contains spaces, but only if LaTeX can handle such a name. I guess that we should also get LyX to use the cleandvi script on the wiki pages, no? Did you get any where with your enquiries on the tex

[Fwd: [Monotone-devel] new Monotone under Cygwin timings]

Hi, I just stumbled across this mail on the monotone mailing list, which advises to use the non-thread-safe libraries to get a 3 factor speed-up on a Cygwin binary. Might be interesting to investigate for those that compiled LyX with Cygwin. Regards, Asger ---BeginMessage--- For the benefit the

Re: [Fwd: [Monotone-devel] new Monotone under Cygwin timings]

Asger Alstrup wrote: Hi, I just stumbled across this mail on the monotone mailing list, which advises to use the non-thread-safe libraries to get a 3 factor speed-up on a Cygwin binary. Might be interesting to investigate for those that compiled LyX with Cygwin. Regards, Asger

Describing the changes since LyX 1.3.5

Jean-Marc, I've been looking through the changes to the 1.3.x tree since I started this effort to merge Ruurd's LyX/Win port into the official sources. As a result, I've added descriptions of a number of small fixes to status.13x, attached. I've also tried to describe the 'bigger picture' that

Re: [PATCH 13x] inputing files with spaces

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc, here's a backport of the 1.4.x changes to enable the Angus user to specify a file whose name contains spaces, but only if Angus LaTeX can handle such a name. I have to admit that the length of this patch makes me nervous. Isn't

Re: [PATCH 13x] inputing files with spaces

Jean-Marc Lasgouttes wrote: Angus Jean-Marc, here's a backport of the 1.4.x changes to enable the Angus user to specify a file whose name contains spaces, but only if Angus LaTeX can handle such a name. I have to admit that the length of this patch makes me nervous. Isn't it possible to

Re: Describing the changes since LyX 1.3.5

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc, I've been looking through the changes to the 1.3.x Angus tree since I started this effort to merge Ruurd's LyX/Win port Angus into the official sources. As a result, I've added descriptions Angus of a number of small fixes to

Re: [PATCH 1.4] user interface

Michael == Michael Schmitt [EMAIL PROTECTED] writes: Michael Before, ellipses have been used in an inconsistent way; the Michael ellipses neither followed the GNOME _nor_ Jean-Marc's rule! As far as I know, we do not ship a GNOME version of LyX. Therefore, it would be more interesting to know

Re: [rework docs] first snapshot of Userguide available

Uwe == Uwe Stöhr [EMAIL PROTECTED] writes: Uwe Hello LyXers, after a lot of work, I have the heart to publish a Uwe development snapshot. Hello Uwe, Uwe I added many informations about topics discussed in the lyx-users Uwe list, like image formats, fonts in pdf etc. (The documentation is Uwe

Re: [PATCH 13x] inputing files with spaces

Angus == Angus Leeming [EMAIL PROTECTED] writes: I have to admit that the length of this patch makes me nervous. Isn't it possible to devise a `just good enough' solution that could go in 1.3.6? Angus Sure. Describe what you would like to see. I do not know precisely... Could we get away

Re: [PATCH 13x] inputing files with spaces

Jean-Marc Lasgouttes wrote: I have to admit that the length of this patch makes me nervous. Isn't it possible to devise a `just good enough' solution that could go in 1.3.6? Angus Sure. Describe what you would like to see. I do not know precisely... Could we get away without the nifty

Re: [patch] fix bug 1879

Georg Baum wrote: We still have some crashes related to open dialogs, see http://bugzilla.lyx.org/show_bug.cgi?id=1879. The attached patch should fix them. I am now pretty sure that I understand LFUN_INSET_MODIFY: The arguments are the new inset parameters. For many insets the first

Re: [patch] fix bug 1879

Georg Baum wrote: Georg Baum wrote: We still have some crashes related to open dialogs, see http://bugzilla.lyx.org/show_bug.cgi?id=1879. The attached patch should fix them. I am now pretty sure that I understand LFUN_INSET_MODIFY: The arguments are the new inset parameters. For many

Re: Describing the changes since LyX 1.3.5

Jean-Marc Lasgouttes wrote: Angus Jean-Marc, I've been looking through the changes to the 1.3.x Angus tree since I started this effort to merge Ruurd's LyX/Win port Angus into the official sources. As a result, I've added descriptions Angus of a number of small fixes to status.13x, attached.

Re: [patch] fix bug 1879

Angus Leeming wrote: If memory serves me right, all insets should emit a signal from their destructor: Indeed. Thanks! A proof-of-concept fix is attached. It works only for normal delete (the inset must not be selected, and the deletion must not cause a paragraph merge. BTW,

Re: [patch] fix bug 1879

Georg Baum wrote: BTW, Dialogs::hideSlot() is currently not used. Ur. When did that happen? 13 months ago: http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/Dialogs.C.diff?r1=1.31r2=1.32 Ouch! Thank you! -- Angus

Re: Describing the changes since LyX 1.3.5

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus I just cut and pasted your suggestion above. Thanks. However, Angus I've no idea how to make the packaging bit shorter as it Angus contains important user information. Maybe this file is the Angus wrong place to put it? What about a line

Re: [PATCH 13x] inputing files with spaces

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc Lasgouttes wrote: I have to admit that the length of this patch makes me nervous. Isn't it possible to devise a `just good enough' solution that could go in 1.3.6? Angus Sure. Describe what you would like to see. I do not

Re: Describing the changes since LyX 1.3.5

Jean-Marc Lasgouttes wrote: This means that all your changes should find their way into either status.13x or the wiki. Does this look like a plan? Yup. Actually, why don't we package clean_dvi.py, dvtdt and dt2dv with LyX 1.3.6, on Windows at least? And define the converters as appropriate. It

Re: Describing the changes since LyX 1.3.5

Some minor corrections for Mac OS X: On May 17, 2005, at 12:16 PM, Jean-Marc Lasgouttes wrote: LyX will expect to find its support files at: Unix/usr/share/lyx MacOS /Applications/LyX.app/Resources/lyx Windows C:\Program Files\LyX\Resources\lyx On the Mac, LyX.app is

Re: [rework docs] first snapshot of Userguide available

Jean-Marc Lasgouttes a écrit: How does this fit with the changes that have been done to the 1.4.0cvs user guide? What is the plan for merging later? I'll make a diff between the current documentation and the documentation of 1.4 to merge the differences into my new version. So I promise that

For the lyx-docs mailing list admin

Hello, could someone please delete the following email adress from the lyx-docs list?: [EMAIL PROTECTED]; Because whenever I write an email to the list, I get a mailer daemon message. thanks and regards Uwe

Re: [PATCH 1.4] user interface

Jean-Marc Lasgouttes wrote: As far as I know, we do not ship a GNOME version of LyX. Therefore, it would be more interesting to know what is said in OSX, Win32 and KDE UI guides. I do not remember the specifics, but it seems to me that we are not too far. This it was the KDE UI guideline says:

tex2lyx roundtrip problem

1. Load test.lyx which has a box inset with an enumeration inside it 2. Export it to LaTex (test.tex) 3. Run tex2lyx on test.tex, creating tex2lyx_output.lyx When tex2lyx_output.lyx is loaded in LyX, the box inset starts with a blank line which disappears once the cursor is moved into the inset.

Some new problems with cvs

Several new problems appear to have crept in recently. These two fail to produce UserGuide.tex: $ qlyxcvs --export latex UserGuide.lyx QPaintDevice: Must construct a QApplication before a QPaintDevice $ xlyxcvs --export latex UserGuide.lyx lyx: SIGSEGV signal caught Sorry, you have found a bug

lyx2lyx problems with the UserGuide

This chunk: If you are in one of these environments: \begin_inset ERT status Collapsed \layout Standard \end_inset \layout Standard \begin_inset ERT status Collapsed \layout Standard \backslash vspace{-2ex} \backslash parbox[t]{3cm}{

Re: [rework docs] first snapshot of Userguide available

Uwe Stöhr wrote: > So it shouldn't be problematic to put the documentation under the GFDL > if we want that. But, and this is a big but, any licence change requires the agreement of all "major" contributers. So, if you want to change the docs licence to the GFDL, then you'll have to start

[PATCH 13x] inputing "files with spaces"

Jean-Marc, here's a backport of the 1.4.x changes to enable the user to specify a file whose name contains spaces, but only if LaTeX can handle such a name. I guess that we should also get LyX to use the cleandvi script on the wiki pages, no? Did you get any where with your enquiries on the tex

[Fwd: [Monotone-devel] new Monotone under Cygwin timings]

Hi, I just stumbled across this mail on the monotone mailing list, which advises to use the non-thread-safe libraries to get a 3 factor speed-up on a Cygwin binary. Might be interesting to investigate for those that compiled LyX with Cygwin. Regards, Asger --- Begin Message --- For the benefit

Re: [Fwd: [Monotone-devel] new Monotone under Cygwin timings]

Asger Alstrup wrote: > Hi, > > I just stumbled across this mail on the monotone mailing list, which > advises to use the non-thread-safe libraries to get a 3 factor speed-up > on a Cygwin binary. > > Might be interesting to investigate for those that compiled LyX with > Cygwin. > > Regards, >

Describing the changes since LyX 1.3.5

Jean-Marc, I've been looking through the changes to the 1.3.x tree since I started this effort to merge Ruurd's LyX/Win port into the official sources. As a result, I've added descriptions of a number of small fixes to status.13x, attached. I've also tried to describe the 'bigger picture' that

Re: [PATCH 13x] inputing "files with spaces"

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Jean-Marc, here's a backport of the 1.4.x changes to enable the Angus> user to specify a file whose name contains spaces, but only if Angus> LaTeX can handle such a name. I have to admit that the length of this patch makes me

Re: [PATCH 13x] inputing "files with spaces"

Jean-Marc Lasgouttes wrote: > Angus> Jean-Marc, here's a backport of the 1.4.x changes to enable the > Angus> user to specify a file whose name contains spaces, but only if > Angus> LaTeX can handle such a name. > > I have to admit that the length of this patch makes me nervous. Isn't > it

Re: Describing the changes since LyX 1.3.5

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Jean-Marc, I've been looking through the changes to the 1.3.x Angus> tree since I started this effort to merge Ruurd's LyX/Win port Angus> into the official sources. As a result, I've added descriptions Angus> of a number of small

Re: [PATCH 1.4] user interface

> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes: Michael> Before, ellipses have been used in an inconsistent way; the Michael> ellipses neither followed the GNOME _nor_ Jean-Marc's rule! As far as I know, we do not ship a GNOME version of LyX. Therefore, it would be more

Re: [rework docs] first snapshot of Userguide available

> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes: Uwe> Hello LyXers, after a lot of work, I have the heart to publish a Uwe> development snapshot. Hello Uwe, Uwe> I added many informations about topics discussed in the lyx-users Uwe> list, like image formats, fonts in pdf etc. (The

Re: [PATCH 13x] inputing "files with spaces"

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: >> I have to admit that the length of this patch makes me nervous. >> Isn't it possible to devise a `just good enough' solution that >> could go in 1.3.6? Angus> Sure. Describe what you would like to see. I do not know precisely...

Re: [PATCH 13x] inputing "files with spaces"

Jean-Marc Lasgouttes wrote: >>> I have to admit that the length of this patch makes me nervous. >>> Isn't it possible to devise a `just good enough' solution that >>> could go in 1.3.6? > > Angus> Sure. Describe what you would like to see. > > I do not know precisely... Could we get away

Re: [patch] fix bug 1879

Georg Baum wrote: > We still have some crashes related to open dialogs, see > http://bugzilla.lyx.org/show_bug.cgi?id=1879. The attached patch should > fix them. I am now pretty sure that I understand LFUN_INSET_MODIFY: The > arguments are the new inset parameters. For many insets the first >

Re: [patch] fix bug 1879

Georg Baum wrote: > Georg Baum wrote: > >> We still have some crashes related to open dialogs, see >> http://bugzilla.lyx.org/show_bug.cgi?id=1879. The attached patch should >> fix them. I am now pretty sure that I understand LFUN_INSET_MODIFY: The >> arguments are the new inset parameters. For

Re: Describing the changes since LyX 1.3.5

Jean-Marc Lasgouttes wrote: > Angus> Jean-Marc, I've been looking through the changes to the 1.3.x > Angus> tree since I started this effort to merge Ruurd's LyX/Win port > Angus> into the official sources. As a result, I've added descriptions > Angus> of a number of small fixes to status.13x,

Re: [patch] fix bug 1879

Angus Leeming wrote: > If memory serves me right, all insets should emit a signal from their > destructor: Indeed. Thanks! >> A proof-of-concept fix is attached. It works only for "normal" delete >> (the inset must not be selected, and the deletion must not cause a >> paragraph merge. BTW,

Re: [patch] fix bug 1879

Georg Baum wrote: >>> BTW, Dialogs::hideSlot() is currently not used. >> Ur. When did that happen? > 13 months ago: > http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/Dialogs.C.diff?r1=1.31=1.32 Ouch! Thank you! -- Angus

Re: Describing the changes since LyX 1.3.5

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> I just cut and pasted your suggestion above. Thanks. However, Angus> I've no idea how to make the packaging bit shorter as it Angus> contains important user information. Maybe this file is the Angus> wrong place to put it? What

Re: [PATCH 13x] inputing "files with spaces"

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Jean-Marc Lasgouttes wrote: I have to admit that the length of this patch makes me nervous. Isn't it possible to devise a `just good enough' solution that could go in 1.3.6? >> Angus> Sure. Describe what you would

Re: Describing the changes since LyX 1.3.5

Jean-Marc Lasgouttes wrote: > This means that all your changes should find their way into either > status.13x or the wiki. Does this look like a plan? Yup. Actually, why don't we package clean_dvi.py, dvtdt and dt2dv with LyX 1.3.6, on Windows at least? And define the converters as appropriate.

Re: Describing the changes since LyX 1.3.5

Some minor corrections for Mac OS X: On May 17, 2005, at 12:16 PM, Jean-Marc Lasgouttes wrote: LyX will expect to find its support files at: Unix/usr/share/lyx MacOS /Applications/LyX.app/Resources/lyx Windows C:\Program Files\LyX\Resources\lyx On the Mac, LyX.app is

Re: [rework docs] first snapshot of Userguide available

Jean-Marc Lasgouttes a écrit: How does this fit with the changes that have been done to the 1.4.0cvs user guide? What is the plan for merging later? I'll make a diff between the current documentation and the documentation of 1.4 to merge the differences into my new version. So I promise that

For the lyx-docs mailing list admin

Hello, could someone please delete the following email adress from the lyx-docs list?: "<[EMAIL PROTECTED]>"; Because whenever I write an email to the list, I get a mailer daemon message. thanks and regards Uwe

Re: [PATCH 1.4] user interface

Jean-Marc Lasgouttes wrote: As far as I know, we do not ship a GNOME version of LyX. Therefore, it would be more interesting to know what is said in OSX, Win32 and KDE UI guides. I do not remember the specifics, but it seems to me that we are not too far. This it was the KDE UI guideline says:

tex2lyx roundtrip problem

1. Load test.lyx which has a box inset with an enumeration inside it 2. Export it to LaTex (test.tex) 3. Run tex2lyx on test.tex, creating tex2lyx_output.lyx When tex2lyx_output.lyx is loaded in LyX, the box inset starts with a blank line which disappears once the cursor is moved into the inset.

Some new problems with cvs

Several new problems appear to have crept in recently. These two fail to produce UserGuide.tex: $ qlyxcvs --export latex UserGuide.lyx QPaintDevice: Must construct a QApplication before a QPaintDevice $ xlyxcvs --export latex UserGuide.lyx lyx: SIGSEGV signal caught Sorry, you have found a bug

lyx2lyx problems with the UserGuide

This chunk: If you are in one of these environments: \begin_inset ERT status Collapsed \layout Standard \end_inset \layout Standard \begin_inset ERT status Collapsed \layout Standard \backslash vspace{-2ex} \backslash parbox[t]{3cm}{