Hi, Abdel,
I am compiling the latest trunk (r14281) using msvc and get our
familiar 'can not open file libboost_signals-vc80-mt-s-1_22_1_lib'
error. I grep in the debug/libs directory and find that qt4.lib
depends on this library.
This might be caused by the use of boost headers without config.h
Lars Gullik Bjønnes wrote:
| > and 0.5 developers...
Oh... we are down to that level now...
i agree 0.5 is not a lot (and, as bo pointed out, it's friday)
...
as you write, there is frustration on many sides.
this needs to be sorted out one way or the other.
putting one's heels in the sand
"Bo Peng" <[EMAIL PROTECTED]> writes:
| So you mean we can ignore xform and gtk when implementing new
| features? If the value of trunk/xform is only for speed benchmarking,
| we can remove/ignore it totally and use 1.4.x. xform.
*doh* ... I wish some one had made that statement a bit earlier...
We have four frontends because Lars simply loves his xform frontend,
Oh... we are down to that level now...
Not exactly. But today is Friday so a little exaggeration is allowed.
You are of course aware that xforms is broken in the tree right now
because I did not push to have it properly fi
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > > Abdel's retirement really makes me feel sad.
|
| Me too. Abdel has helped me fight the scons war, and was on my side
| for many such situations. If this is not only a Friday vent of anger,
| I may have to retire as well.
Which would be a real pitty.
I
On Fri, Jun 30, 2006 at 02:56:14PM -0500, Bo Peng wrote:
> > I don't know if this is because the cygwin python needs sh for spawning
> > external programs. Someone with a native python should perform the test.
> >
>
> Under linux, when sh is removed, lyx2lyx does not work, although there
> is no
> Abdel's retirement really makes me feel sad.
Me too. Abdel has helped me fight the scons war, and was on my side
for many such situations. If this is not only a Friday vent of anger,
I may have to retire as well.
I said this a couple of times before: We have a project management problem!
W
Michael Gerz wrote:
Hello,
Abdel's retirement really makes me feel sad. I said this a couple of
times before: We have a project management problem! And we lost focus.
> 4 frontends, 3 build systems,
and 0.5 developers...
... unbelievable!
It seems that I have to make a break for some time.
I don't know if this is because the cygwin python needs sh for spawning
external programs. Someone with a native python should perform the test.
Under linux, when sh is removed, lyx2lyx does not work, although there
is no sign of sh being called in lyx2lyx.
You are right, we need to test nativ
Edwin Leuven wrote:
Abdelrazak Younes wrote:
Hello,
I have committed the updated attached patch in the "younes" branch in
case someone would like to continue the clean up work.
i hope that this is not the last thing we see of you
Congratulation, LyX! You lost another ambitious developer
On Fri, Jun 30, 2006 at 09:18:53AM -0500, Bo Peng wrote:
> > >
> > > I like this *a lot* better than executing two commands. If you have
> > > tested it, I will apply it unless I heard some other opinions.
> >
> > Yep, it works.
>
> OK. I will commit it. Please remove your windows/mingw/sh and s
On Fri, Jun 30, 2006 at 06:51:32PM +0200, Enrico Forestieri wrote:
> On Fri, Jun 30, 2006 at 03:56:37PM +0200, Georg Baum wrote:
>
> > Edwin Leuven wrote:
> >
> > > atm i have troubles previewing the document and i somehow connected it
> > > to changing preferences (but i was wrong)
> > >
> > >
Abdelrazak Younes wrote:
Hello,
I have committed the updated attached patch in the "younes" branch in
case someone would like to continue the clean up work.
Cheers,
Abdel.
i hope that this is not the last thing we see of you
On Fri, Jun 30, 2006 at 03:56:37PM +0200, Georg Baum wrote:
> Edwin Leuven wrote:
>
> > atm i have troubles previewing the document and i somehow connected it
> > to changing preferences (but i was wrong)
> >
> > get an error message:
> >
> > file does not exist:
> > c:/tmp/lyx_tmpdir ... /C:_d
Hello,
I have committed the updated attached patch in the "younes" branch in
case someone would like to continue the clean up work.
Cheers,
Abdel.
Index: src/BufferView.C
===
--- src/BufferView.C(revision 14280)
+++ src/Buffer
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | | No because, depending on where you emit the signal your are
| > targetting
| > | this or that slot in particular.
| > But this is instan
>
> I like this *a lot* better than executing two commands. If you have
> tested it, I will apply it unless I heard some other opinions.
Yep, it works.
OK. I will commit it. Please remove your windows/mingw/sh and see if
sh is needed anywhere else.
Bo
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | | No because, depending on where you emit the signal your are
| > targetting
| > | this or that slot in particular.
| > But this is instances of signals, so you are em
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
|
| No because, depending on where you emit the signal your are targetting
| this or that slot in particular.
But this is instances of signals, so you are emitting the signals in
the instance of the class that you are in.
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | > | I'll see what I can do...
| > | > | (See... I am actually prepared to go t
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > I wonder... is this quite true? Do we actully emit qt signals
| > ourselfs? Or only signals that we have declared/defined in a signals:
| > section in a class?
|
| I think both cases are used. That is we do emit signal
Edwin Leuven wrote:
> atm i have troubles previewing the document and i somehow connected it
> to changing preferences (but i was wrong)
>
> get an error message:
>
> file does not exist:
> c:/tmp/lyx_tmpdir ... /C:_data_newfile8.dvi
>
> it doesn't like the semicolon i guess, probably path conv
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | I'll see what I can do...
| > | (See... I am actually prepared to go the extra mile to please you)
| > I am trying to figure out a way s
Georg Baum wrote:
> Anyway, I think we should call python with the -tt flag. The attached
> patch does that, and is going in tomorrow unless I get objections.
This updated patch is going in now.
Georg
Log:
Call python with the -tt switch to make mixed tab/space indentation an error
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > I wonder... is this quite true? Do we actully emit qt signals
| > ourselfs? Or only signals that we have declared/defined in a signals:
| > section in a class?
|
| I think both cases are used. That is we do emit signals inherited from
| Qt signal
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > We cannot continue to have this battle every time you create a new
| > patch.
|
| Right, trusting me a tiny more bit would help.
It is not about trust. It is about not doing too many changes at the
same time.
Actual
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | I'll see what I can do...
| > | (See... I am actually prepared to go the extra mile to please you)
| > I am trying to figure out a way so that a comment is not neede
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | Like so.
| > I see that I missed quite a few emit's.
|
| What? You commit a patch without checking that it compiles?
|
| > I'll fix th
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | Like so.
| > I see that I missed quite a few emit's.
|
| What? You commit a patch without checking that it compiles?
|
| > I'll fix that promptly.
|
| You never q
Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I'll see what I can do...
| (See... I am actually prepared to go the extra mile to please you)
I am trying to figure out a way so that a comment is not needed.
Would been nice if qt signals had a .emit(...) thingie...
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I'll see what I can do...
| (See... I am actually prepared to go the extra mile to please you)
I am trying to figure out a way so that a comment is not needed.
Would been nice if qt signals had a .emit(...) thingie... but
I am pretty sure it doesn
Thanks Asger, you expressed what I meant very clearly.
Abdel.
Lars Gullik Bjønnes wrote:
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| For what it's worth, watching from the sideline, I think that Abdel
| has a point: I think LyX has been micro-managed, and this is slowing
| progress and scaring contributors away.
I might very well be that I micro-man
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| > | Like so.
| > I see that I missed quite a few emit's.
|
| What? You commit a patch without checking that it compiles?
But I did... unfortunately our build system do
Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Like so.
I see that I missed quite a few emit's.
What? You commit a patch without checking that it compiles?
I'll fix that promptly.
You never question whether yours changes are good or not, are you? I am
not
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Like so.
I see that I missed quite a few emit's.
I'll fix that promptly.
--
Lgb
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| For what it's worth, watching from the sideline, I think that Abdel
| has a point: I think LyX has been micro-managed, and this is slowing
| progress and scaring contributors away.
I might very well be that I micro-manage things.
But the issue wi
For what it's worth, watching from the sideline, I think that Abdel has
a point: I think LyX has been micro-managed, and this is slowing
progress and scaring contributors away.
We share the same objective: It is in our common interest to make sure
that all code in LyX has release quality: This
Like so.
Index: src/frontends/qt3/QCommandBuffer.C
===
--- src/frontends/qt3/QCommandBuffer.C (revision 14268)
+++ src/frontends/qt3/QCommandBuffer.C (working copy)
@@ -50,7 +50,7 @@
|| e->x() > width() || e->y() > height()) {
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > We cannot continue to have this battle every time you create a new
| > patch.
|
| Right, trusting me a tiny more bit would help.
It is not about trust. It is about not doing too many changes at the
same time.
Actually, I do trust you, your code
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | * frontends/Timeout:
| > |- emit() renamed to emitSignal() to avoid compiler confusion with Qt
| > | emit() function (change prop
Abdelrazak Younes wrote:
> Because this change will have to be done on all qt code and the
> resulting patch will be bigger than this one. IMO, those changes are
> really minimal, nothing to fuss about.
Well, you see that they create fuss, so why not solve the problem once and
forever?
Nobody wou
Georg Baum wrote:
Abdelrazak Younes wrote:
No, there is a boost macro compatibility flag that I plan to use in the
future for that. This flag will need a change of the "emit", "signals"
and "slot" macros to "Q_EMIT", "Q_SIGNALS" and "Q_SLOT" or something
like that. In the mean time, please acce
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Michael Gerz wrote:
>> >The attached patch (against 1.4svn) should fix it, but since I
>> cannot >reproduce the problem here, Michael or someone who sees it
>> should test. >
>>
>> Looks good. Please commit.
Juergen>
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | * frontends/Timeout:
| > |- emit() renamed to emitSignal() to avoid compiler confusion with Qt
| > | emit() function (change propagated to all frontend).
| >
Juergen Spitzmueller wrote:
Edwin Leuven wrote:
here is a snippet:
What's wrong with this?
mmm, it seems i need another coffee
didn't look close enough
atm i have troubles previewing the document and i somehow connected it
to changing preferences (but i was wrong)
get an error message:
Abdelrazak Younes wrote:
> No, there is a boost macro compatibility flag that I plan to use in the
> future for that. This flag will need a change of the "emit", "signals"
> and "slot" macros to "Q_EMIT", "Q_SIGNALS" and "Q_SLOT" or something
> like that. In the mean time, please accept my timeout
Edwin Leuven <[EMAIL PROTECTED]> writes:
| atm saved preferences end up in my lyx file!
|
| is this related to your recent changes bo?
|
| here is a snippet:
|
| #LyX 1.5.0svn created this file. For more info see http://www.lyx.org/
| \lyxformat 247
| \begin_document
| \begin_header
| \textclas
Edwin Leuven wrote:
> atm saved preferences end up in my lyx file!
I don't see any preferences there. If you meant the \font... settings: Have
a look at development/FORMAT.
Georg
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| * frontends/Timeout:
|- emit() renamed to emitSignal() to avoid compiler confusion with Qt
| emit() function (change propagated to all frontend).
This I do not like.
I agree on the principle but, come on, we d
Edwin Leuven wrote:
> here is a snippet:
What's wrong with this?
Jürgen
On Fri, Jun 30, 2006 at 11:15:23AM +0200, Enrico Forestieri wrote:
> works in the windows shell, too ;-)
^^^
Oops...
--
Enrico
atm saved preferences end up in my lyx file!
is this related to your recent changes bo?
here is a snippet:
#LyX 1.5.0svn created this file. For more info see http://www.lyx.org/
\lyxformat 247
\begin_document
\begin_header
\textclass article
\language english
\inputencoding auto
\font_roman def
On Fri, Jun 30, 2006 at 08:28:52AM +0200, Georg Baum wrote:
> Abdelrazak Younes wrote:
>
> > Indeed, for me neither. Works for other programs though... Surely
> > because it is a graphical program.
>
> No. The reason is that debug output is sent to stderr, not stdout. "lyx -dbg
> info 2> foo.log
On Thu, Jun 29, 2006 at 04:11:10PM -0500, Bo Peng wrote:
> > > Do you want a patch along these lines? I think it is more elegant.
> >
> > Here is my proposed patch.
>
> I like this *a lot* better than executing two commands. If you have
> tested it, I will apply it unless I heard some other opin
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| * frontends/Timeout:
|- emit() renamed to emitSignal() to avoid compiler confusion with Qt
| emit() function (change propagated to all frontend).
This I do not like.
Qt deserves a lot of flak for pushing such common names into
the global n
56 matches
Mail list logo
