Sorry Peter, I have not found the definition of ‘Q_EMIT’ in Qt-Headers for qt
4.3
...
/usr/src/lyx/lyx-devel/src/frontends/qt4/GuiProgress.cpp: In member function
‘void lyx::frontend::GuiProgress::doClearMessages()’:
/usr/src/lyx/lyx-devel/src/frontends/qt4/GuiProgress.cpp:96: error: ‘Q_EMIT’
w
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > other bug you would like to see killed?
>
> The error dialog is currently completely broken (it doesn't show at all). I
> think this is a pretty nasty bug.
ok
pavel
Pavel Sanda wrote:
> other bug you would like to see killed?
The error dialog is currently completely broken (it doesn't show at all). I
think this is a pretty nasty bug.
Jürgen
Pavel Sanda wrote:
> Alpha - next week if possible
tarball creation is already fixed, monolithic builds checked, short
work with trunk didn't revealed any drastic problems and currently
i monitor two ugly bugs:
- crashes in #6516, there are already some hinst from Peter in trac
- Richard fixed cr
On 05/03/2010 2:38 PM, rgheck wrote:
> On 03/05/2010 11:43 AM, Julien Rioux wrote:
> Missing requirements would obviously be better, since then the user
> knows what to do.
>
Thanks Richard.
Here's a patch for review. Missing packages that prevent a layout from
being available are listed in tex
Pavel Sanda wrote:
* Advanced Search - as far as I can see all wanted features finished, Tommaso?
at least the simple usage scenarios are ok . . .
I expect lot of bug reports here though, we need to wait on users testing.
. . . though, I expect bugs to come up when you try all the thing
Manoj Rajagopalan wrote:
Hi lyx-devel,
Hello,
no need to file another trac request, there's already one (#2548) . . .
http://www.lyx.org/trac/ticket/2548
It would be useful to support this feature because we could perform a
replace-all within a selection and quickly achieve the desired
Le 6 mars 10 à 18:34, José Matos a écrit :
On Saturday 06 March 2010 15:35:49 Pavel Sanda wrote:
hi,
* make dist produces both bzip and gzip files. why do we use both.
wouldn't be bzip one enough? Jose, JMarc?
We try to be conservative and the disc space is not a constraint.
FWIW I would s
Abdelrazak Younes wrote:
>> Is there some cost to leaving the old code in until e.g. #6516 is fixed?
>>
>
> No, we can leave it if this is a blocker of course.
actually it would fine if you could look before alpha on this particular one.
pavel
Darren Freeman wrote:
> Is 2.0 close enough that I should start using it, or shall I get to know
> 1.6.x?
Welcome back, Darren.
Use 1.6.x. LyX 2.0 is not stable enough for serious work (although we are
heading towards something usable).
Jürgen
Hi all,
it's been over two years and I'm back to writing my PhD thesis. I
shudder to think how much has changed since version 1.5 :)
You can expect to hear more from me over the next couple of months.
Is 2.0 close enough that I should start using it, or shall I get to know
1.6.x?
Have fun,
Darr
sp...@lyx.org wrote:
> Author: spitz
> Date: Sun Mar 7 10:29:33 2010
> New Revision: 33656
> URL: http://www.lyx.org/trac/changeset/33656
>
> Log:
> * RELEASE_NOTES:
> - some notes on the spellchecker/thesaurus changes and requirements.
nice, thanks.
pavel
Jürgen Spitzmüller wrote:
> > Jürgen has much better writing skills than me :-P
>
> Very transparent trial. But I'll do it.
Done. Please check if everything is correct.
Jürgen
Abdelrazak Younes wrote:
> >>For the packagers we need some summary what are the recommended
> >>dependencies. Haven't been closely following this stuff - could somebody
> >>write some summary of all those spellcheck (a/i/hun/spell) and thesaurus
> >>deps into RELEASE-NOTES? Juergen, Abdel?
> >
Uwe Stöhr wrote:
> > * long time issue. we are constantly committing tons of senseless
> > diffs of our .po files just because gettext do different line breaking.
> > we should finally resolve this.
> > Uwe, Juergen what gettext version do you have? (0.17 here).
>
> I don't use gettext, I use the
15 matches
Mail list logo
