Hi again.
I've traced this cgi export bug into filetools.C (MakeDisplayPath) and
from there to lstrings.C and it is stuck in this loop.
while ((i = lstr.find(oldstr, i)) != string::npos) {
lyxerr << "while subst " << i << endl;
lstr.replace(i, olen, newstr
Hi all,
An update on this problem and a few questions...
I've traced the hang into src/lyxtextclass.C - LyXTextClass::load().
Specifically, the following line (~855) is where execution heads toward
500MB.
loaded_ = const_cast(this)->Read(real_file) == 0;
I've built the CVS and still get t
On Sat, Aug 13, 2005 at 01:56:22PM +0200, Andre Poenitz wrote:
> Btw, I don't really like BOOST_ASSERT (as well as the 'traditional'
> ASSERT) as it does not offer a possibility to specify what should happen
> in the failure case. Most failure conditions are not critical for the
> appliction, but
Hi all,
the list seems really quite. :-)
For sometime I had the idea of separating the handling of the preamble
from the rest of the header. Finally in Paris I have come to the conclusion
that it really should be in a different part of the document.
Even although we are in a deep free
On Tue, Aug 02, 2005 at 10:19:59PM +0200, Jean-Marc Lasgouttes wrote:
> > "John" == John Spray <[EMAIL PROTECTED]> writes:
>
> John> Hi, Attached patch hacks around a crash I encountered scrolling
> John> through the user guide in lyx-gtk. It would be nice to track
> John> down what was passin