Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg I could only find one: The error list is not shown if the file
Georg is corrupt. This could probably be fixed by handing the temp
Georg buffer to InsertLyXFile:
Is it really necessary to disconnect, or is it done when the buffer is
deleted?
Jean-Marc Lasgouttes wrote:
Georg I could only find one: The error list is not shown if the file
Georg is corrupt. This could probably be fixed by handing the temp
Georg buffer to InsertLyXFile:
Is it really necessary to disconnect, or is it done when the buffer is
deleted?
It is probably
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg It works perfectly. One minor note: Is the debug message
Georg lyxerr[Debug::DEBUG] pasteSelection sel_index
Georg endl;
Georg in pasteSelection still needed?
I removed the message and committed.
JMarc
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> I could only find one: The error list is not shown if the file
Georg> is corrupt. This could probably be fixed by handing the temp
Georg> buffer to InsertLyXFile:
Is it really necessary to disconnect, or is it done when the buffer is
Jean-Marc Lasgouttes wrote:
> Georg> I could only find one: The error list is not shown if the file
> Georg> is corrupt. This could probably be fixed by handing the temp
> Georg> buffer to InsertLyXFile:
>
> Is it really necessary to disconnect, or is it done when the buffer is
> deleted?
It is
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> It works perfectly. One minor note: Is the debug message
Georg> lyxerr[Debug::DEBUG] << " pasteSelection " << sel_index <<
Georg> endl;
Georg> in pasteSelection still needed?
I removed the message and committed.
JMarc
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg The advantage of my patch is that it uses the existing cut and
Georg paste code and that it will automatically benefit from future
Georg changes to that code.
I thought again about it during the week-end and came up with the
following version
Jean-Marc Lasgouttes wrote:
Georg The advantage of my patch is that it uses the existing cut and
Georg paste code and that it will automatically benefit from future
Georg changes to that code.
I thought again about it during the week-end and came up with the
following version of the
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> The advantage of my patch is that it uses the existing cut and
Georg> paste code and that it will automatically benefit from future
Georg> changes to that code.
I thought again about it during the week-end and came up with the
Jean-Marc Lasgouttes wrote:
> Georg> The advantage of my patch is that it uses the existing cut and
> Georg> paste code and that it will automatically benefit from future
> Georg> changes to that code.
>
> I thought again about it during the week-end and came up with the
> following version of
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg It works if the cursor is in a new empty paragraph. It tries to
Georg eat all available memory (and more) if the cursor is inside a
Georg section.
I cannot see that. Could you give directions?
Georg Unavailable layouts are parsed as errors
Jean-Marc Lasgouttes wrote:
Georg It works if the cursor is in a new empty paragraph. It tries to
Georg eat all available memory (and more) if the cursor is inside a
Georg section.
I cannot see that. Could you give directions?
I tried again and I see now that it does work with small
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> It works if the cursor is in a new empty paragraph. It tries to
Georg> eat all available memory (and more) if the cursor is inside a
Georg> section.
I cannot see that. Could you give directions?
Georg> Unavailable layouts are
Jean-Marc Lasgouttes wrote:
> Georg> It works if the cursor is in a new empty paragraph. It tries to
> Georg> eat all available memory (and more) if the cursor is inside a
> Georg> section.
>
> I cannot see that. Could you give directions?
I tried again and I see now that it does work with
After a lot of head scratching (a first patch with cut and paste, plus
many ruminations on code merging), I came up with the following
patch to fix LyX file insertion. As an added bonus, it fixes the
situation where inInset could be NULL.
I'd appreciate if someone could give it a good testing.
Am Donnerstag, 24. November 2005 16:47 schrieb Jean-Marc Lasgouttes:
After a lot of head scratching (a first patch with cut and paste, plus
many ruminations on code merging), I came up with the following
patch to fix LyX file insertion. As an added bonus, it fixes the
situation where inInset
After a lot of head scratching (a first patch with cut and paste, plus
many ruminations on code merging), I came up with the following
patch to fix LyX file insertion. As an added bonus, it fixes the
situation where inInset could be NULL.
I'd appreciate if someone could give it a good testing.
Am Donnerstag, 24. November 2005 16:47 schrieb Jean-Marc Lasgouttes:
>
> After a lot of head scratching (a first patch with cut and paste, plus
> many ruminations on code merging), I came up with the following
> patch to fix LyX file insertion. As an added bonus, it fixes the
> situation where
18 matches
Mail list logo