Abdelrazak Younes wrote:
> Yes, it should be true but as I said, I cannot reproduce the bug so I
> guess it will be true for me.
It also doesn't always crash for me (but very often).
> I'll try to debug that today to verify that.
Please let me know if I can do something.
Jürgen
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
While I agree with you, I also agree with Dov that we should branch 1.5
now...
I'm not opposed to that, but it's up to José.
Well, as the baby is supposed to land in your hand very soon now (how
many time I said this? ;-)) I think your opin
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I cannot reproduce the crash under windows but this looks familiar to an
old crash you had with the Toc if you remember.
I rather think it's a remainder of bug 3258. Note that in the backtrace, line
3497 in InsetTabular::doDispatch is reached
Richard Heck wrote:
Jürgen Spitzmüller wrote:
Richard Heck wrote:
Comments welcome.
Could you please wait until 1.5.0 is done?
Sorry, didn't mean to distract you. It just seems as if most of us are
waiting for 1.5.0 to be done---there are a few things left, not
unimportant things,
Jürgen Spitzmüller wrote:
Richard Heck wrote:
I've done this: patch attached. That said, just removing the option from
the dialog won't do anything one way or another about old files in which
it exists. Those files will still be loaded with that option, and it
won't be handled properly.
Mayb
Abdelrazak Younes wrote:
> While I agree with you, I also agree with Dov that we should branch 1.5
> now...
I'm not opposed to that, but it's up to José.
Jürgen
Richard Heck wrote:
Another issue is that the Edit>Text Style menu could become very
crowded.
I can imagine a menu containing the last 10 styles used only. The last
menu item would launch a dialog with a list view (or a tree view) or all
available menu.
It'd be nice to be able to define cha
Richard Heck wrote:
> Sorry, didn't mean to distract you. It just seems as if most of us are
> waiting for 1.5.0 to be done---there are a few things left, not
> unimportant things, but not much for most of us to do
On the contrary, this is attracting me, and I try to be resistant ;-)
Jürgen
Jürgen Spitzmüller wrote:
Dov Feldstern wrote:
So far, though, these two patches have mostly been ignored --- a few
people have responded, but not many.
You're not ignored. I agree that these patches should be considered, but I
don't understand the stuff enough to comment (and I'm too busy fo
Jürgen Spitzmüller wrote:
Richard Heck wrote:
Comments welcome.
Could you please wait until 1.5.0 is done?
Sorry, didn't mean to distract you. It just seems as if most of us are
waiting for 1.5.0 to be done---there are a few things left, not
unimportant things, but not much for mos
Enrico Forestieri wrote:
On Wed, Jul 18, 2007 at 03:21:52AM +0300, Dov Feldstern wrote:
Hi!
Attached find a lyx2lyx for patch 1820. It's not perfect, though --- it
actually corrupts some files which shouldn't be changed at all; if
anyone wants to try and fix that, be my guest, I've just spen
Richard Heck wrote:
> Comments welcome.
Could you please wait until 1.5.0 is done?
Jürgen
Richard Heck wrote:
> There are several large issues with this dialog collected in bug 3893.
> It really doesn't work very well. Here is a radical suggestion: Get rid
> of it in favor of character styles. So we'd have character styles like
> Italic, SmallCaps, and the like, accessed via the Edit>Te
Richard Heck wrote:
> I've done this: patch attached. That said, just removing the option from
> the dialog won't do anything one way or another about old files in which
> it exists. Those files will still be loaded with that option, and it
> won't be handled properly.
>
> Maybe that's OK for now,
I've uploaded a patch to bugzilla
http://bugzilla.lyx.org/show_bug.cgi?id=3309#c3
that adds collapsible character styles, so you can do this:
CharStyle Endnote
InsetType Collapsable
LatexType Command
LatexName endnote
Preamble
\usepackage{endnotes}
EndPreamble
End
and sud
There are several large issues with this dialog collected in bug 3893.
It really doesn't work very well. Here is a radical suggestion: Get rid
of it in favor of character styles. So we'd have character styles like
Italic, SmallCaps, and the like, accessed via the Edit>Text Styles menu,
rather
Abdelrazak Younes wrote:
> > It should, but you need another OK.
>
> OK from me.
José?
Jürgen
Dov Feldstern wrote:
> So far, though, these two patches have mostly been ignored --- a few
> people have responded, but not many.
You're not ignored. I agree that these patches should be considered, but I
don't understand the stuff enough to comment (and I'm too busy for testing).
I think you s
Enrico Forestieri wrote:
On Wed, Jul 18, 2007 at 03:21:52AM +0300, Dov Feldstern wrote:
Hi!
Attached find a lyx2lyx for patch 1820. It's not perfect, though --- it
actually corrupts some files which shouldn't be changed at all; if
anyone wants to try and fix that, be my guest, I've just s
On Wed, Jul 18, 2007 at 03:21:52AM +0300, Dov Feldstern wrote:
> Hi!
>
> Attached find a lyx2lyx for patch 1820. It's not perfect, though --- it
> actually corrupts some files which shouldn't be changed at all; if
> anyone wants to try and fix that, be my guest, I've just spent the past
> six
Uwe Stöhr wrote:
Jürgen requested that I fix bug 2787:
http://bugzilla.lyx.org/show_bug.cgi?id=2787
for LyX 1.5.0.
I did this in the attached patch. (I can do the same for the
translated manuals when I get the OK.)
But when applying this, the "generate hyperlink" option in the URL
dialog is
Dov Feldstern wrote:
I've spent an enormous amount of time on getting these two bugs fixed
for 1.5.0, since we realized that they involve format changes. I think
I deserve to have them applied and tested, even if it means postponing
the release for a week or two. I already suggested how we can
Hi!
I've spent an enormous amount of time on getting these two bugs fixed
for 1.5.0, since we realized that they involve format changes. I think I
deserve to have them applied and tested, even if it means postponing the
release for a week or two. I already suggested how we can do this
without
Hi!
Attached find a lyx2lyx for patch 1820. It's not perfect, though --- it
actually corrupts some files which shouldn't be changed at all; if
anyone wants to try and fix that, be my guest, I've just spent the past
six hours on this and I'm not sure that it's doable.
Also, this has only conv
Jürgen requested that I fix bug 2787:
http://bugzilla.lyx.org/show_bug.cgi?id=2787
for LyX 1.5.0.
I did this in the attached patch. (I can do the same for the translated manuals
when I get the OK.)
But when applying this, the "generate hyperlink" option in the URL dialog is then senseless (perh
The attached documentation patch fixes
http://bugzilla.lyx.org/show_bug.cgi?id=3798
It also converts depend.py to UTF-8 format that we use for all Python scripts
in LyX 1.5.
Can this go in José?
regards Uwe
Index: depend.py
===
---
Bo Peng wrote:
So if you think that bug 3582 is solved, I'd propose to put that into
1.5.0.
It should, but you need another OK.
OK from me.
Abdel.
So if you think that bug 3582 is solved, I'd propose to put that into 1.5.0.
It should, but you need another OK.
Bo
Bo Peng wrote:
> The problem seems to be solved, but I can not figure out when an ERT
> inset will occupy the rest of the line during edition. E.g.
This is the unsavoury "wide() thing" (TM).
The rule is: an inset spans the whole line, if
- it is the only thing in the row
and
- the cursor is insid
José Matos wrote:
On Tuesday 17 July 2007 15:02:42 Mostafa Vahedi wrote:
The patch sent by Dov is OK. I am really sorry for being late in replying
to the emails. These days I have too many things TODO.
OK then.
Mostafa
Committed as 19105.
Dov
On 7/17/07, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote:
Bo Peng wrote:
> There is also a redraw problem when you delete in ERT or listings
> inset, do you also have an oneliner? :-)
Try this (OK, a bit more than one line).
The problem seems to be solved, but I can not figure out when an ERT
Abdelrazak Younes wrote:
> I cannot reproduce the crash under windows but this looks familiar to an
> old crash you had with the Toc if you remember.
I rather think it's a remainder of bug 3258. Note that in the backtrace, line
3497 in InsetTabular::doDispatch is reached,
if (!is_deleted
Bo Peng wrote:
> There is also a redraw problem when you delete in ERT or listings
> inset, do you also have an oneliner? :-)
Try this (OK, a bit more than one line).
Jürgen
Index: src/rowpainter.cpp
===
--- src/rowpainter.cpp (Revis
On 7/17/07, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote:
- New Document
- Insert 1x1 tabular (one cell)
- type "foo" inside cell
- hit DEL
=> crash
I can confirm this. A really easy way to crash lyx.
Bo
Jose:
The test case of bug 3404 has multiple consecutive
\begin_deeper
\begin_deeper
\end_deeper
\end_deeper
and an \end_layout is inserted before each \begin_deeper. This leads
to excessive \end_layout.
I am *not* familiar with lyx 1.3.x format and I do not know if there
are valid cases whe
Abdelrazak Younes wrote:
> I just committed a fix in the std declaration, does that help?
No.
Jürgen
Jürgen Spitzmüller wrote:
- New Document
- Insert 1x1 tabular (one cell)
- type "foo" inside cell
- hit DEL
=> crash
I cannot reproduce the crash under windows but this looks familiar to an
old crash you had with the Toc if you remember.
I just committed a fix in the std declaration, does th
- New Document
- Insert 1x1 tabular (one cell)
- type "foo" inside cell
- hit DEL
=> crash
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47819059702400 (LWP 29034)]
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x00a11d53 in lyx::Inset
This bug was reported in the users list.
The problem was with the translation of the following piece:
\begin_inset LatexCommand
\url{http://www.worldscinet.com/ijmpc/mkt/guidelines.s
html}
\end_inset
lyx2lyx was expecting the whole command to be in the same line so it left that
html} alone in
On Tuesday 17 July 2007 15:02:42 Mostafa Vahedi wrote:
> The patch sent by Dov is OK. I am really sorry for being late in replying
> to the emails. These days I have too many things TODO.
OK then.
> Mostafa
--
José Abílio
Bo Peng wrote:
> There is also a redraw problem when you delete in ERT or listings
> inset, do you also have an oneliner? :-)
No, unfortunately not.
Jürgen
Jürgen Spitzmüller wrote:
- our source files are encoded in latin 1 (your patch mangles names with
special characters, such as "Bjønnes")
Shouldn't we convert that to utf8 before 1.5.0? I remind you that we
need to do that for layouts too.
Abdel.
On 7/17/07, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote:
This oneliner fixes some ugly drawing artefacts with insets in the appendix
(probably introduced with revision 19039).
There is also a redraw problem when you delete in ERT or listings
inset, do you also have an oneliner? :-)
Bo
Tommaso Cucinotta wrote:
> Added a new patch.
Hi Tommaso,
this is just to let you know that we are actually noticing what you are
doing :-) You might be aware that we are busy with getting 1.5.0 out (and in
feature freeze), so you will have to be a bit patient.
I have applied your patch and ha
The patch sent by Dov is OK. I am really sorry for being late in replying to
the emails. These days I have too many things TODO.
Mostafa
-
Need a vacation? Get great deals to amazing places on Yahoo! Travel.
On Sunday 15 July 2007 18:02:46 Dov Feldstern wrote:
> Files from pre-249 are wrong, but post-249 don't have the problem. So my
> new stage (277) should only run on files which originated at pre-249...
> Currently, since I'm running on everything, I'm trying to "fix" things
> which aren't broken...
On Tuesday 17 July 2007 14:25:23 Jürgen Spitzmüller wrote:
> This oneliner fixes some ugly drawing artefacts with insets in the appendix
> (probably introduced with revision 19039).
>
> Attached also a testcase where you can see the artefacts.
>
> OK to apply?
OK.
> Jürgen
--
José Abílio
This oneliner fixes some ugly drawing artefacts with insets in the appendix
(probably introduced with revision 19039).
Attached also a testcase where you can see the artefacts.
OK to apply?
Jürgen
Index: src/rowpainter.cpp
===
---
Abdelrazak Younes ha scritto:
I'll try to look at the Controller code tommorrow.
Obviously, the controller was missing. Added a new patch.
T.
On Friday 13 July 2007 13:16:46 Anders Ekberg wrote:
> I have tried to address Georg's and Juergen's comments.
> To avoid data-loss, the function is only run if the encoding is auto
> or default and there are no language changes (overly conservative,
> but possible to work around, as commented in t
On Tuesday 17 July 2007 11:28:26 Abdelrazak Younes wrote:
> Quite frankly, I don't think there's anybody but Mostafa. Even though
> there is other users the only difference with the patch is, AFAIU, that
> the number in the output will be in the correct order. This was clearly
> a bug in LyX latex
José Matos wrote:
On Tuesday 17 July 2007 10:52:13 Abdelrazak Younes wrote:
"arabi" was not supported up until recently (1.5 only) so there was no
users of it, only Mostafa recently for Farsi.
I know that. But we have already released pre-releases with the support on
it and we want our user
On Tuesday 17 July 2007 10:52:13 Abdelrazak Younes wrote:
> "arabi" was not supported up until recently (1.5 only) so there was no
> users of it, only Mostafa recently for Farsi.
I know that. But we have already released pre-releases with the support on
it and we want our users to take the pre-
José Matos wrote:
On Monday 16 July 2007 20:17:44 Dov Feldstern wrote:
This is technically a format change, though I would again argue that we
should *not* create a lyx2lyx for it. However, if this is not
acceptable, a lyx2lyx patch should be relatively simple; and that only
underlines the need
On Monday 16 July 2007 20:17:44 Dov Feldstern wrote:
> This is technically a format change, though I would again argue that we
> should *not* create a lyx2lyx for it. However, if this is not
> acceptable, a lyx2lyx patch should be relatively simple; and that only
> underlines the need for applying
José Matos wrote:
On Tuesday 17 July 2007 09:43:12 Abdelrazak Younes wrote:
There's nothing much to think about IMO. The two patches are fixing
_real_ crashes:
Close to the final release any patch that is not a one line makes me
nervous, no matter if they fix crashes or not. :-)
I underst
On Tuesday 17 July 2007 09:43:12 Abdelrazak Younes wrote:
> There's nothing much to think about IMO. The two patches are fixing
> _real_ crashes:
Close to the final release any patch that is not a one line makes me
nervous, no matter if they fix crashes or not. :-)
> * delete_hideSignal.patch:
José Matos wrote:
On Monday 16 July 2007 18:46:55 Abdelrazak Younes wrote:
OK, Jose shall I commit?
OK.
Done.
Please note that I have two other patches pending...
I know, I am a slow thinker. :-)
There's nothing much to think about IMO. The two patches are fixing
_real_ crashes:
*
58 matches
Mail list logo
