On 26/07/2019 8:41 PM, Richard Kimberly Heck wrote:
On 7/26/19 12:46 AM, Daniel wrote:
On 2019-07-25 23:40, Andrew Parsloe wrote:
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To
On 7/26/19 12:46 AM, Daniel wrote:
> On 2019-07-25 23:40, Andrew Parsloe wrote:
>> I can create a crash by trying to delete the final column in the
>> following construction:
>>
>>
>> \begin{align*}
>>
>> \begin{aligned}\end{aligned}
>>
>> \\
>>
>> \end{align*}
>>
>>
>> To create:
>>
>>
>> 1.
On 2019-07-25 23:40, Andrew Parsloe wrote:
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To create:
1. Ctrl+Shift+M to create a display math equation.
2. Ctrl+Return to create an
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To create:
1. Ctrl+Shift+M to create a display math equation.
2. Ctrl+Return to create an align* environment
3. Insert > Math > Aligned
Abdelrazak Younes wrote:
I've done enough cleanups for 1.5 ;-)
Does it mean that you won't do any other major cleanups for 1.5?
Actually, I wondering about what needs to be done/is intended to be done
for 1.5 besides adding unicode support. Isn't it time to set up some
kind of roadmap?
Michael Gerz wrote:
Abdelrazak Younes wrote:
I've done enough cleanups for 1.5 ;-)
Does it mean that you won't do any other major cleanups for 1.5?
I guess so yes. Well, unless 1.5 is still far away that is :-)
But if those guys in Denmark fix all remaining issues about unicode,
chances
Abdelrazak Younes wrote:
I've done enough cleanups for 1.5 ;-)
Does it mean that you won't do any other major cleanups for 1.5?
Actually, I wondering about what needs to be done/is intended to be done
for 1.5 besides adding unicode support. Isn't it time to set up some
kind of roadmap?
Michael Gerz wrote:
Abdelrazak Younes wrote:
I've done enough cleanups for 1.5 ;-)
Does it mean that you won't do any other major cleanups for 1.5?
I guess so yes. Well, unless 1.5 is still far away that is :-)
But if those guys in Denmark fix all remaining issues about unicode,
chances
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Hi, This crash was due to an invalid CursorSlice::text()
Abdelrazak null pointer accessed in InsetMathNest::cursorPos():
Abdelrazak CoordCache coord_cache =
Abdelrazak sl.text()-bv()-coordCache();
Abdelrazak As you can
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Hi, This crash was due to an invalid CursorSlice::text()
Abdelrazak null pointer accessed in InsetMathNest::cursorPos():
Abdelrazak CoordCache coord_cache =
Abdelrazak
Georg Baum wrote:
Am Dienstag, 17. Oktober 2006 17:06 schrieb Abdelrazak Younes:
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache coord_cache = sl.text()-bv()-coordCache();
As you can see, I used this
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Nothing wrong per see. But Andre (and I think I agree with
Abdelrazak him) thinks that we should decorrelate the model and the
Abdelrazak view. Passing a BufferView (the view) and a DocIterator
Abdelrazak (the model independent
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak Nothing wrong per see. But Andre (and I think I agree with
Abdelrazak him) thinks that we should decorrelate the model and the
Abdelrazak view. Passing a BufferView (the view) and a DocIterator
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
In the new getPos, you pass 3 parameters that all should com from
one cursor. This is wrong, especially since the method os useful to
find the position of a cursor.
Abdelrazak IMHO, what is wrong really is this cursorPos() method.
Jean-Marc Lasgouttes wrote:
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
In the new getPos, you pass 3 parameters that all should com from
one cursor. This is wrong, especially since the method os useful to
find the position of a cursor.
Abdelrazak IMHO, what is wrong really is
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
I agree that these things should be moved out of insets.
Abdelrazak I've done enough cleanups for 1.5 ;-)
We'll see :)
JMarc
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Hi, This crash was due to an invalid CursorSlice::text()
Abdelrazak> null pointer accessed in InsetMathNest::cursorPos():
Abdelrazak> CoordCache & coord_cache =
Abdelrazak> sl.text()->bv()->coordCache();
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Hi, This crash was due to an invalid CursorSlice::text()
Abdelrazak> null pointer accessed in InsetMathNest::cursorPos():
Abdelrazak> CoordCache & coord_cache =
Abdelrazak>
Georg Baum wrote:
Am Dienstag, 17. Oktober 2006 17:06 schrieb Abdelrazak Younes:
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache & coord_cache = sl.text()->bv()->coordCache();
As you can see, I used this
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Nothing wrong per see. But Andre (and I think I agree with
Abdelrazak> him) thinks that we should decorrelate the model and the
Abdelrazak> view. Passing a BufferView (the view) and a DocIterator
Abdelrazak> (the
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Nothing wrong per see. But Andre (and I think I agree with
Abdelrazak> him) thinks that we should decorrelate the model and the
Abdelrazak> view. Passing a BufferView (the view) and a
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> In the new getPos, you pass 3 parameters that all should com from
>> one cursor. This is wrong, especially since the method os useful to
>> find the position of a cursor.
Abdelrazak> IMHO, what is wrong really is this
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
In the new getPos, you pass 3 parameters that all should com from
one cursor. This is wrong, especially since the method os useful to
find the position of a cursor.
Abdelrazak> IMHO, what is wrong
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> I agree that these things should be moved out of insets.
Abdelrazak> I've done enough cleanups for 1.5 ;-)
We'll see :)
JMarc
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache coord_cache = sl.text()-bv()-coordCache();
As you can see, I used this indirection to access the
BufferView::CoordCache(). Bad luck, the passed CursorSlice was
Abdelrazak Younes wrote:
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache coord_cache = sl.text()-bv()-coordCache();
As you can see, I used this indirection to access the
BufferView::CoordCache(). Bad luck, the
Am Dienstag, 17. Oktober 2006 17:06 schrieb Abdelrazak Younes:
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache coord_cache = sl.text()-bv()-coordCache();
As you can see, I used this indirection to access
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache & coord_cache = sl.text()->bv()->coordCache();
As you can see, I used this indirection to access the
BufferView::CoordCache(). Bad luck, the passed CursorSlice
Abdelrazak Younes wrote:
Hi,
This crash was due to an invalid CursorSlice::text() null pointer
accessed in InsetMathNest::cursorPos():
CoordCache & coord_cache = sl.text()->bv()->coordCache();
As you can see, I used this indirection to access the
BufferView::CoordCache(). Bad luck, the
Am Dienstag, 17. Oktober 2006 17:06 schrieb Abdelrazak Younes:
> Hi,
>
> This crash was due to an invalid CursorSlice::text() null pointer
> accessed in InsetMathNest::cursorPos():
>
> CoordCache & coord_cache = sl.text()->bv()->coordCache();
>
> As you can see, I used this indirection
On Fri, Jan 16, 2004 at 02:23:24PM +0900, Rob Lahaye wrote:
Current CVS with xforms crashes as follows:
Start LyX
File-New
Insert Math
lyx: SIGSEGV signal caught
(Sorry can't make a backtrace at this stage).
Never mind.
I am aware of it.
Andre'
--
Those who desire to give up
On Fri, Jan 16, 2004 at 02:23:24PM +0900, Rob Lahaye wrote:
>
> Current CVS with xforms crashes as follows:
>
> Start LyX
> File->New
> Insert Math
>
> lyx: SIGSEGV signal caught
>
>
> (Sorry can't make a backtrace at this stage).
Never mind.
I am aware of it.
Andre'
--
Those who desire
Hi,
Current CVS with xforms crashes as follows:
Start LyX
File-New
Insert Math
lyx: SIGSEGV signal caught
(Sorry can't make a backtrace at this stage).
Regards,
Rob.
Hi,
Current CVS with xforms crashes as follows:
Start LyX
File->New
Insert Math
lyx: SIGSEGV signal caught
(Sorry can't make a backtrace at this stage).
Regards,
Rob.
When reading the attached file, mathed crashes.
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language american
\inputencoding default
\fontscheme default
\graphics default
\paperfontsize 12
\spacing single
\papersize Default
\paperpackage
Dekel Tsur wrote:
When reading the attached file, mathed crashes.
no problem here with latest cvs
Herbert
--
http://www.lyx.org/help/
On Tue, May 07, 2002 at 05:07:55PM +0300, Dekel Tsur wrote:
When reading the attached file, mathed crashes.
Mine works.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
On Tue, May 07, 2002 at 04:45:16PM +0200, Andre Poenitz wrote:
On Tue, May 07, 2002 at 05:07:55PM +0300, Dekel Tsur wrote:
When reading the attached file, mathed crashes.
Mine works.
Try compiling --with-included-string
On Tue, May 07, 2002 at 06:36:03PM +0300, Dekel Tsur wrote:
Try compiling --with-included-string
Even then.
Could you try to get down to the source of that crash?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T.
When reading the attached file, mathed crashes.
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language american
\inputencoding default
\fontscheme default
\graphics default
\paperfontsize 12
\spacing single
\papersize Default
\paperpackage
Dekel Tsur wrote:
> When reading the attached file, mathed crashes.
no problem here with latest cvs
Herbert
--
http://www.lyx.org/help/
On Tue, May 07, 2002 at 05:07:55PM +0300, Dekel Tsur wrote:
> When reading the attached file, mathed crashes.
Mine works.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
On Tue, May 07, 2002 at 04:45:16PM +0200, Andre Poenitz wrote:
> On Tue, May 07, 2002 at 05:07:55PM +0300, Dekel Tsur wrote:
> > When reading the attached file, mathed crashes.
>
> Mine works.
>
Try compiling --with-included-string
On Tue, May 07, 2002 at 06:36:03PM +0300, Dekel Tsur wrote:
> Try compiling --with-included-string
Even then.
Could you try to get down to the source of that crash?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T.
Hi there
Just found a little bug in LyX 1.0.2 and want to let you know of it.
Thanks for your great work,
Martin
Here's the information how to reproduce it:
HOW TO CRASH IT
===
!All the keyboard shortcuts are for the german version!
* New doc, doesn't matter which class
*
Hi there
Just found a little bug in LyX 1.0.2 and want to let you know of it.
Thanks for your great work,
Martin
Here's the information how to reproduce it:
HOW TO CRASH IT
===
!All the keyboard shortcuts are for the german version!
* New doc, doesn't matter which class
*
46 matches
Mail list logo
