On Saturday 03 November 2007 05:44:44 Andre Poenitz wrote:
A solution for back-and-forward conversions in the final script would be
some 'obsoleted in format n' property. So lyx2lyx would skip parts
that are obsoleted if the target format has a higher version, yet in
between it will do the
On Wed, Nov 07, 2007 at 01:15:45PM -0500, José Matos wrote:
On Saturday 03 November 2007 05:44:44 Andre Poenitz wrote:
A solution for back-and-forward conversions in the final script would be
some 'obsoleted in format n' property. So lyx2lyx would skip parts
that are obsoleted if the target
On Saturday 03 November 2007 05:44:44 Andre Poenitz wrote:
> A solution for back-and-forward conversions in the final script would be
> some 'obsoleted in format n' property. So lyx2lyx would skip parts
> that are obsoleted if the target format has a higher version, yet in
> between it will do the
On Wed, Nov 07, 2007 at 01:15:45PM -0500, José Matos wrote:
> On Saturday 03 November 2007 05:44:44 Andre Poenitz wrote:
> > A solution for back-and-forward conversions in the final script would be
> > some 'obsoleted in format n' property. So lyx2lyx would skip parts
> > that are obsoleted if the
Bo Peng wrote:
During a fast-evolving period like this, with no public release in
between, reversion of lyx2lyx is IMHO acceptable
I think we discussed this sufficiently now. It doesn't matter in which release
perdiod we are.
Jürgen
On Sat, Nov 03, 2007 at 01:12:24AM +0200, Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
OK, I've done some cleanup an the crashes are gone but the inset
layouts
are broken!
Martin, Richard, do you have an idea here? I don't
On Sat, Nov 03, 2007 at 12:29:39AM +0100, Uwe Stöhr wrote:
During a fast-evolving period like this, with no public release in
between, reversion of lyx2lyx is IMHO acceptable.
But this introduces crashed: I can for example not open Stefan's macro
example file, see my just sent post on the
Andre Poenitz wrote:
On Sat, Nov 03, 2007 at 01:12:24AM +0200, Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I
Bo Peng wrote:
> During a fast-evolving period like this, with no public release in
> between, reversion of lyx2lyx is IMHO acceptable
I think we discussed this sufficiently now. It doesn't matter in which release
perdiod we are.
Jürgen
On Sat, Nov 03, 2007 at 01:12:24AM +0200, Martin Vermeer wrote:
> On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
>
> ...
>
> > >> OK, I've done some cleanup an the crashes are gone but the inset
> > >> layouts
> > >> are broken!
> > >>
> > >> Martin, Richard, do you have
On Sat, Nov 03, 2007 at 12:29:39AM +0100, Uwe Stöhr wrote:
> > During a fast-evolving period like this, with no public release in
> > between, reversion of lyx2lyx is IMHO acceptable.
>
> But this introduces crashed: I can for example not open Stefan's macro
> example file, see my just sent post
Andre Poenitz wrote:
On Sat, Nov 03, 2007 at 01:12:24AM +0200, Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Program received signal
Bo Peng wrote:
On Nov 2, 2007 6:45 AM, Helge Hafting [EMAIL PROTECTED] wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token:
On Nov 2, 2007 6:45 AM, Helge Hafting [EMAIL PROTECTED] wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token: `\begin_manifest'
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
I can do that, no problem.
I though lyx2lyx would do such things anyway though,
I did not want to complicate lyx2lyx by adding another reversion
function to remove this section.
or that the unknown stuff would be lost the next time I save
a changed file?
Yes. (But the trunk crashes quite
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16 in
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
Abdelrazak Younes wrote:
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I don't know if we shall we
fix Inset::getLayout() or if we shall assume that each inset hard-code
its own layout.
OK, I see that the
I can do that, no problem.
I though lyx2lyx would do such things anyway though,
I did not want to complicate lyx2lyx by adding another reversion
function to remove this section.
This won't complicate lyx2lyx, that's what lyx2lyx is for. Removing stuff manually from a LyX file
using an
On Nov 2, 2007 3:47 PM, Uwe Stöhr [EMAIL PROTECTED] wrote:
I can do that, no problem.
I though lyx2lyx would do such things anyway though,
I did not want to complicate lyx2lyx by adding another reversion
function to remove this section.
This won't complicate lyx2lyx, that's what
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV,
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a recent document - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I don't know if we shall we
fix Inset::getLayout() or if we shall assume that
Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
I fought with this fruitlessly until Jean-Marc showed me. You
reverted to my old non-working code :-(
Calm down, I found a better solution (appended below, I guess you cannot
read lyx-cvs?).
Yes,
During a fast-evolving period like this, with no public release in
between, reversion of lyx2lyx is IMHO acceptable.
But this introduces crashed: I can for example not open Stefan's macro example file, see my just
sent post on the list.
Besides this we have the general problem that LyX can
But this introduces crashed: I can for example not open Stefan's macro
example file, see my just
sent post on the list.
As far as I know, today's crash is caused by some insets, not \begin manifest.
Bo
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Program received signal
Bo Peng wrote:
On Nov 2, 2007 6:45 AM, Helge Hafting <[EMAIL PROTECTED]> wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token:
On Nov 2, 2007 6:45 AM, Helge Hafting <[EMAIL PROTECTED]> wrote:
> Start lyx, open a "recent document" - assert.
>
> Case one (A11.lyx, beamer presentation)
>
> Handling unknown body token: `\begin_manifest'
> Handling unknown body token: `\end_manifest'
> Handling unknown body token:
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
> I can do that, no problem.
> I though lyx2lyx would do such things anyway though,
I did not want to complicate lyx2lyx by adding another reversion
function to remove this section.
> or that the unknown stuff would be lost the next time I save
> a changed file?
Yes. (But the trunk crashes
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
> Start lyx, open a "recent document" - assert.
>
> Case one (A11.lyx, beamer presentation)
...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xa62949b0 (LWP 10363)]
> 0x0832ec16 in
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
Abdelrazak Younes wrote:
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I don't know if we shall we
fix Inset::getLayout() or if we shall assume that each inset hard-code
its own layout.
OK, I see that the
>> I can do that, no problem.
>> I though lyx2lyx would do such things anyway though,
>
> I did not want to complicate lyx2lyx by adding another reversion
> function to remove this section.
This won't complicate lyx2lyx, that's what lyx2lyx is for. Removing stuff manually from a LyX file
using
On Nov 2, 2007 3:47 PM, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
> >> I can do that, no problem.
> >> I though lyx2lyx would do such things anyway though,
> >
> > I did not want to complicate lyx2lyx by adding another reversion
> > function to remove this section.
>
> This won't complicate
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> > On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
> >> Start lyx, open a "recent document" - assert.
> >>
> >> Case one (A11.lyx, beamer presentation)
> > ...
> >> Program received
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
> >> OK, I've done some cleanup an the crashes are gone but the inset layouts
> >> are broken!
> >>
> >> Martin, Richard, do you have an idea here? I don't know if we shall we
> >> fix Inset::getLayout() or if we shall
Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
I fought with this fruitlessly until Jean-Marc showed me. You
reverted to my old non-working code :-(
Calm down, I found a better solution (appended below, I guess you cannot
read lyx-cvs?).
Yes,
> During a fast-evolving period like this, with no public release in
> between, reversion of lyx2lyx is IMHO acceptable.
But this introduces crashed: I can for example not open Stefan's macro example file, see my just
sent post on the list.
Besides this we have the general problem that LyX
> But this introduces crashed: I can for example not open Stefan's macro
> example file, see my just
> sent post on the list.
As far as I know, today's crash is caused by some insets, not \begin manifest.
Bo
44 matches
Mail list logo