Re: [PATCH] show changes when merging and another change tracking bug

2008-10-24 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: >>> It makes sure that the BufferView is updated after doing findNextChange. >>> Abdel, is it how it is supposed to be done? >>> > Yes. OK, applied. JMarc

Re: Patch for 5310 (was: Re: [PATCH] show changes when merging and another change tracking bug)

2008-10-24 Thread José Matos
On Friday 24 October 2008 16:29:22 Jean-Marc Lasgouttes wrote: > Jose'? OK. > JMarc -- José Abílio

Re: [PATCH] show changes when merging and another change tracking bug

2008-10-24 Thread Abdelrazak Younes
On 24/10/2008 17:06, Jean-Marc Lasgouttes wrote: Jean-Marc Lasgouttes<[EMAIL PROTECTED]> writes: The following patch is related to bug 5310 http://bugzilla.lyx.org/show_bug.cgi?id=5310 It makes sure that the BufferView is updated after doing findNextChange. Abdel, is it how it is supposed

Patch for 5310 (was: Re: [PATCH] show changes when merging and another change tracking bug)

2008-10-24 Thread Jean-Marc Lasgouttes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > Then a more annoying problem occurs: in findnextChange, we have the code > > // avoid crash (assertion violation) if the imaginary end-of-par > // character of the last paragraph of the document is marked as changed > if (tip.at_

Re: [PATCH] show changes when merging and another change tracking bug

2008-10-24 Thread Jean-Marc Lasgouttes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > The following patch is related to bug 5310 > http://bugzilla.lyx.org/show_bug.cgi?id=5310 > > It makes sure that the BufferView is updated after doing findNextChange. > Abdel, is it how it is supposed to be done? Oops. svndiff src Index: src/Bu

[PATCH] show changes when merging and another change tracking bug

2008-10-24 Thread Jean-Marc Lasgouttes
The following patch is related to bug 5310 http://bugzilla.lyx.org/show_bug.cgi?id=5310 It makes sure that the BufferView is updated after doing findNextChange. Abdel, is it how it is supposed to be done? Then a more annoying problem occurs: in findnextChange, we have the code // avoid