Hi developers,
I'm trying to build LyX 2.0.0svn from the latest update and compilation of
src/frontends/qt4/GuiProgressView.cpp fails because of the condition
mentioned in the subject.
Any idea on why this might be happening and what I could do?
thanks,
Manoj
On Sunday 03 January 2010 09:40:09 Abdelrazak Younes wrote:
> Happy new year to you all and your respective families!
>
> Abdel.
The same to you all. :-)
2010 seems a promising year for lyx. :-)
--
José Abílio
On 12/31/2009 06:22 PM, rgheck wrote:
LyX accepts these commands and creates a MathSplit inset, but
compilation fails because mathtools.sty is not loaded via validate.
Should we be supporting these? If so, we need to add mathtools.sty to
Features, etc, etc. Or should they be removed?
rh
On 01/03/2010 06:10 AM, Abdelrazak Younes wrote:
H Richard,
I guess this is for you :-)
Wow. I put that assertion there to make sure I'd handled all cases, and
what do you know? I hadn't!
rh
LyX.exe!lyx::doAssert(const char * expr=0x01f22720, const char *
file=0x01f226e8, long line=21
John McCabe-Dansted schreef:
I have not managed to manually reproduce this bug, but it seems to pop
up regularly in keytest, and apparently it can be triggered by a
single keypress (Ctrl-W) in an empty document.
Does it have an obvious cause?
No. It's something I've never seen before.
Vinc
On Sun, Jan 3, 2010 at 9:14 PM, Pavel Sanda wrote:
> hehehe. you should really try to use it in a real life. just consider we are
> having different header for lyx 1.6.4, lyx 1.6.5, so single resave will do MC
Then there are all the hundreds of changes to open/close insets. I get
this even with a
へのメールを送信できませんでした。
このメッセージは自動的にメール配信ソフトウェアによって作成されました。
Richard Heck wrote:
>
> As said.
progress part of code is not yet stable, but this particular issue should be
better now.
pavel
Am 03.01.2010 00:35, schrieb Pavel Sanda:
This commit breaks SVN completely: SVN cleanup doesn't help and also no
completely new checkout.
ouch. can you try whether svn works now?
It works now, many thanks.
regards Uwe
we are going to the endless flame, ...
No we're not, I was just wondering whether I was really supposed to
count the rain drops while my colleagues are writing... ;-) I have no
problems with that.
pavel
Vincent
へのメールを送信できませんでした。
このメッセージは自動的にメール配信ソフトウェアによって作成されました。
Vincent van Ravesteijn wrote:
>> the only way how to reasonably avoid merge conflicts which are
>> unresolvable by
>> the normal user.
>
> That's why my colleagues just send me the new file: "If you want to do
> version control, well here is the file and commit it then".
well, the point was that
I have not managed to manually reproduce this bug, but it seems to pop
up regularly in keytest, and apparently it can be triggered by a
single keypress (Ctrl-W) in an empty document.
Does it have an obvious cause?
--
Revision: 32739 (Trunk)
arch x86_64
file:///mnt/big/xp/images/share/Ubuntu904/k
Trying the new version, I was pleased. There is just one point that makes me worry, but I am not really sure if this is a bug in Lyx or KDVI:
Your dvi file is problematic here too (WinVista, MikTeX), it seems there
is a font "min1" missing. When I compile your lyx file there is no
problem at
Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
It feels like it is a bit too specific to have a new rc value just for
showing a warning that only effects a specific case that I don't even
understand that can only happen when using a feature which is probably only
used by you.
i s
へのメールを送信できませんでした。
このメッセージは自動的にメール配信ソフトウェアによって作成されました。
Vincent van Ravesteijn wrote:
> It feels like it is a bit too specific to have a new rc value just for
> showing a warning that only effects a specific case that I don't even
> understand that can only happen when using a feature which is probably only
> used by you.
i still hope there is (or w
Dear developers of Lyx,
since many years I used my old notebook with Lyx 1.3.2 running under SUSE Linux
and I really liked it and used it a lot, to write letters, scripts for lessons
and more. Now I got a new notebook running a RedHat Fedora Linux, but without
Lyx :-((
So I got Lyx 1.6.4.2 (an
Pavel Sanda schreef:
hi,
i would like to introduce new rc for some kind of pop-up (unset by default)
which would
warn about unreleased file lock when working with version control.
any objections?
pavel
It feels like it is a bit too specific to have a new rc value just for
showing a warning
hi,
i would like to introduce new rc for some kind of pop-up (unset by default)
which would
warn about unreleased file lock when working with version control.
any objections?
pavel
H Richard,
I guess this is for you :-)
LyX.exe!lyx::doAssert(const char * expr=0x01f22720, const char *
file=0x01f226e8, long line=212) Ligne 23C++
LyX.exe!lyx::InsetMathDecoration::mathmlize(lyx::MathStream &
os={...}) Ligne 212 + 0x5e octetsC++
>LyX.exe!lyx::mathmlize
Happy new year to you all and your respective families!
Abdel.
On 02/01/2010 03:07, Vincent van Ravesteijn wrote:
Tommaso Cucinotta schreef:
However, in order to implement this, I would need to call the
GuiWorkArea * GuiView::workArea(Buffer & buffer)
on a related note, what is the "Buffer::gui_" field ? What is the
purpose of those "gui delegate" ? If
On 27/12/2009 11:03, kuem...@lyx.org wrote:
Author: kuemmel
Date: Sun Dec 27 11:03:16 2009
New Revision: 32653
URL: http://www.lyx.org/trac/changeset/32653
Log:
no duplicated success messages: one connection is enough
Modified:
lyx-devel/trunk/src/frontends/qt4/GuiView.cpp
Modified: lyx-de
24 matches
Mail list logo
