Re: [patch] Some old work

2004-07-18 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > > | I don't have the energy to argue one way or the other. Too much > | exercise is as bad as too litle. > > And you just leave me flumoxed(?). Very good! Where _do_ you learn your English?!? -- Angus

Re: {bug] InsetIterator and DocIterator unusable with std::algorithms

2004-07-18 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: > > | Changes should be made so that the regular stl::algorithms can be used > | with InsetIterator and DocIterator. ...and the bug is? Oh well... > Hmm it seems that the DocIterator and StableDocIterator are not reall

Re: [patch] LyXSocket cleanup

2004-07-18 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > At least I find it a bit nicer. Comments/Objections? You go on to use 'MAX_CLIENTS' below, so don't cull it here: Index: lyxsocket.C - fd_(lyx::support::socktools::listen(addr, MAX_CLIENTS)), + fd_(lyx::support::socktools::listen(addr, 3)), In Engl

Re: [patch] LyXSocket cleanup

2004-07-18 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: > >> At least I find it a bit nicer. Comments/Objections? > | You go on to use 'MAX_CLIENTS' below, so don't cull it here: > | Index: lyxsocket.C | - fd_(lyx::support::socktools::listen(addr, MAX_CLIENTS)), | +

Re: [patch] LyXSocket cleanup

2004-07-18 Thread Angus Leeming
Lars Gullik Bjønnes wrote: > So no substantial objections to this patch then? Q (Angus): Do things continue to work after your patch is applied? A (Lars): Of course, or else I would not be suggesting applying this patch. What objection could I make, therefore, given that a feature freeze is meani

Re: [patch] LyXSocket cleanup

2004-07-18 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: >> So no substantial objections to this patch then? > | Q (Angus): Do things continue to work after your patch is applied? | A (Lars): Of course, or else I would not be suggesting applying this patch. So you are saying that I

Re: [patch] LyXSocket cleanup

2004-07-18 Thread John Levon
On Sun, Jul 18, 2004 at 01:38:33PM +0200, Lars Gullik Bj?nnes wrote: > Here is an updated patch as well, gets rid fo the data_recieved > function in qt socket_callback. You've tested this carefully to make *sure* it works? connect() does NO compile time checking. In fact, I'd be very surprised

Re: [patch] LyXSocket cleanup

2004-07-18 Thread Lars Gullik Bjønnes
John Levon <[EMAIL PROTECTED]> writes: | On Sun, Jul 18, 2004 at 01:38:33PM +0200, Lars Gullik Bj?nnes wrote: > >> Here is an updated patch as well, gets rid fo the data_recieved >> function in qt socket_callback. > | You've tested this carefully to make *sure* it works? No :-) it is more "this

Re: [patch] LyXSocket cleanup

2004-07-18 Thread John Levon
On Sun, Jul 18, 2004 at 04:18:13PM +0200, Lars Gullik Bj?nnes wrote: > it is more "this should obviously work, else qt is braindead"... but > we already know the answer to that I guess Indeed. It's best to not touch Qt /at all/ unless you're fully prepared to test every changed line... > Is it

Re: tex2lyx shortcoming

2004-07-18 Thread Georg Baum
Am Samstag, 17. Juli 2004 15:48 schrieb Juergen Spitzmueller: > I don't care for that. BTW we also have > \begin_inset LatexCommand \bibtex[bibtotoc,diss]{diss} > or > \begin_inset LatexCommand \bibtex[diss][btPrintCited]{diss} > which does not even exist as a LaTeX command > or > \begin_inset Late

Re: tex2lyx shortcoming

2004-07-18 Thread Juergen Spitzmueller
Georg Baum wrote: > Am Samstag, 17. Juli 2004 15:48 schrieb Juergen Spitzmueller: > > I don't care for that. BTW we also have > > \begin_inset LatexCommand \bibtex[bibtotoc,diss]{diss} > > or > > \begin_inset LatexCommand \bibtex[diss][btPrintCited]{diss} > > which does not even exist as a LaTeX co