submenus create black areas on the LyX canvas
Hi, I'm using current LyX-cvs on my Mandrake Linux 7.2 PC. Large black areas are left on the text-canvas, when I do the following: (this is just as an example) - Click on Edit->Math to pop up the Edit menu list and the Math submenu list. - Then click somewhere so that the Math submenu disappears, but not the Edit menu list: click on an Edit-> for example - The space on the LyX canvas that was overlayed with the Math submenu, is now black. - By opening and closing this way more submenus and closing them, I keep creating more such black areas on the LyX canvas. - Only after the Edit menu list is gone, also the black areas will be cleaned up (repaint of the canvas). - Well, only the text area of the LyX canvas is repainted, not the 'command margin' at bottom of the window, nor the scroll bar at the right; these two still show black areas. An older version of LyX (1.1.5fix1) doesn't show these black areas! Any idea what causes this? Rob.
Re: Compile bug in lyx-1.1.6?
<[EMAIL PROTECTED]> writes: >> This depends upon what compiler you use. >> Gcc is mostly well supported. >> >> Lgb [cghan@cellular cghan]$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 2731 (Red Hat Linux 7.0) The problem never occurred with lyx-1.1.5. Regards, cghan
Re: Problem with Citation dialog
On Thu, 15 Feb 2001, Michael Schmitt wrote: > Hello, > > in the citation dialog there is a problem with the OK button: > > 1. Select a citation > 2. Select another citation > 3. Remove one of the two citations > 4. Click on the other citation > --> the OK button is disabled This is the problem Angus is asking ButtonController questions about. It is being worked on and a fix should be available soon. Thanks, Allan. (ARRae)
Re: ButtonController questions
On Thu, 15 Feb 2001, Angus Leeming wrote: > Allan, > > why have you made ButtonController::valid() a "Passthrough function -- > returns its input value"? It isn't used as such. Can I make it a void > function please? It seemed like a good idea at the time. I thought it might be used in a way similar to readOnly() is used so made it a pass through. > I think that I'll modify my trigger_change_ vector and associated methods to > dont_trigger_change_ because FL_OBJECTs that trigger a callback to InputCB > but shoudn't trigger a change in the state of the Ok,Apply buttons are much > rarer than those that should. Maybe they shouldn't have callbacks at all then? The point of input is to do input checking and make changes to interface as appropriate. > What do you mean by "I think you're attacking the problem from the wrong > end"? Do you mean that callbacks from these FL_OBJECTs should not be dealt > with by input(), but by another method, say internalInput(). This would be > exactly equivalent to my solution I think. If a callback from something is checked by input() and input() decides that there is invalid data when you think there isn't any there is a bug. Right? The bug is either that input() shouldn't have been called or a check in input() is wrong. I'm inclined to believe the second possibility since the user has obviously done something to the interface for input() to have been called. SO, which check in input() is saying there is invalid data? If you want to use input() to also monitor if the contents of the dialog have changed and thereby decide if the Ok & Apply buttons should be [de]activated you could do this explicitly by checking against a copy of the contents when it was first show()n. But, this shouldn't be necessary because the state machine should transition to a modified state and stay there until the user Cancels. Any invalid input transitions to MODIFIED_INVALID or something like that name. So the only problem, as I see it, is why is it transitioning to MI when it should still be in M? Some test in input says that the input is invalid. Or perhaps more likely, a test is trying to do the work of the button controller and enforce some policy change. This is a major no-no. input() should only test input validity and nothing else. The button policy defines all policy decisions. Mixing the two does not work and violates all the assumptions. In simple terms, for the case you are trying to fix, clicking on an existing reference _is_ a valid input. Although I'd be inclinded to say it isn't an input at all but a selection. Allan. (ARRae)
Latest CVS: make dist error
It looks like a quick fix... I am running too fast to make the patch, just reporting this: make[1]: Entering directory `/home/kayvan/src/lyx/src' make[1]: *** No rule to make target `bibforms.h', needed by `distdir'. Stop. make[1]: Leaving directory `/home/kayvan/src/lyx/src' -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc.| Laura Isabella Sylvan | Katherine Yelena http://www.successlinks.com/kayvan | Reach your goals now! | Robin Gregory
Re: May a document require 6 (six!) LaTeX runs?
On Thu, Feb 15, 2001 at 09:55:12PM +0100, Michael Schmitt wrote: > Hi, Hi, > > when starting LaTeX from within LyX 1.1.6cvs, it takes 6 (!) runs to produce a > dvi file for one of my documents. Is it possible that a document requires so > many iterations or does this indicate a LyX problem? Even a dvi update requires > as many runs. For further investigation, enclosed please find the LaTeX log. It > seem to indicate that even after the last run some labels may have changed. Hyperref woes. I've seen it on my thesis too (: (that I couldn't pdflatex directly with LyX BTW, as bad packages interractions required graphics to be placed before babel. Oh, well...) So the constant should be a bit larger > > Regards, Michael > > -- > == > Michael Schmittphone: +49 451 500 3725 > Institute for Telematics secretary: +49 451 500 3721 > Medical University of Luebeck fax: +49 451 500 3722 > Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] > D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de > == -- Yves
Re: 1.1.6fix1 stability?
Dear Jules, I wouldn't say that 1.1.6fix1 is unstable in the sense that it crashes regularly. In fact, it hasn't crashed a single time even though I use it aggressively. And, of course, there are many new improvements, e.g., a totally revised menu structure, that show how hard the LyX developers have worked on this release. However, it is my impression that 1.1.6 has been released a bit too early because, e.g., the table handling is incomplete and causes a lot of pain in practice. >From a user's point I recommend to continue to work with 1.1.5fix2 (which is _very_ stable) and to wait until the childhood diseases of 1.1.6 have vanished. I am sure that these great LyX guys will provide solutions very soon. Regards, Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de ==
Problem with Citation dialog
Hello, in the citation dialog there is a problem with the OK button: 1. Select a citation 2. Select another citation 3. Remove one of the two citations 4. Click on the other citation --> the OK button is disabled Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de ==
May a document require 6 (six!) LaTeX runs?
Hi, when starting LaTeX from within LyX 1.1.6cvs, it takes 6 (!) runs to produce a dvi file for one of my documents. Is it possible that a document requires so many iterations or does this indicate a LyX problem? Even a dvi update requires as many runs. For further investigation, enclosed please find the LaTeX log. It seem to indicate that even after the last run some labels may have changed. Regards, Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de == This is TeX, Version 3.14159 (Web2C 7.3.1) (format=latex 2000.10.3) 15 FEB 2001 21:42 **phd.tex (phd.tex LaTeX2e <1999/12/01> patch level 1 Babel and hyphenation patterns for american, french, german, ngerman, i talian, portuges, spanish, swedish, nohyphenation, loaded. (/usr/share/texmf/tex/latex/koma-script/scrreprt.cls Document Class: scrreprt 1999/12/29 v2.5h LaTeX2e KOMA document class (/usr/share/texmf/tex/latex/base/size11.clo File: size11.clo 1999/09/10 v1.4a Standard LaTeX file (size option) ) (/usr/share/texmf/tex/latex/koma-script/typearea.sty Package: typearea 1999/12/29 v2.5h LaTeX2e KOMA package Package: typearea, Copyright (C) Frank Neukam, 1992-1994 Copyright (C) Markus Kohm, 1994-1999 \ta@bcor=\dimen102 \ta@div=\count79 \ta@hblk=\dimen103 \ta@vblk=\dimen104 \ta@temp=\dimen105 Package typearea Info: These are the values describing the layout: (typearea) DIV = 12 (typearea) BCOR = 42.67912pt (typearea) \paperwidth = 597.50793pt (typearea) \textwidth = 416.12161pt (typearea) DIV-departure = -6/100 (typearea) \evensidemargin = 20.20148pt (typearea) \oddsidemargin = 16.64487pt (typearea) \paperheight = 845.04694pt (typearea) \textheight = 609.40027pt (typearea) \topmargin = -1.84941pt (typearea) \headheight = 17.0pt (typearea) \headsep= 20.40001pt (typearea) \topskip= 11.0pt (typearea) \footskip = 47.60002pt (typearea) \baselineskip = 13.6pt (typearea) on input line 502. ) \c@part=\count80 \c@chapter=\count81 \c@section=\count82 \c@subsection=\count83 \c@subsubsection=\count84 \c@paragraph=\count85 \c@subparagraph=\count86 \c@figure=\count87 \c@table=\count88 \abovecaptionskip=\skip41 \belowcaptionskip=\skip42 \bibindent=\dimen106 ) (/usr/share/texmf/tex/latex/base/fontenc.sty Package: fontenc 1999/12/08 v1.9x Standard LaTeX package (/usr/share/texmf/tex/latex/base/t1enc.def File: t1enc.def 1999/12/08 v1.9x Standard LaTeX file LaTeX Font Info:Redeclaring font encoding T1 on input line 38. )) (/usr/share/texmf/tex/generic/babel/babel.sty Package: babel 1999/09/09 v3.6Z The Babel package (/usr/share/texmf/tex/generic/babel/english.ldf Language: english 1999/04/11 v3.3i English support from the babel system (/usr/share/texmf/tex/generic/babel/babel.def File: babel.def 1999/09/09 v3.6Z Babel common definitions \babel@savecnt=\count89 \U@D=\dimen107 ))) (/usr/share/texmf/tex/latex/graphics/graphics.sty Package: graphics 1999/02/16 v1.0l Standard LaTeX Graphics (DPC,SPQR) (/usr/share/texmf/tex/latex/graphics/trig.sty Package: trig 1999/03/16 v1.09 sin cos tan (DPC) ) (/usr/share/texmf/tex/latex/config/graphics.cfg) Package graphics Info: Driver file: dvips.def on input line 80. (/usr/share/texmf/tex/latex/graphics/dvips.def File: dvips.def 1999/02/16 v3.0i Driver-dependant file (DPC,SPQR) )) (/usr/share/texmf/tex/latex/algorith/algorithm.sty Package: algorithm Document Style `algorithm' - floating environment (/usr/share/texmf/tex/latex/misc/float.sty Package: float 1999/05/29 v1.2d Float enhancements (AL) \c@float@type=\count90 \float@box=\box26 \@floatcapt=\box27 ) (/usr/share/texmf/tex/latex/base/ifthen.sty Package: ifthen 1999/09/10 v1.1b Standard LaTeX ifthen package (DPC) ) \c@algorithm=\count91 ) (/usr/share/texmf/tex/latex/misc/subfigure.sty Package: subfigure 1995/03/06 v2.0 subfigure package Package: subfigure 1995/03/06 v2.0 \c@subfigure=\count92 \c@lofdepth=\count93 \c@subtable=\count94 \c@lotdepth=\count95 ) (/usr/share/texmf/tex/latex/tools/verbatim.sty Package: verbatim 2000/01/07 v1.5m LaTeX2e package for verbatim enhancements \every@verbatim=\toks14 \verbatim@line=\toks15 \verbatim@in@stream=\read1 ) (/usr/share/texmf/tex/latex/ae/ae.sty Package: ae 1998/11/17 1.0 Almost European Computer Modern (/usr/share/texmf/tex/latex/base/fontenc.sty Package: fontenc 1999/12/08 v1.9x Standard LaTeX package (/usr/share/texm
Re: Localized: Failure to update dvi, ps files
The bug remains after applying the patch.
> Can you try the following patch ?
>
> Index: LaTeX.C
> ===
> RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/LaTeX.C,v
> retrieving revision 1.37
> diff -u -p -r1.37 LaTeX.C
> --- LaTeX.C 2001/02/03 12:27:21 1.37
> +++ LaTeX.C 2001/02/15 10:28:05
> @@ -608,7 +608,7 @@ void LaTeX::deplog(DepTable & head)
>
> string logfile = OnlyFilename(ChangeExtension(file, ".log"));
>
> - LRegex reg1(")* *\\(([^ \\)]+).*");
> + LRegex reg1("\\)* *\\(([^ \\)]+).*");
> LRegex reg2("File: ([^ ]+).*");
> LRegex reg3("No file ([^ ]+)\\..*");
> LRegex reg4("openout[0-9]+.*=.*`([^ ]+)'\\..*");
>
Re: Bug in 1.1.6fix1: LaTeX very slow
Hello, On Thu, Feb 15, 2001 at 01:03:13PM +0100, Bernd Harmsen wrote: > At the moment I am compiling lyx-1.1.6fix1 on my stable debian2.2 box > with libstdc++2.10. Maybe the problem does not occurre with this older > library. It will take some time, because of the slower cpu. I will > report afterwards. The problem does not occurre on a Debian2.2 Potato (stable) Box mit the libstdc++2.10 library from gcc-2.95.3. Debian Woddy (testing) uses the libstdc++2.10-glibc2.2 from gcc-2.95.3. There the problem occurres. On Thu, Feb 15, 2001 at 03:06:34PM +0200, Dekel Tsur wrote: > Can you pinpoint the problem ? > I suspect the problem is the line ostr << ifs.rdbuf() in lyx::sum. > Try compiling with the attached lyxsum.C You are right. The time was consumed in: Line:two = lyx::sum(f); Method: DepTable::insert File:DebTable.C I have compiled lyx again with your lyxsum.C on my testing system. But it seems to make no difference. Thanks for your hint, any other suggestions. Bernd
1.1.6fix1 stability?
Hi all, I'm thinking of packaging a new version of lyx for debian, since I have shamefully not updated it since the deadkeys bugged one. However, i've been a little alarmed by all the crash reportss I've seen for 1.1.6fix1. Is my impression right that it's less stable than 1.1.5? Should I wait for fix2? Jules
Re: Next style question
> You are allowed to look at code outside the mathed dir you know... Somebody should have told me ;-} Andre' -- André Pönitz [EMAIL PROTECTED]
Re: mathed21.diff
> Can you recreate this (if needed to avoid ) so that we wont get
> conflicts.
I attach a new diff against my current tree.
Note that two files are empty now and could be removed..
Andre'
--
André Pönitz [EMAIL PROTECTED]
? mathed22.diff
? .math_draw.C.swp
? mathedbug.diff
? mathed16.diff
? mathed21.diff
? .ChangeLog.swp
? mathed19.diff
? mathed17.diff
? mathed18.diff
? mathed20.diff
Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.29
diff -u -p -u -r1.29 ChangeLog
--- ChangeLog 2001/02/15 12:22:01 1.29
+++ ChangeLog 2001/02/15 13:10:19
@@ -1,3 +1,20 @@
+
+2001-02-15 André Pönitz <[EMAIL PROTECTED]>
+
+ * math_bigopinset.C:
+ * math_accentinset.C:
+ * math_fracinset.C:
+ * math_matrixinset.C:
+ * math_panel.C:
+ * math_root.C:
+ * formula.C: reformatting
+
+ * math_delim.C:
+ * math_draw.C: are empty now!
+
+ * math_support.[Ch]: move search_deco(int code)
+
+
2001-02-15 Lars Gullik Bjønnes <[EMAIL PROTECTED]>
* matriz.C: clean up a bit.
Index: math_bigopinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_bigopinset.C,v
retrieving revision 1.3
diff -u -p -u -r1.3 math_bigopinset.C
--- math_bigopinset.C 2001/02/15 12:22:01 1.3
+++ math_bigopinset.C 2001/02/15 13:10:19
@@ -39,8 +39,7 @@ MathedInset * MathBigopInset::Clone()
}
-void
-MathBigopInset::draw(Painter & pain, int x, int y)
+void MathBigopInset::draw(Painter & pain, int x, int y)
{
string s;
short t;
@@ -52,19 +51,19 @@ MathBigopInset::draw(Painter & pain, int
s = name;
t = LM_TC_TEXTRM;
}
+
if (sym == LM_oint) {
pain.arc(x, y - 5 * width / 4, width, width, 0, 360*64,
LColor::mathline);
++x;
}
+
pain.text(x, y, s, mathed_get_font(t, size()));
}
-void
-MathBigopInset::Metrics()
+void MathBigopInset::Metrics()
{
- //char c;
string s;
short t;
@@ -76,9 +75,11 @@ MathBigopInset::Metrics()
s = name;
t = LM_TC_TEXTRM;
}
+
mathed_string_height(t, size(), s, ascent, descent);
width = mathed_string_width(t, size(), s);
- if (sym == LM_oint) width += 2;
+ if (sym == LM_oint)
+ width += 2;
}
Index: math_delim.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_delim.C,v
retrieving revision 1.18
diff -u -p -u -r1.18 math_delim.C
--- math_delim.C2001/02/15 12:22:01 1.18
+++ math_delim.C2001/02/15 13:10:19
@@ -1,64 +0,0 @@
- /*
- * File:math_delim.C
- * Purpose: Draw delimiters and decorations
- * Author: Alejandro Aguilar Sierra <[EMAIL PROTECTED]>
- * Created: January 1996
- * Description: Vectorial fonts for simple and resizable objets.
- *
- * Dependencies: Xlib, XForms
- *
- * Copyright: 1996, Alejandro Aguilar Sierra
- *
- * Version: 0.8beta, Mathed & Lyx project.
- *
- * You are free to use and modify this code under the terms of
- * the GNU General Public Licence version 2 or later.
- */
-
-#include
-
-#include FORMS_H_LOCATION
-#include
-#include "symbol_def.h"
-#include "math_inset.h"
-#include "LColor.h"
-#include "Painter.h"
-#include "math_deliminset.h"
-#include "mathed/support.h"
-
-using std::sort;
-using std::lower_bound;
-using std::endl;
-
-/*
- * Internal struct of a drawing: code n x1 y1 ... xn yn, where code is:
- * 0 = end, 1 = line, 2 = polyline, 3 = square line, 4= square polyline
- */
-
-
-
-//inline
-//int odd(int x) { return ((x) & 1); }
-
-//typedef float matriz_data[2][2];
-
-//const matriz_data MATIDEN= { {1, 0}, {0, 1}};
-
-//extern int mathed_char_width(short type, int style, byte c);
-//extern int mathed_char_height(short, int, byte, int &, int &);
-
-//#define mateq(m1, m2) memcpy(m1, m2, sizeof(matriz_data))
-
-
-
-
-
-
-
-
-
-
-// If we had exceptions we could return a reference in stead and not
-// have to check for a null pointer in mathed_draw_deco
-
-
Index: math_dotsinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_dotsinset.C,v
retrieving revision 1.3
diff -u -p -u -r1.3 math_dotsinset.C
--- math_dotsinset.C2001/02/15 12:22:01 1.3
+++ math_dotsinset.C2001/02/15 13:10:19
@@ -17,32 +17,31 @@ MathedInset * MathDotsInset::Clone()
}
-void
-MathDotsInset::draw(Painter & pain, int x, int y)
+void MathDotsInset::draw(Painter & pain, int x, int y)
{
mathed_draw_deco(pain, x + 2, y - dh, width - 2, ascent, code);
- if (code == LM_vdots || code == LM_ddots) ++x;
-
Re: Next style question
Andre Poenitz <[EMAIL PROTECTED]> writes:
| class foo {
| public:
| ///
| void do_it();
| private:
| ///
| int x_;
| };
Thsi one.
You are allowed to look at code outside the mathed dir you know...
Lgb
Re: mathed21.diff
Andre Poenitz <[EMAIL PROTECTED]> writes: | Mainly whitespace again... Can you recreate this (if needed to avoid ) so that we wont get conflicts. Lgb | | Andre' | | -- | André Pönitz [EMAIL PROTECTED]
Re: Bug in 1.1.6fix1: LaTeX very slow
Moin, moin On Wed, Feb 14, 2001 at 10:16:42PM +0100, Yves Bastide wrote: > > > The problem seems to come from libstdc++, at least on my Debian > > > unstable machine.. It's the parsing of the log file which is excruciating > > > slow, IIRC. > I think it's the getline() call in the while loop, in LaTeX::scanLogFile > (src/LaTeX.C), which scans the .log file produced. But I never bothered to > investigate (with at least the debug versions of the libraries, since > I thought I was the only person affected, and using stlport solved this > problem... :-) I have investigated this a bit. The method (?) LaTeX::scanLogFile is realy fast for me. There is no time problem. The time was consumed in LaTeX:run with the following calls: - head.insert(file,true); - deplog(head); - head.update(); Each of this calls needs 5-10 minutes on my Pentium III 800. > > I have installed libstlport, libstlport-dbg & libstlport-dev 4.1 > > Can you give me a hint how to use this lib? > I think this will do the trick: > $ CPPFLAGS=-I/usr/include/stlport LIBS=-lstlport ./configure > Oh, I forgot: this is STLport 4.1beta, and there is a bug in > /usr/include/stlport/stl/_istream.h. Fix attached. Ok, thank you for this hint. But I think it's not a good way to make lyx depend on a beta library that needs Bugfixes. I will try that later, if there is no other solution. At the moment I am compiling lyx-1.1.6fix1 on my stable debian2.2 box with libstdc++2.10. Maybe the problem does not occurre with this older library. It will take some time, because of the slower cpu. I will report afterwards. Bernd
ButtonController questions
Allan,
why have you made ButtonController::valid() a "Passthrough function --
returns its input value"? It isn't used as such. Can I make it a void
function please?
I think that I'll modify my trigger_change_ vector and associated methods to
dont_trigger_change_ because FL_OBJECTs that trigger a callback to InputCB
but shoudn't trigger a change in the state of the Ok,Apply buttons are much
rarer than those that should.
What do you mean by "I think you're attacking the problem from the wrong
end"? Do you mean that callbacks from these FL_OBJECTs should not be dealt
with by input(), but by another method, say internalInput(). This would be
exactly equivalent to my solution I think.
Angus
aleem@pneumon:xforms-> grep -n "valid(" *.C | grep -v nvalid
ButtonController.C:151:bool ButtonController::valid(bool v, FL_OBJECT * obj)
ButtonController.C:180: valid(false);
FormBase.C:173: pre->bc_.valid(pre->input(ob, data), ob);
FormDocument.C:396:pre->bc_.valid(pre->CheckDocumentInput(0,0));
FormInset.C:98: bc_.valid(); // so that the user can press Ok
FormPreferences.C:1855:
pre->bc_.valid(pre->input(reinterpret_cast(combox), 0));
FormPrint.C:199:bc_.valid();
FormTabularCreate.C:57: bc_.valid(true);
Re: Localized: Failure to update dvi, ps files
On Thu, Feb 15, 2001 at 12:33:48PM +0200, Dekel Tsur wrote: > On Wed, Feb 14, 2001 at 06:54:32PM -0500, Mark van Rossum wrote: > > > > Lyx 1.1.6 failed updating the dvi file in some cases. > > Can you try the following patch ? One more thing: In LaTeX::deplog, why aren't we checking if foundfile exists when foundfile is an absolute path ?
Re: Localized: Failure to update dvi, ps files
On Wed, Feb 14, 2001 at 06:54:32PM -0500, Mark van Rossum wrote:
>
> Lyx 1.1.6 failed updating the dvi file in some cases.
>
> It happens when '\usepackage{harvard}' is present in the Latex preamble.
> This probably screws up the depedency files in the temp dir (see
> attachement)
> When commented out (%\usepackage{harvard}) , the bug disappears.
>
> The bug occurs on lyx compiled on RH7 with gcc 2.96
> The rpm package does not show the bug.
>
> Enough info ? Can somebody fix it ?
Can you try the following patch ?
Index: LaTeX.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/LaTeX.C,v
retrieving revision 1.37
diff -u -p -r1.37 LaTeX.C
--- LaTeX.C 2001/02/03 12:27:21 1.37
+++ LaTeX.C 2001/02/15 10:28:05
@@ -608,7 +608,7 @@ void LaTeX::deplog(DepTable & head)
string logfile = OnlyFilename(ChangeExtension(file, ".log"));
- LRegex reg1(")* *\\(([^ \\)]+).*");
+ LRegex reg1("\\)* *\\(([^ \\)]+).*");
LRegex reg2("File: ([^ ]+).*");
LRegex reg3("No file ([^ ]+)\\..*");
LRegex reg4("openout[0-9]+.*=.*`([^ ]+)'\\..*");
Next style question
class foo {
public:
///
void do_it();
private:
///
int x_;
};
or
class foo {
public:
///
void do_it();
private:
///
int x_;
};
or
class foo
{
public:
///
void do_it();
private:
///
int x_;
};
or
class foo
{
public:
///
void do_it();
private:
///
int x_;
};
or
... ?
Andre'
--
André Pönitz [EMAIL PROTECTED]
