Re: Beta (status update #3)

Am 01.11.2010 um 23:42 schrieb Pavel Sanda: Stephan Witt wrote: Sorry, I went out and could not answer :-) 1) I have a patch at hand to add the ability to collect stderr in system call and to simplify the stdout collection too. This patch doesn't change the current interface but adds a

Re: Beta (status update #3)

Am 02.11.2010 um 07:31 schrieb Stephan Witt: Am 01.11.2010 um 23:42 schrieb Pavel Sanda: Stephan Witt wrote: 3) Want the readFile() issue fixed. is this beta1 critical stuf? After my last commit in readFile() it's only the issue with file_found_hook being called with the wrong

Re: #7008: longtable dialog regression

On 11/02/2010 12:11 AM, LyX Ticket Tracker wrote: #7008: longtable dialog regression ---+ Reporter: uwestoehr | Owner: poenitz Type: defect | Status: new Priority: high | Milestone:

Re: Beta (status update #3)

After my last commit in readFile() it's only the issue with file_found_hook being called with the wrong file name in case of autosave and emergency. I'd like to fix it before (2) or maybe Vincent does it... For users of VCS I'd rate it as a serious problem - but not critical. To

Commit logs

Log: first step to cure the VCS load problem Log: Partially fix #5108. Log: Fix bug #6997 Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed,

Re: Beta (status update #3)

Am 02.11.2010 um 10:22 schrieb Vincent van Ravesteijn: After my last commit in readFile() it's only the issue with file_found_hook being called with the wrong file name in case of autosave and emergency. I'd like to fix it before (2) or maybe Vincent does it... For users of

Re: Beta (status update #3)

Yes. Ive got something. Wait Op 1 nov 2010 14:21 schreef Pavel Sanda sa...@lyx.org: hi, 1. Richard, whats the status of a)? i'm basically waiting only for this. could you give it top priority on your list if its not fixed yet? 2. Vincent could you put in the pending patch for b? 3.

Re: Commit logs

Am 02.11.2010 um 10:29 schrieb Vincent van Ravesteijn: Log: first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what

Re: feature request: edit tex files

On 1. Nov 2010, at 14:22, Jürgen Spitzmüller wrote: Yann Disser wrote: Your arguments make sense. However, I think many people must have my problem. Perhaps it would be sufficient to provide a way to keep the .lyx file and the .tex file in sync. Whenever one of the two would get changed,

Re: #6871: Missing screen update can cause assertion after lyxserver communication

On 11/02/2010 12:31 PM, LyX Ticket Tracker wrote: Comment(by sanda): But you will still have a latent bug here. so this 'fix' is still not fixing the root cause, right? Right.

vcs load problem

first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed, why other solutions might be wrong although it may

Re: vcs load problem

Am 02.11.2010 um 12:34 schrieb Vincent van Ravesteijn: first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it

Re: Commit logs

Log: first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed, why other solutions might be wrong although it

Re: vcs load problem

The VCS load problem is (was) twofold: 1. the parser of the document needs the VCS state so this state (checked by file_found_hook) had to be done earlier. = first step, move it some lines up, above the readDocument() call. Why does the parser need to know the state ? If the state changes,

Re: vcs load problem

Am 02.11.2010 um 12:51 schrieb Stephan Witt: Am 02.11.2010 um 12:34 schrieb Vincent van Ravesteijn: first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or

Re: vcs load problem

Vincent van Ravesteijn wrote: Why does the parser need to know the state ? If the state changes, do we then reparse the file too ? I think this stumbles on a other design problem. If we have a file, we insert an InsetInfo about vcs, then we add the file to a vcs, will the InsetInfo be

Re: vcs load problem

Stephan Witt wrote: The attached patch works. i'm happy the other occurences disappeared... pavel

Re: vcs load problem

Vincent van Ravesteijn wrote: If we have a file, we insert an InsetInfo about vcs, then we add the file to a vcs, will the InsetInfo be updated ? Apparently not, apparently the file is updated not until we parse the file again. it will be updated, when you add file to vcs, its reloaded.

Re: vcs load problem

Am 02.11.2010 um 13:06 schrieb Vincent van Ravesteijn: The VCS load problem is (was) twofold: 1. the parser of the document needs the VCS state so this state (checked by file_found_hook) had to be done earlier. = first step, move it some lines up, above the readDocument() call. Why

Re: Beta (status update #3)

Stephan Witt wrote: if you have the patch already feel free to post it, but... I'll attach it - so you get the idea. I want to 1) catch the output of failing system calls to display them in error message dialog 2) eventually be able to pass it up to caller for parsing it 3) simplify

Re: Beta (status update #3)

Vincent van Ravesteijn wrote: Yes. Ive got something. Wait can you share your timetable? pavel

Re: r35970 - lyx-devel/trunk/src/frontends/qt4

Author: rgheck Date: Mon Nov 1 20:37:59 2010 New Revision: 35970 URL: http://www.lyx.org/trac/changeset/35970 Log: Fix bug #7002. I think this is correct, but Peter should check. May I, may I ? func_ = f; - callInGuiThread(); + if (theApp() == 0)

Re: r35970 - lyx-devel/trunk/src/frontends/qt4

Sorry, Peter already did this. Vincent

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

Le 01/11/2010 14:27, Pavel Sanda a écrit : you...@lyx.org wrote: Modified: lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui == --- lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui Wed Oct 27 14:55:57 2010

Re: feature request: edit tex files

I agree it would be nice. But it's almost impossible. The problem is that (La)TeX provides multiple ways (packages) for achieving the same thing. LyX will never be able to support them all, so either your LaTeX collaborators will needs to know what LyX supports (which is not what they

Re: r35995 - lyx-devel/trunk/src

rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every platform. btw on which platform will this enum starts on non zero number? pavel

Re: feature request: edit tex files

Le 01/11/2010 14:16, Yann Disser a écrit : Well, as I said, with automatic sync I do not think it would be so much of a nightmare anymore. And, for me at least, editing formula-heavy .tex is also not very enjoyable. A typical example of when tex-lyx breaks with formulas is when people use

Re: RefStyle Patch

Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : So do we have an extra \makeatletter somewhere? Yes, exporting my example file in LaTeX reads: cite \makeatletter %% LyX specific LaTeX commands.

Re: r35995 - lyx-devel/trunk/src

On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every platform. btw on which platform

Abdel

On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every

Re: Abdel

On 11/02/2010 11:34 AM, Abdelrazak Younes wrote: On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the

Re: Abdel

On 11/02/2010 04:35 PM, Richard Heck wrote: On 11/02/2010 11:34 AM, Abdelrazak Younes wrote: On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL:

Re: r35995 - lyx-devel/trunk/src

Richard Heck wrote: Log: Make sure that the members of this enum get the same value on every platform. btw on which platform will this enum starts on non zero number? I don't know for sure. But the file Uwe posted with #7005 had: \html_math_output -1 which was what was

Re: Abdel

On 11/02/2010 11:39 AM, Abdelrazak Younes wrote: On 11/02/2010 04:35 PM, Richard Heck wrote: Well, it can't hurt to specify that it starts from 0. Sure. I even consider this good practice. And I'm not sure how Uwe could otherwise have gotten the line with -1. Don't know... But if this is

Re: r35995 - lyx-devel/trunk/src

On 11/02/2010 11:41 AM, Pavel Sanda wrote: Richard Heck wrote: Log: Make sure that the members of this enum get the same value on every platform. btw on which platform will this enum starts on non zero number? I don't know for sure. But the file Uwe posted with #7005

Re: Abdel

Abdelrazak Younes wrote: I don't think so. I don't know for sure but think an enum is guaranted to start from zero on all platform by the standard (unless if set older C++ standard i have (but should be the same nowadays) says: If the first enumerator has no initializer, the value of the

Re: r36001 - lyx-devel/trunk/src

rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 16:42:45 2010 New Revision: 36001 URL: http://www.lyx.org/trac/changeset/36001 Log: Perhaps this is overkill, but it can't hurt yes, it is overkill. the quote from standard continues: An enumerator-definition without an

Re: r36001 - lyx-devel/trunk/src

On 11/02/2010 11:57 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 16:42:45 2010 New Revision: 36001 URL: http://www.lyx.org/trac/changeset/36001 Log: Perhaps this is overkill, but it can't hurt yes, it is overkill. the quote from standard

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

i see these lines are becoming part of our ui files more and more often. is there anybody around to check it compiles with qt 4.2.2 which we claim to support? It doesn't compile with Qt 4.2.x with this line. André once explained us why and that one must have at least Qt 4.3.0 to get it

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

Uwe Stöhr wrote: i see these lines are becoming part of our ui files more and more often. is there anybody around to check it compiles with qt 4.2.2 which we claim to support? It doesn't compile with Qt 4.2.x with this line. André once explained us why and that one must have at least

Re: Beta (status update #3)

Am 02.11.2010 um 13:44 schrieb Pavel Sanda: Stephan Witt wrote: if you have the patch already feel free to post it, but... I'll attach it - so you get the idea. I want to 1) catch the output of failing system calls to display them in error message dialog 2) eventually be able to pass

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

Uwe Stöhr wrote: However, if Jürgen doesn't use Qt 4.2 anymore I think nobody of us do and we will sooner or later forget to remove this line when committing UI stuff. So I think its best to promise only Qt 4.3.0 support for LyX 2.0. Personally, I do not use Qt 4.2 (but 4.7), but I use a 4.2

Re: RefStyle Patch

Jean-Pierre Chrétien a écrit : Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in

Re: Beta (status update #3)

Stephan Witt wrote: Where did you draw the line exactly? :-) thats difficult to describe exactly :) when you asked about some cvs improvements i thought you just want to replace few cvs parameters and perhaphs push one two new commands, give it testing and check the documentation. that was what

Re: r35995 - lyx-devel/trunk/src

On Tue, Nov 02, 2010 at 03:53:56PM +0100, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every platform.

Re: r35970 - lyx-devel/trunk/src/frontends/qt4

On 02.11.2010 14:46, Vincent van Ravesteijn wrote: Sorry, Peter already did this. Vincent Sorry, should have dropped a mail to the list. But it's nice to see others have similar ideas. Peter

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

exclude it just out of lazyness. After all, there might still be some conservative admins out there. Jürgen Will a conservative admin install LyX 2? Peter

Re: RefStyle Patch

On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : I got an anwer from Danie, I was mistaken about the multilingual feature of refstyle: it works all right (as \def commands are encapsulated in \extraslang commands) if refstyle is loaded *after* babel. Is

Re: Beta (status update #3)

When starts the 2.1 cycle, by the way? After 2.0 final release? Would 2.0 be a branch then? we should wait for for x.y.1 so people focus on bugfixing little more. iirc this was the case for previous releases too. pavel I wanted to propose to start the 2.0.x branch when you enter the

Re: Beta (status update #3)

Vincent van Ravesteijn wrote: I wanted to propose to start the 2.0.x branch when you enter the feature-freeze/beta state. This would allow to continue redesigning and refactoring the code, because I stumble on this everytime I try to fix real problems in the codebase. we can discuss it.

Re: #6940: Check lilypond before release

On 01/11/2010 8:37 PM, Julien Rioux wrote: On 01/11/2010 6:49 PM, Pavel Sanda wrote: Julien Rioux wrote: This is with instant preview on, opening the file examples/lilypond.lyx, the preview fails (some lilypond code in there should be changed) and then this signal occurs. thanks, can you try

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

On 11/02/2010 06:50 PM, Pavel Sanda wrote: Peter Kümmel wrote: exclude it just out of lazyness. After all, there might still be some conservative admins out there. well, conservative admins... current release of centos has 4.2.1... Will a conservative admin install LyX 2?

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

Peter Kümmel wrote: exclude it just out of lazyness. After all, there might still be some conservative admins out there. well, conservative admins... current release of centos has 4.2.1... Will a conservative admin install LyX 2? the admin no, but the user can do it locally without need

Re: contributions

On 11/02/2010 04:19 PM, John Perry wrote: to whom it may concern, I hereby grant permission to use my contributions to LyX under the GPL license version 2 or later. Thanks. I'll get you into the CREDITS file once the message appear on MARC. (We reference it that way.) rh

contributions

to whom it may concern, I hereby grant permission to use my contributions to LyX under the GPL license version 2 or later. regards john perry

Re: Beta (status update #3)

Am 02.11.2010 um 19:27 schrieb Pavel Sanda: Stephan Witt wrote: Where did you draw the line exactly? :-) thats difficult to describe exactly :) Wow, long text... when you asked about some cvs improvements i thought you just want to replace few cvs parameters and perhaphs push one two

Re: Beta (status update #3)

On 11/02/2010 02:31 AM, Stephan Witt wrote: After my last commit in readFile() it's only the issue with file_found_hook being called with the wrong file name in case of autosave and emergency. I'd like to fix it before (2) or maybe Vincent does it... For users of VCS I'd rate it as a serious

Re: Beta (status update #3)

After my last commit in readFile() it's only the issue with file_found_hook being called with the wrong file name in case of autosave and emergency. I'd like to fix it before (2) or maybe Vincent does it... For users of VCS I'd rate it as a serious problem - but not critical. To

Re: Beta (status update #3)

On 11/02/2010 02:31 AM, Stephan Witt wrote: Am 01.11.2010 um 23:42 schrieb Pavel Sanda: Stephan Witt wrote: Sorry, I went out and could not answer :-) 1) I have a patch at hand to add the ability to collect stderr in system call and to simplify the stdout collection too. This patch

Re: Beta (status update #3)

Stephan Witt wrote: I only introduced the getState() method because I couldn't collect the error message. does it mean we can get rid of this CvsStatus creature and logic around if error messages are caught? When starts the 2.1 cycle, by the way? After 2.0 final release? Would 2.0 be a

Re: Beta (status update #3)

On 11/02/2010 07:39 PM, Pavel Sanda wrote: Vincent van Ravesteijn wrote: I wanted to propose to start the 2.0.x branch when you enter the feature-freeze/beta state. This would allow to continue redesigning and refactoring the code, because I stumble on this everytime I try to fix real

Re: #6940: Check lilypond before release

Julien Rioux wrote: Updates to examples/lilypond.lyx - requirements - gotchas - removed some lilypond code which made lilypond-book safe-mode unhappy thanks, its in. pavel

Re: Beta (status update #3)

It gets called again in readfile, but then with the wrong name. As discussed in another thread we can use a single call only and use d-filename. Op 3 nov 2010 01:06 schreef Richard Heck rgh...@comcast.net: On 11/02/2010 02:31 AM, Stephan Witt wrote: After my last commit in readFile() it's

Re: Beta (status update #3)

Richard Heck wrote: There's a difference between refactoring because we think the code is ugly or hard to understand, and refactoring that is necessary to fix a problem the right way. Freeze means none of the former. The latter sort of thing can be considered on a case-by-case basis. I.e.,

Re: Beta (status update #3)

I would still like to move renamebuffer from guiview to buffer. Fix the vc problems and I'll quit the refactoring for a while. Next fun project would be to add testcode for the buffer class. This can be done in trunk as it won't be compiled for a release. The features I am preparing still: - add

Re: Beta (status update #3)

On 11/01/2010 09:20 AM, Pavel Sanda wrote: hi, 1. Richard, whats the status of a)? i'm basically waiting only for this. could you give it top priority on your list if its not fixed yet? I've sent a note to JMarc asking a few questions. Once I'm absolutely sure what I need to do, then it

Re: Beta (status update #3)

Richard Heck wrote: One other issue, by the way, which maybe isn't essential for beta1: I've written the python for the LFUN and preferences conversion routines, i dont think this is essential issue. pavel

Re: Beta (status update #3)

Am 01.11.2010 um 23:42 schrieb Pavel Sanda: > Stephan Witt wrote: >> Sorry, I went out and could not answer :-) >> >> 1) I have a patch at hand to add the ability to collect stderr in system call >> and to simplify the stdout collection too. This patch doesn't change the >> current interface but

Re: Beta (status update #3)

Am 02.11.2010 um 07:31 schrieb Stephan Witt: > Am 01.11.2010 um 23:42 schrieb Pavel Sanda: > >> Stephan Witt wrote: >> >>> 3) Want the readFile() issue fixed. >> >> is this beta1 critical stuf? > > After my last commit in readFile() it's "only" the issue with file_found_hook > being called

Re: #7008: longtable dialog regression

On 11/02/2010 12:11 AM, LyX Ticket Tracker wrote: #7008: longtable dialog regression ---+ Reporter: uwestoehr | Owner: poenitz Type: defect | Status: new Priority: high | Milestone:

Re: Beta (status update #3)

> After my last commit in readFile() it's "only" the issue with file_found_hook being called with the wrong file name in case of autosave and emergency. > I'd like to fix it before (2) or maybe Vincent does it... > For users of VCS I'd rate it as a serious problem - but not critical. To

Commit logs

Log: first step to cure the VCS load problem Log: Partially fix #5108. Log: Fix bug #6997 Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed,

Re: Beta (status update #3)

Am 02.11.2010 um 10:22 schrieb Vincent van Ravesteijn: > >> > >> After my last commit in readFile() it's "only" the issue with >> file_found_hook being called with the wrong file name in case of autosave >> and emergency. >> >> > >> I'd like to fix it before (2) or maybe Vincent does it...

Re: Beta (status update #3)

Yes. Ive got something. Wait Op 1 nov 2010 14:21 schreef "Pavel Sanda" : hi, 1. Richard, whats the status of a)? i'm basically waiting only for this. could you give it top priority on your list if its not fixed yet? 2. Vincent could you put in the pending patch for b? 3.

Re: Commit logs

Am 02.11.2010 um 10:29 schrieb Vincent van Ravesteijn: > >> Log: >> first step to cure the VCS load problem > > Can I please remind you and ask you to write meaningful commit-logs. Logs > explaining why the change has been made, why the new design or solution or > implementation is better,

Re: feature request: edit tex files

On 1. Nov 2010, at 14:22, Jürgen Spitzmüller wrote: > Yann Disser wrote: >> Your arguments make sense. However, I think many people must have my >> problem. Perhaps it would be sufficient to provide a way to keep the .lyx >> file and the .tex file in sync. Whenever one of the two would get

Re: #6871: Missing screen update can cause assertion after lyxserver communication

On 11/02/2010 12:31 PM, LyX Ticket Tracker wrote: Comment(by sanda): >But you will still have a latent bug here. so this 'fix' is still not fixing the root cause, right? Right.

vcs load problem

first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed, why other solutions might be wrong although it may

Re: vcs load problem

Am 02.11.2010 um 12:34 schrieb Vincent van Ravesteijn: > first step to cure the VCS load problem >>> Can I please remind you and ask you to write meaningful commit-logs. Logs >>> explaining why the change has been made, why the new design or solution or >>> implementation is better, what

Re: Commit logs

Log: first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new design or solution or implementation is better, what problem it fixed, why other solutions might be wrong although it

Re: vcs load problem

The VCS load problem is (was) twofold: 1. the parser of the document needs the VCS state so this state (checked by file_found_hook) had to be done earlier. => first step, move it some lines up, above the readDocument() call. Why does the parser need to know the state ? If the state changes,

Re: vcs load problem

Am 02.11.2010 um 12:51 schrieb Stephan Witt: > Am 02.11.2010 um 12:34 schrieb Vincent van Ravesteijn: > >> > first step to cure the VCS load problem Can I please remind you and ask you to write meaningful commit-logs. Logs explaining why the change has been made, why the new

Re: vcs load problem

Vincent van Ravesteijn wrote: > Why does the parser need to know the state ? If the state changes, do we > then reparse the file too ? I think this stumbles on a other design > problem. > > If we have a file, we insert an InsetInfo about vcs, then we add the file > to a vcs, will the InsetInfo

Re: vcs load problem

Stephan Witt wrote: > > The attached patch works. i'm happy the other occurences disappeared... pavel

Re: vcs load problem

Vincent van Ravesteijn wrote: > If we have a file, we insert an InsetInfo about vcs, then we add the file > to a vcs, will the InsetInfo be updated ? Apparently not, apparently the > file is updated not until we parse the file again. it will be updated, when you add file to vcs, its reloaded.

Re: vcs load problem

Am 02.11.2010 um 13:06 schrieb Vincent van Ravesteijn: > The VCS load problem is (was) twofold: 1. the parser of the document needs the VCS state so this state (checked by file_found_hook) had to be done earlier. => first step, move it some lines up, above the

Re: Beta (status update #3)

Stephan Witt wrote: > > if you have the patch already feel free to post it, but... > > I'll attach it - so you get the idea. > > I want to > 1) catch the output of failing system calls to display them in error message > dialog > 2) eventually be able to pass it up to caller for parsing it > 3)

Re: Beta (status update #3)

Vincent van Ravesteijn wrote: > Yes. Ive got something. Wait can you share your timetable? pavel

Re: r35970 - lyx-devel/trunk/src/frontends/qt4

Author: rgheck Date: Mon Nov 1 20:37:59 2010 New Revision: 35970 URL: http://www.lyx.org/trac/changeset/35970 Log: Fix bug #7002. I think this is correct, but Peter should check. May I, may I ? func_ = f; - callInGuiThread(); + if (theApp() == 0)

Re: r35970 - lyx-devel/trunk/src/frontends/qt4

Sorry, Peter already did this. Vincent

Re: r35867 - in lyx-devel/trunk/src/frontends/qt4: . ui

Le 01/11/2010 14:27, Pavel Sanda a écrit : you...@lyx.org wrote: Modified: lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui == --- lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui Wed Oct 27 14:55:57 2010

Re: feature request: edit tex files

> > I agree it would be nice. But it's almost impossible. The problem is that > (La)TeX provides multiple ways (packages) for achieving the same thing. LyX > will never be able to support them all, so either your LaTeX collaborators > will needs to know what LyX supports (which is not what

Re: r35995 - lyx-devel/trunk/src

rgh...@lyx.org wrote: > Author: rgheck > Date: Tue Nov 2 15:50:07 2010 > New Revision: 35995 > URL: http://www.lyx.org/trac/changeset/35995 > > Log: > Make sure that the members of this enum get the same value on every > platform. btw on which platform will this enum starts on non zero number?

Re: feature request: edit tex files

Le 01/11/2010 14:16, Yann Disser a écrit : Well, as I said, with automatic sync I do not think it would be so much of a nightmare anymore. And, for me at least, editing formula-heavy .tex is also not very enjoyable. A typical example of when tex<->lyx breaks with formulas is when people use

Re: RefStyle Patch

Richard Heck a écrit : On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote: Jean-Pierre Chrétien a écrit : So do we have an extra \makeatletter somewhere? Yes, exporting my example file in LaTeX reads: \makeatletter %% LyX specific LaTeX commands.

Re: r35995 - lyx-devel/trunk/src

On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every platform. btw on which platform

Abdel

On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the members of this enum get the same value on every

Re: Abdel

On 11/02/2010 11:34 AM, Abdelrazak Younes wrote: On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL: http://www.lyx.org/trac/changeset/35995 Log: Make sure that the

Re: Abdel

On 11/02/2010 04:35 PM, Richard Heck wrote: On 11/02/2010 11:34 AM, Abdelrazak Younes wrote: On 11/02/2010 04:29 PM, Richard Heck wrote: On 11/02/2010 10:53 AM, Pavel Sanda wrote: rgh...@lyx.org wrote: Author: rgheck Date: Tue Nov 2 15:50:07 2010 New Revision: 35995 URL:

Re: r35995 - lyx-devel/trunk/src

Richard Heck wrote: >>> Log: >>> Make sure that the members of this enum get the same value on every >>> platform. >>> >> btw on which platform will this enum starts on non zero number? >> >> > I don't know for sure. But the file Uwe posted with #7005 had: > \html_math_output -1 >

  1   2   >