Jürgen Spitzmüller wrote:
There is one outstanding issue which should be fixed, since it potentially
results in really bad dataloss:
http://bugzilla.lyx.org/show_bug.cgi?id=5813
Apart from that, we are ready.
Unfortunately, I'm totally blocked by real work, so I cannot look into the
Uwe Stöhr wrote:
The mentioned open crash is a special one - only a few users use branches
and child documents together, while the other crashes we fixed affect much
more people.
I was hit myself by that bug, and I almost lost a very important document
_completely_ (btw, in my case, no
Uwe Stöhr wrote:
The mentioned open crash is a special one - only a few users use
branches and child documents together
I do not agree it is a special one.
I won't release 1.6.2 with such a severe bug. The cycle until 1.6.3 is too
long.
I agree, there are no critical bugs anymore to fix, so
Vincent van Ravesteijn - TNW wrote:
Well, this must be fixed.. pretty soon.. I'm just scared to break anything
with the updateMacros mechanism...
I can understand that. I looked into it and shuddered. Is anybody there who
actually understands the mechanism and why the calls are needed in all
Vincent van Ravesteijn - TNW wrote:
Uwe Stöhr wrote:
The mentioned open crash is a special one - only a few users use
branches and child documents together
I do not agree it is a special one.
I won't release 1.6.2 with such a severe bug. The cycle until 1.6.3 is too
long.
I agree,
I was hit myself by that bug, and I almost lost a very important document
_completely_ (btw, in my case, no branch, but a box inset was involved).
I never doubt that this bug is a must fix, but it is also in LyX 1.6.1 and waiting two weeks doesn't
improve anything. When this bug is fixed, LyX
Uwe Stöhr wrote:
The release doesn't make anything worse but LyX in general much more
stable.
I don't take responsibility for a release which _knowingly_ includes a bug
that could destroy other people's work.
If you want LyX 1.6.2 to appear sooner, go ahead and help us fix this bug.
Jürgen
Jürgen Spitzmüller wrote:
Uwe Stöhr wrote:
The release doesn't make anything worse but LyX in general much more
stable.
I don't take responsibility for a release which _knowingly_ includes a bug
that could destroy other people's work.
If you want LyX 1.6.2 to appear sooner, go
Am 06.03.2009 um 16:10 schrieb Pavel Sanda:
Vincent van Ravesteijn - TNW wrote:
Uwe Stöhr wrote:
The mentioned open crash is a special one - only a few users use
branches and child documents together
I do not agree it is a special one.
I won't release 1.6.2 with such a severe bug. The
Jürgen Spitzmüller wrote:
> There is one outstanding issue which should be fixed, since it potentially
> results in really bad dataloss:
> http://bugzilla.lyx.org/show_bug.cgi?id=5813
>
> Apart from that, we are ready.
>
> Unfortunately, I'm totally blocked by real work, so I cannot look into
Uwe Stöhr wrote:
> The mentioned open crash is a special one - only a few users use branches
> and child documents together, while the other crashes we fixed affect much
> more people.
I was hit myself by that bug, and I almost lost a very important document
_completely_ (btw, in my case, no
>Uwe Stöhr wrote:
>> The mentioned open crash is a special one - only a few users use
>> branches and child documents together
I do not agree it is a special one.
>I won't release 1.6.2 with such a severe bug. The cycle until 1.6.3 is too
>long.
I agree, there are no critical bugs anymore to
Vincent van Ravesteijn - TNW wrote:
> Well, this must be fixed.. pretty soon.. I'm just scared to break anything
> with the updateMacros mechanism...
I can understand that. I looked into it and shuddered. Is anybody there who
actually understands the mechanism and why the calls are needed in all
Vincent van Ravesteijn - TNW wrote:
> >Uwe Stöhr wrote:
> >> The mentioned open crash is a special one - only a few users use
> >> branches and child documents together
>
> I do not agree it is a special one.
>
> >I won't release 1.6.2 with such a severe bug. The cycle until 1.6.3 is too
>
> I was hit myself by that bug, and I almost lost a very important document
> _completely_ (btw, in my case, no branch, but a box inset was involved).
I never doubt that this bug is a must fix, but it is also in LyX 1.6.1 and waiting two weeks doesn't
improve anything. When this bug is fixed,
Uwe Stöhr wrote:
> The release doesn't make anything worse but LyX in general much more
> stable.
I don't take responsibility for a release which _knowingly_ includes a bug
that could destroy other people's work.
If you want LyX 1.6.2 to appear sooner, go ahead and help us fix this bug.
Jürgen
Jürgen Spitzmüller wrote:
Uwe Stöhr wrote:
The release doesn't make anything worse but LyX in general much more
stable.
I don't take responsibility for a release which _knowingly_ includes a bug
that could destroy other people's work.
If you want LyX 1.6.2 to appear sooner, go
Am 06.03.2009 um 16:10 schrieb Pavel Sanda:
Vincent van Ravesteijn - TNW wrote:
Uwe Stöhr wrote:
The mentioned open crash is a special one - only a few users use
branches and child documents together
I do not agree it is a special one.
I won't release 1.6.2 with such a severe bug. The
hi,
just found box and note insets do not have open/close item in their context
menu. i'll add them unless comebody complains.
pavel
diff --git a/lib/ui/stdcontext.inc b/lib/ui/stdcontext.inc
index 301608c..74d9d0c 100644
--- a/lib/ui/stdcontext.inc
+++ b/lib/ui/stdcontext.inc
@@ -148,6 +148,9
just found box and note insets do not have open/close
item in their context menu. i'll add them unless comebody
complains.
And if you right-click on the text in an open note or box or inside a
table, you should get the edit menu + inset menu.
Pavel
Vincent
Pavel Sanda wrote:
just found box and note insets do not have open/close item in their
context menu. i'll add them unless comebody complains.
You can submit to 1.6.2svn, if exactly these strings are already in the *.po
files (i.e., including the accelerators). If the commit generates new
Jürgen Spitzmüller wrote:
strings to translate, please wait for 1.6.3.
btw when do you plan to release it?
pavel
Pavel Sanda wrote:
btw when do you plan to release it?
There is one outstanding issue which should be fixed, since it potentially
results in really bad dataloss:
http://bugzilla.lyx.org/show_bug.cgi?id=5813
Apart from that, we are ready.
Unfortunately, I'm totally blocked by real work, so I
hi,
just found box and note insets do not have open/close item in their context
menu. i'll add them unless comebody complains.
pavel
diff --git a/lib/ui/stdcontext.inc b/lib/ui/stdcontext.inc
index 301608c..74d9d0c 100644
--- a/lib/ui/stdcontext.inc
+++ b/lib/ui/stdcontext.inc
@@ -148,6 +148,9
>just found box and note insets do not have open/close
>item in their context menu. i'll add them unless comebody
>complains.
And if you right-click on the text in an open note or box or inside a
table, you should get the edit menu + inset menu.
>Pavel
Vincent
Pavel Sanda wrote:
> just found box and note insets do not have open/close item in their
> context menu. i'll add them unless comebody complains.
You can submit to 1.6.2svn, if exactly these strings are already in the *.po
files (i.e., including the accelerators). If the commit generates new
Jürgen Spitzmüller wrote:
> strings to translate, please wait for 1.6.3.
btw when do you plan to release it?
pavel
Pavel Sanda wrote:
> btw when do you plan to release it?
There is one outstanding issue which should be fixed, since it potentially
results in really bad dataloss:
http://bugzilla.lyx.org/show_bug.cgi?id=5813
Apart from that, we are ready.
Unfortunately, I'm totally blocked by real work, so I
28 matches
Mail list logo
