I just submitted the following patch.
It is wrong not to save the whole cursor stack as lastFilePos, and it
is more wrong to save top (innermost) level pit and pos. As a result,
if you quit lyx with cursor in an inset, lastFilePos will save pit/pos
within this inset, and will restore the cursor t
Ya, the import took care of the issue.
Richard Heck wrote:
This is from something I checked in, probably, unless headers have been
changed elsewhere. I don't have this problem on Linux. Is this on OSX?
In any event, can you try adding:
#include
to the headers in src/frontends/qt4/QParagraphDi
On Sat, 14 Apr 2007, Michael Gerz wrote:
[EMAIL PROTECTED] schrieb:
Maintaining a list of show stoppers might be easier using bugzilla
directly - I don't know. The page's there now in case anyone wants to use
it.
I don't think it is a good idea to maintain multiple lists of bugs.
I don't
Today's svn-version (Revision: 17807) compiled fine on Mac PPC (OSX
10.4.8). However, there have been some shaky versions in the last
weeks so I have needed to do make clean at some occasions. Also, I
have QT 4.2.3 (with the newly released security patch) and not 4.2.0
if that could be a re
The attached patch fixes
- TeX-code not updated when switchin on the same item row to the opposite
character (bug 3456)
by adding a method that handles the on_click.
- TeX-code incorrectly displayed because the "\" character was set to all
delimiters, also to
e.g."[" as "\[" (bug 3457)
-
> your changes to g-brief2.layout don't look right!
> You mentioned that your patch was 4 years old and thus didn't require any
further discussion.
> However, it seems that you missed a few changes to g-brief2 since 2003.
What exactly? The template file I added to SVN works perfectly with the l
>> (bug 3458)
>> I fixed this by using \backslash instead
>
> I think you can commit this part.
Done.
>> This line makes the dialog crashing when you call it:
>>
>> string stri_left = fromqstr(leftLW->currentItem()->toolTip());
>>
>> What is wrong with this?
The row is i
This is from something I checked in, probably, unless headers have been
changed elsewhere. I don't have this problem on Linux. Is this on OSX?
In any event, can you try adding:
#include
to the headers in src/frontends/qt4/QParagraphDialog.C and see if that
fixes the problem?
Alternatively, can s
I just noticed that the BaKoMa math fonts are not in SVN. Therefore they are missing in all my
svn-builds. If I get no objections. I'll add them tomorrow to /lib/fonts.
- This is important to assure that everbody who compiles LyX have all that is
needed to run LyX
properly after compiling.
-
Uwe Stöhr wrote:
The math delimiter dialog is still buggy. Attached is a patch that fixes
bug 3457 and bug 3458:
- the sequence "\\" must not be used as math delimiters, so currently we
produce LaTeX-errors
(bug 3458)
I fixed this by using \backslash instead
I think you can commit this p
Hi Bo,
Now that you're back to affair here's one that you could put in your
Todo list if possible:
http://bugzilla.lyx.org/show_bug.cgi?id=3171
Nothing major but a bit annoying.
Abdel.
The math delimiter dialog is still buggy. Attached is a patch that fixes bug
3457 and bug 3458:
- the sequence "\\" must not be used as math delimiters, so currently we
produce LaTeX-errors
(bug 3458)
I fixed this by using \backslash instead
- the shown TeX-Code of the selected delimiters i
This is my fault.
moveToPosition would fail to move to a closed inset, with error messages like:
Assertion triggered in virtual void
lyx::InsetCollapsable::cursorPos(const lyx::BufferView&, const
lyx::CursorSlice&, bool, int&, int&) const by failing check "status()
!= Collapsed" in file src/inse
On 4/12/07, Bo Peng <[EMAIL PROTECTED]> wrote:
Create a file A
SaveAs to B
Export xxx exports to A.xxx, instead of B.xxx.
Strange, can not reproduce this any more
Bo
Michael Gerz wrote:
[EMAIL PROTECTED] schrieb:
Modified: lyx-devel/trunk/src/mathed/InsetMathHull.C
URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/mathed/InsetMathHull.C?rev=17794
==
--- lyx-devel/trunk/src/
I will patch my msvc and report back.
With a lot of trouble, I was able to get the patch and compile lyx. It
is irritating that I have to 'sign up' and 'connect' to MS to fix a MS
product, but this is how MS works.
Cheers,
Bo
[EMAIL PROTECTED] schrieb:
Modified: lyx-devel/trunk/src/mathed/InsetMathHull.C
URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/mathed/InsetMathHull.C?rev=17794
==
--- lyx-devel/trunk/src/mathed/InsetMathHull.C (or
[EMAIL PROTECTED] schrieb:
Maintaining a list of show stoppers might be easier using bugzilla
directly - I don't know. The page's there now in case anyone wants to
use it.
I don't think it is a good idea to maintain multiple lists of bugs.
bugzilla is made EXACTLY for the purpose of capturing
Georg Baum wrote:
Am Freitag, 13. April 2007 21:38 schrieb Abdelrazak Younes:
Georg Baum wrote:
I don't share your pessimism, especially
if we are to compare current SVN with the state of 1.4.0 when it was
released.
That is not a good comparison. 1.4.0 should not have been released in
that
On Fri, 13 Apr 2007, Abdelrazak Younes wrote:
So, here is my list of show stoppers:
http: //bugzilla.lyx.org/show_bug.cgi?id=3043
http: //bugzilla.lyx.org/show_bug.cgi?id=3291
http: //bugzilla.lyx.org/show_bug.cgi?id=3346
http: //bugzilla.lyx.org/show_bug.cgi?id=3404
http: //bugzilla.lyx.org/sh
Am Samstag, 14. April 2007 13:17 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > Obviously we have different quality demands concerning a stable
release.
>
> I don't understand how this is a show stopper. The only problem is that
> you have more grey area than needed (ideally there should be
Uwe,
your changes to g-brief2.layout don't look right!
You mentioned that your patch was 4 years old and thus didn't require
any further discussion. However, it seems that you missed a few changes
to g-brief2 since 2003. Moreover, it seems that you changed a few styles
and labels in the wrong
Am Samstag, 14. April 2007 13:13 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > Am Freitag, 13. April 2007 22:07 schrieb Abdelrazak Younes:
> >
> >>> http://bugzilla.lyx.org/show_bug.cgi?id=3449
> >> I'll try to solve this one, even though I know nothing about math
> > macro...
> >
> > Great
Georg Baum wrote:
Am Freitag, 13. April 2007 21:55 schrieb Abdelrazak Younes:
Georg Baum wrote:
If you want something to work on: 3427 was introduced by you with the
metrics reorganization, and it happens always for me.
I don't think this has anything to do with metrics. It is an artefact of
Georg Baum wrote:
Am Freitag, 13. April 2007 22:07 schrieb Abdelrazak Younes:
http://bugzilla.lyx.org/show_bug.cgi?id=3449
I'll try to solve this one, even though I know nothing about math
macro...
Great! Some more info: This has probably nothing to do with macros, but
with a not working Fo
[EMAIL PROTECTED] schrieb:
Author: uwestoehr
Date: Wed Apr 4 03:35:15 2007
New Revision: 17714
Added:
lyx-devel/trunk/lib/layouts/europecv.layout (with props)
lyx-devel/trunk/lib/templates/europeCV.lyx
Uwe,
what is the strategy behind your use of lower and upper case?
Michael
Georg Baum schrieb:
Just look at the traffic on the user list.
There is no such thing as a "lost reputation" in an open source project.
Of course there is. But you can't see that from the mailing list of a
project, because most people who think it is crap simply ignore it and use
somet
Am Freitag, 13. April 2007 22:07 schrieb Abdelrazak Younes:
> > http://bugzilla.lyx.org/show_bug.cgi?id=3449
>
> I'll try to solve this one, even though I know nothing about math
macro...
Great! Some more info: This has probably nothing to do with macros, but
with a not working FontSetChanger.
Am Freitag, 13. April 2007 21:55 schrieb Abdelrazak Younes:
> Georg Baum wrote:
>
> > If you want something to work on: 3427 was introduced by you with the
> > metrics reorganization, and it happens always for me.
>
> I don't think this has anything to do with metrics. It is an artefact of
> the
Am Freitag, 13. April 2007 21:38 schrieb Abdelrazak Younes:
> Georg Baum wrote:
>
> >> I don't share your pessimism, especially
> >> if we are to compare current SVN with the state of 1.4.0 when it was
> >> released.
> >
> > That is not a good comparison. 1.4.0 should not have been released in
30 matches
Mail list logo