hi,
i started having these linking errs when using monolithic builds...
./.libs/liblyxcore.a(TextClass.o): In function
`__static_initialization_and_destruction_0':
/home/installer/lyx/dbg_1.6/src/TextClass.cpp:112: undefined reference to
`lyx::InsetLayout::InsetLayout()'
./.libs/liblyxcore.a(Tex
> Pavel Sanda wrote:
>> Open math manual.
>> Ctrl+F and Find next "Because all"
>> Toggle Search backwards
>> Twice push Find next button
>> Kaboom!
>>
> Can't reproduce this one
difficult to reproduce, when its already fixed :D
pavel
sebastian guttenberg wrote:
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
Fixed.
Abdel.
Leuven, E. wrote:
ctrl-m
alt m f
Fixed.
From Andre, earlier:
Problems can be solved by the following recipe:
The LyX code 2 in the error can be 'translated' by using insets/InsetCode.h
into 'QUOTE_CODE', and
[EMAIL PROTECTED]:/data/lyx/trunk > g 'new InsetQuote'
src/Text3.cpp: cur.insert(new
Stefan Schimanski wrote:
It's the line which sets the buffer for a new inset.
Yes, I added this line and there was not crash before. I guess the
passed inset is null and it wasn't before. Why would we want to insert a
null inset anyway? That seems like a bigger problem to me.
I had a bad fe
sebastian guttenberg wrote:
Hi all
I get permanently crashes when trying to copy a text that contains
footnotes. The same crash happens when I try to move the same text with
the tools of outline. The backtrace below is from such a try.
I am not 100% sure whether it's the footnote in general, or j
Pavel Sanda wrote:
Open math manual.
Ctrl+F and Find next "Because all"
Toggle Search backwards
Twice push Find next button
Kaboom!
Can't reproduce this one
[EMAIL PROTECTED] ~]$ uname -r && rpm -q qt4
2.6.23.15-137.fc8
qt4-4.3.3-1.fc8
rh
It's the line which sets the buffer for a new inset. I had a bad
feeling about this Buffer* patch for insets and now it bites us with
plenty of segfaults :-/
Stefan
Am 29.02.2008 um 18:12 schrieb Abdelrazak Younes:
Stefan Schimanski wrote:
Does it happen all the time? I cannot reproduce it
Stefan Schimanski wrote:
Does it happen all the time? I cannot reproduce it. It would help a lot
if you find a sequence of keypresses or so to trigger the crash.
Alt-i f
Ctrl-m
A
Happens all the time. Must be a recent commit because it didn't happen
before I svn updated.
Abdel.
Stefan
A
>
> Am 29.02.2008 um 16:46 schrieb Pavel Sanda:
>
>>> Author: sts
>>> Date: Fri Feb 29 11:02:25 2008
>>> New Revision: 23350
>>>
>>> URL: http://www.lyx.org/trac/changeset/23350
>>> Log:
>>> * the automatic arity changing proposed by Uwe: you go into a macro and
>>> type \#9. The arity is visually
Does it happen all the time? I cannot reproduce it. It would help a
lot if you find a sequence of keypresses or so to trigger the crash.
Stefan
Am 29.02.2008 um 16:48 schrieb sebastian guttenberg:
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224735024 (LWP 18784)]
0x0926b0cd in ?? ()
(gdb) bt
#0 0x0926b0cd in ?? ()
#1 0xbfc6007b in ?? ()
#2 0x08b746a0 in ?? ()
#3
Am 29.02.2008 um 16:46 schrieb Pavel Sanda:
Author: sts
Date: Fri Feb 29 11:02:25 2008
New Revision: 23350
URL: http://www.lyx.org/trac/changeset/23350
Log:
* the automatic arity changing proposed by Uwe: you go into a macro
and type \#9. The arity is visually adapted right away. The real
> Author: sts
> Date: Fri Feb 29 11:02:25 2008
> New Revision: 23350
>
> URL: http://www.lyx.org/trac/changeset/23350
> Log:
> * the automatic arity changing proposed by Uwe: you go into a macro and type
> \#9. The arity is visually adapted right away. The real change though takes
> place when y
ctrl-m
alt m f
1
lyx.exe!lyx::InsetMathNest::doDispatch(lyx::Cursor & cur={...},
lyx::FuncRequest & cmd={...}) Line 764 + 0x34 bytesC++
lyx.exe!lyx::Inset::dispatch(lyx::Cursor & cur={...}, lyx::FuncRequest
& cmd={...}) Line 197 + 0x1a bytes C++
lyx.exe!lyx::C
Hi all
I get permanently crashes when trying to copy a text that contains
footnotes. The same crash happens when I try to move the same text with
the tools of outline. The backtrace below is from such a try.
I am not 100% sure whether it's the footnote in general, or just a
special content in the f
> Fixed in r23354.
thanks
pavel
Fixed in r23354.
Stefan
Am 29.02.2008 um 16:02 schrieb Pavel Sanda:
Open math manual.
Ctrl+F and Find next "Because all"
Toggle Search backwards
Twice push Find next button
Kaboom!
Backtraces make life easier:
#4 0x95f756f9 in __gnu_debug::_Error_formatter::_M_error ()
#5 0x00114512 in
__gnu_debug
::_Safe_iterator<__gnu_cxx::__normal_iterator__gnu_norm::vector > >,
__gnu_debug_def::vector >
>::operator-> (this=0xbfffce04) at safe_iterator.h:191
#6 0x00113182 in ly
Open math manual.
Ctrl+F and Find next "Because all"
Toggle Search backwards
Twice push Find next button
Kaboom!
On Feb 29, 2008, at 1:53 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Feb 28, 2008, at 7:55 PM, Pavel Sanda wrote:
you really mean --enable-optimization=-Os ? why not O2 ?
With LyX-1.3, I did some systematic tests. O3 was not noticeably
faster
than O2 or Os, and we thought at the t
Stefan Schimanski schrieb:
I wonder whether it would make sense to make the math toolbar automatic
as well by default.
Opinions?
I absolutely agree to this, also for the table toolbar. This was often requested by users, so that I
already did this in my installer via a default session file. H
> Why do you remove this? It is supposed to be there.
I was confused by this and thought this is one of the reasons that
the macro toolbar dioesn't popup automatically as it should, Sorry.
As discussed in bug 4592 you reverted it already and thanks that you
added a note there to explain tha
> Why do you remove this? It is supposed to be there.
I was confused by this and thought this is one of the reasons that the macro toolbar dioesn't popup
automatically as it should, Sorry. As discussed in bug 4592 you reverted it already and thanks that
you added a note there to explain that it
Uwe Stöhr wrote:
> The attached patch backports the fixes for bug 2461 from trunk to branch.
> OK to go in Jürgen?
Yes (I suppose it's tested well).
Jürgen
Stefan Schimanski wrote:
Am 29.02.2008 um 09:40 schrieb Abdelrazak Younes:
Stefan,
It seems that typing while the completion combo is open trigger a full
redraw each time. I don't know what is the cause of this, it's either
the combo or the grey completion text. In the first case, the combo
Am 29.02.2008 um 09:40 schrieb Abdelrazak Younes:
Stefan,
It seems that typing while the completion combo is open trigger a
full redraw each time. I don't know what is the cause of this, it's
either the combo or the grey completion text. In the first case, the
combo is an external widget
Stefan,
It seems that typing while the completion combo is open trigger a full
redraw each time. I don't know what is the cause of this, it's either
the combo or the grey completion text. In the first case, the combo is
an external widget so it should be independent from the work area
drawing
Am 28.02.2008 um 23:23 schrieb [EMAIL PROTECTED]:
Author: uwestoehr
Date: Thu Feb 28 23:23:15 2008
New Revision: 23341
URL: http://www.lyx.org/trac/changeset/23341
Log:
default.ui: delete a spurious parameter
Modified:
lyx-devel/trunk/lib/ui/default.ui
Modified: lyx-devel/trunk/lib/ui/def
30 matches
Mail list logo
