On 08.11.2010 02:17, Enrico Forestieri wrote:
> On Mon, Nov 08, 2010 at 01:42:35AM +0100, Peter Kümmel wrote:
>
>> On 08.11.2010 01:15, Enrico Forestieri wrote:
>>> On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
>>>
>>>> Enrico Forestieri
On 08.11.2010 09:13, Jean-Pierre Chrétien wrote:
> Hello,
>
> Here is what I see (Debina lenny, Qt 4.4.3)
>
> g++ -DHAVE_CONFIG_H -I. -I../.. -I./.. -I../../boost -DQT_NO_STL
> -DQT_NO_KEYWORDS -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore
> -Wextra -Wall-g -O -MT
On 08.11.2010 02:17, Enrico Forestieri wrote:
> On Mon, Nov 08, 2010 at 01:42:35AM +0100, Peter Kümmel wrote:
>
>> On 08.11.2010 01:15, Enrico Forestieri wrote:
>>> On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
>>>
>>>> Enrico Forestieri
On 08.11.2010 00:34, Enrico Forestieri wrote:
On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
Richard Heck wrote:
that can be taken out now. However, my sense is that whatever is stopping
compilation with 4.2.x could have been wrapped in #ifs. The
EXPORT_IN_THREAD code
On 08.11.2010 01:15, Enrico Forestieri wrote:
On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
#ifdefs where placed without care. My feeling is that it would not be
at all difficult resolving this.
can you try please?
The link fails because the
On 08.11.2010 00:34, Enrico Forestieri wrote:
> On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
>
>> Richard Heck wrote:
>>> that can be taken out now. However, my sense is that whatever is stopping
>>> compilation with 4.2.x could have been wrapped in #ifs. The
>>>
On 08.11.2010 01:15, Enrico Forestieri wrote:
> On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
>
>> Enrico Forestieri wrote:
>>> #ifdefs where placed without care. My feeling is that it would not be
>>> at all difficult resolving this.
>>
>> can you try please?
>
> The link fails
On 02.11.2010 14:46, Vincent van Ravesteijn wrote:
Sorry, Peter already did this.
Vincent
Sorry, should have dropped a mail to the list.
But it's nice to see others have similar ideas.
Peter
exclude it just out of lazyness. After all, there might still be some
conservative admins out there.
Jürgen
Will a conservative admin install LyX 2?
Peter
On 02.11.2010 14:46, Vincent van Ravesteijn wrote:
> Sorry, Peter already did this.
>
> Vincent
>
Sorry, should have dropped a mail to the list.
But it's nice to see others have similar ideas.
Peter
> exclude it just out of lazyness. After all, there might still be some
> conservative admins out there.
>
> Jürgen
>
Will a conservative admin install LyX 2?
Peter
Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
Most probably Peter,
is there some way how to get rid of this:
maybe
- compiler update
- boost update to 1.44
- using Qt signals
- suppressing the warning -Wno-ignored-qualifiers
CXXForkedCalls.o
Am Montag, den 25.10.2010, 20:30 +0200 schrieb Peter Kümmel:
Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
Most probably Peter,
is there some way how to get rid of this:
maybe
- compiler update
- boost update to 1.44
I've updated boost. (Updating boost was never
- compiler update
- boost update to 1.44
There's a typo in the log message (1.43),
but it IS boost 1.44.
Peter
Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
> Most probably Peter,
>
> is there some way how to get rid of this:
maybe
- compiler update
- boost update to 1.44
- using Qt signals
- suppressing the warning -Wno-ignored-qualifiers
> CXXForkedCalls.o
>
Am Montag, den 25.10.2010, 20:30 +0200 schrieb Peter Kümmel:
> Am Montag, den 25.10.2010, 14:33 +0200 schrieb Pavel Sanda:
> > Most probably Peter,
> >
> > is there some way how to get rid of this:
>
> maybe
> - compiler update
> - boost update to 1.44
I'
> > - compiler update
> > - boost update to 1.44
There's a typo in the log message (1.43),
but it IS boost 1.44.
Peter
Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda:
Richard Heck wrote:
Along these same lines, I wonder if we should pop up an info box when
the export is done. If it takes a while, then the user may not notice the
status message, and those get over-written quickly, anyway.
In
Am Samstag, den 23.10.2010, 12:52 +0200 schrieb Peter Kümmel:
Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda:
Richard Heck wrote:
Along these same lines, I wonder if we should pop up an info box when
the export is done. If it takes a while, then the user may not notice
Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
Peter Kuemmel committed:
http://www.lyx.org/trac/changeset/35795
peter, after your commit, how easy would it be to change the mouse
cursor to Qt::PointingHandCursor when hovering a clickable inset?
thanks, edwin
Sorry, would
Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
There will be never a gtk based gui.
dont you know the plans about ncurses-lyx? :)
I thought there are plans for ASCII-only terminals :)
pavel
But I wonder if there are still active developers who
insist
Am Samstag, den 23.10.2010, 22:27 +0200 schrieb Abdelrazak Younes:
On 23/10/2010 21:42, Peter Kümmel wrote:
Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
Peter Kuemmel committed:
http://www.lyx.org/trac/changeset/35795
peter, after your commit, how
Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
There will be never a gtk based gui.
dont you know the plans about ncurses-lyx? :)
I thought there are plans for ASCII-only terminals :)
pavel
But I wonder if there are still active developers who
insist
Am Samstag, den 23.10.2010, 22:48 +0200 schrieb Peter Kümmel:
Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
There will be never a gtk based gui.
dont you know the plans about ncurses-lyx? :)
I thought there are plans for ASCII-only terminals
Am Samstag, den 23.10.2010, 22:27 +0200 schrieb Abdelrazak Younes:
On 23/10/2010 21:42, Peter Kümmel wrote:
Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
Peter Kuemmel committed:
http://www.lyx.org/trac/changeset/35795
peter, after your commit, how
Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda:
> Richard Heck wrote:
> > Along these same lines, I wonder if we should pop up an info box when
> > the export is done. If it takes a while, then the user may not notice the
> > status message, and those get over-written quickly, anyway.
Am Samstag, den 23.10.2010, 12:52 +0200 schrieb Peter Kümmel:
> Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda:
> > Richard Heck wrote:
> > > Along these same lines, I wonder if we should pop up an info box when
> > > the export is done. If it takes
Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
> Peter Kuemmel committed:
> > http://www.lyx.org/trac/changeset/35795
>
> peter, after your commit, how easy would it be to change the mouse
> cursor to Qt::PointingHandCursor when hovering a clickable inset?
>
> thanks, edwin
Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > There will be never a gtk based gui.
>
> dont you know the plans about ncurses-lyx? :)
I thought there are plans for ASCII-only terminals :)
> pavel
But I wonder if there are still act
Am Samstag, den 23.10.2010, 22:27 +0200 schrieb Abdelrazak Younes:
> On 23/10/2010 21:42, Peter Kümmel wrote:
> > Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
> >
> >> Peter Kuemmel committed:
> >>
> >>> http://www.lyx.org/
Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > There will be never a gtk based gui.
>
> dont you know the plans about ncurses-lyx? :)
I thought there are plans for ASCII-only terminals :)
> pavel
But I wonder if there are still act
Am Samstag, den 23.10.2010, 22:48 +0200 schrieb Peter Kümmel:
> Am Samstag, den 23.10.2010, 21:57 +0200 schrieb Pavel Sanda:
> > Peter Kümmel wrote:
> > > There will be never a gtk based gui.
> >
> > dont you know the plans about ncurses-lyx? :)
>
> I th
Am Samstag, den 23.10.2010, 22:27 +0200 schrieb Abdelrazak Younes:
> On 23/10/2010 21:42, Peter Kümmel wrote:
> > Am Samstag, den 23.10.2010, 18:21 +0200 schrieb Edwin Leuven:
> >
> >> Peter Kuemmel committed:
> >>
> >>> http://www.lyx.org/
A. Am Freitag, den 22.10.2010, 22:34 +0200 schrieb Vincent van
Ravesteijn:
Incidentally, in testing all this, I had LyX crash on me twice. I
don't have time now to get a backtrace, but let me know if you want me
to post one later.
BH
I think the culprit might be in this
Am Sonntag, den 17.10.2010, 18:28 +0200 schrieb Pavel Sanda:
John McCabe-Dansted wrote:
the most problematic cases of our copypaste typically happen when
middle button is used for getting, or puting stuff from/into another
applications and when more lyx instances are used. dunno whether
Am Freitag, den 22.10.2010, 13:28 -0400 schrieb Richard Heck:
i wonder why Alert:: code is affected when no preview or export is done?
It was a bug in InGuiThread.h, see commit message:
bind makes a copy of the arguments by default. This is secure if the
bound object survives the existence of
A. Am Freitag, den 22.10.2010, 22:34 +0200 schrieb Vincent van
Ravesteijn:
> > Incidentally, in testing all this, I had LyX crash on me twice. I
> > don't have time now to get a backtrace, but let me know if you want me
> > to post one later.
> >
> > BH
> >
>
> I think the culprit
Am Sonntag, den 17.10.2010, 18:28 +0200 schrieb Pavel Sanda:
> John McCabe-Dansted wrote:
> > > the most problematic cases of our copy typically happen when
> > > middle button is used for getting, or puting stuff from/into another
> > > applications and when more lyx instances are used. dunno
Am Freitag, den 22.10.2010, 13:28 -0400 schrieb Richard Heck:
> >> i wonder why Alert:: code is affected when no preview or export is done?
It was a bug in InGuiThread.h, see commit message:
"bind makes a copy of the arguments by default. This is secure if the
bound object survives the existence
I agree. But this would mean that all dialog related code must be
removed from the export functions... which would be a good thing in
itself but is a bit more involved than what was originally thought.
The box is open again ;)
Abdel.
whenever in a thread frontend::Alert could send a signal that would be
caught by GuiView in the main thread. Once sent the thread would sleep
up until it receives a signal from GuiView. Upon reception of the
signal, GuiView would execute the required Alert dialog and send a
signal when
On 20.10.2010 14:02, Richard Heck wrote:
On 10/20/2010 05:44 AM, Pavel Sanda wrote:
Peter Kümmel wrote:
I agree. But this would mean that all dialog related code must be
removed from the export functions... which would be a good thing in
itself but is a bit more involved than what
Am Dienstag, den 19.10.2010, 20:40 -0400 schrieb Richard Heck:
I think what's happening is this. If you export pdf (say) without there
already being a pdf file there, then everything is fine. But if the pdf
file exists, then LyX will try to ask the user whether to overwrite.
This means
>
> I agree. But this would mean that all dialog related code must be
> removed from the export functions... which would be a good thing in
> itself but is a bit more involved than what was originally thought.
The "box" is open again ;)
>
> Abdel.
>
>
> whenever in a thread frontend::Alert could send a signal that would be
> caught by GuiView in the main thread. Once sent the thread would sleep
> up until it receives a signal from GuiView. Upon reception of the
> signal, GuiView would execute the required Alert dialog and send a
> signal
On 20.10.2010 14:02, Richard Heck wrote:
> On 10/20/2010 05:44 AM, Pavel Sanda wrote:
>> Peter Kümmel wrote:
>>
>>>> I agree. But this would mean that all dialog related code must be
>>>> removed from the export functions... which would be a good thing in
Am Dienstag, den 19.10.2010, 20:40 -0400 schrieb Richard Heck:
> I think what's happening is this. If you export pdf (say) without there
> already being a pdf file there, then everything is fine. But if the pdf
> file exists, then LyX will try to ask the user whether to overwrite.
> This means
I always have to look for this path in the mailing list.
Don't know if it's in the wiki, at least I couln't find it.
Couldn't we add the link to the download website?
Peter
On 19.10.2010 00:05, Uwe Stöhr wrote:
OK, committed a fix, but it needs testing.
Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide
to PDF (pdflatex).
Maybe the pdf is now in the temp folder. Because the only difference I see is a
flag
in doExport.
regards
On 19.10.2010 08:42, Peter Kümmel wrote:
On 19.10.2010 00:05, Uwe Stöhr wrote:
OK, committed a fix, but it needs testing.
Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide
to PDF (pdflatex).
Maybe the pdf is now in the temp folder. Because the only difference
Am Dienstag, den 19.10.2010, 15:09 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
Couldn't we add the link to the download website?
its already there on very bottom of the page.
No, there's ftp://ftp.lyx.org but not ftp://ftp.devel.lyx.org.
Peter
Am Dienstag, den 19.10.2010, 17:32 -0400 schrieb Richard Heck:
On 10/19/2010 04:32 PM, Uwe Stöhr wrote:
When exporting I get now tons of this message in the LyX console:
QObject::startTimer: timers cannot be started from another thread
QApplication: Object event filter cannot be in a
Am Mittwoch, den 20.10.2010, 01:02 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
Am Dienstag, den 19.10.2010, 15:09 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
Couldn't we add the link to the download website?
its already there on very bottom of the page.
No, there's ftp
I think what's happening is this. If you export pdf (say) without there
already being a pdf file there, then everything is fine. But if the pdf
file exists, then LyX will try to ask the user whether to overwrite.
This means creating a dialog as a child of the parent. But the parent,
I always have to look for this path in the mailing list.
Don't know if it's in the wiki, at least I couln't find it.
Couldn't we add the link to the download website?
Peter
On 19.10.2010 00:05, Uwe Stöhr wrote:
> > OK, committed a fix, but it needs testing.
>
> Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide
> to PDF (pdflatex).
Maybe the pdf is now in the temp folder. Because the only difference I see is a
flag
in doExport.
>
>
On 19.10.2010 08:42, Peter Kümmel wrote:
> On 19.10.2010 00:05, Uwe Stöhr wrote:
>> > OK, committed a fix, but it needs testing.
>>
>> Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide
>> to PDF (pdflatex).
>
> Maybe the pdf is now
Am Dienstag, den 19.10.2010, 15:09 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > Couldn't we add the link to the download website?
>
> its already there on very bottom of the page.
No, there's ftp://ftp.lyx.org but not ftp://ftp.devel.lyx.org.
Peter
Am Dienstag, den 19.10.2010, 17:32 -0400 schrieb Richard Heck:
> On 10/19/2010 04:32 PM, Uwe Stöhr wrote:
> > When exporting I get now tons of this message in the LyX console:
> >
> > QObject::startTimer: timers cannot be started from another thread
> > QApplication: Object event filter cannot be
Am Mittwoch, den 20.10.2010, 01:02 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > Am Dienstag, den 19.10.2010, 15:09 +0200 schrieb Pavel Sanda:
> > > Peter Kümmel wrote:
> > > > Couldn't we add the link to the download website?
> > >
> > &
> I think what's happening is this. If you export pdf (say) without there
> already being a pdf file there, then everything is fine. But if the pdf
> file exists, then LyX will try to ask the user whether to overwrite.
> This means creating a dialog as a child of the parent. But the parent,
Am Sonntag, den 17.10.2010, 17:52 -0400 schrieb Richard Heck:
On 10/17/2010 04:19 PM, Pavel Sanda wrote:
Peter Kümmel wrote:
#412: Opening the box of QProcess short before a release?
I don't know if this is a good idea. We had so much problems
when introducing unblocked texing, so I
Am Sonntag, den 17.10.2010, 17:52 -0400 schrieb Richard Heck:
> On 10/17/2010 04:19 PM, Pavel Sanda wrote:
> > Peter Kümmel wrote:
> >
> >> #412: Opening the box of QProcess short before a release?
> >> I don't know if this is a good idea. We had so mu
Am Sonntag, den 17.10.2010, 18:32 +0200 schrieb Pavel Sanda:
kuem...@lyx.org wrote:
Author: kuemmel
Date: Sun Oct 17 12:44:53 2010
New Revision: 35662
URL: http://www.lyx.org/trac/changeset/35662
Log:
Use DispatchResult also in GuiView::dispatchVC to handle messages.
Make it
Am Sonntag, den 17.10.2010, 22:19 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
#412: Opening the box of QProcess short before a release?
I don't know if this is a good idea. We had so much problems
when introducing unblocked texing, so I think we should
postpone it.
i thought
Am Sonntag, den 17.10.2010, 18:32 +0200 schrieb Pavel Sanda:
> kuem...@lyx.org wrote:
> > Author: kuemmel
> > Date: Sun Oct 17 12:44:53 2010
> > New Revision: 35662
> > URL: http://www.lyx.org/trac/changeset/35662
> >
> > Log:
> > Use DispatchResult also in GuiView::dispatchVC to handle messages.
Am Sonntag, den 17.10.2010, 22:19 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > #412: Opening the box of QProcess short before a release?
> > I don't know if this is a good idea. We had so much problems
> > when introducing unblocked texing, so I think we should
&g
Am Samstag, den 11.09.2010, 00:14 +0200 schrieb Pavel Sanda:
Uwe Stöhr wrote:
Am 10.09.2010 20:49, schrieb Pavel Sanda:
do you understand why the code in r35299
string width_str = fromqstr(WidthLE-text());
if (width_str[0] == '-')
width_str.erase(0,1);
must crash sooner or
Am Samstag, den 11.09.2010, 00:14 +0200 schrieb Pavel Sanda:
> Uwe Stöhr wrote:
> > Am 10.09.2010 20:49, schrieb Pavel Sanda:
> >
> >> do you understand why the code in r35299
> >>
> >> string width_str = fromqstr(WidthLE->text());
> >> if (width_str[0] == '-')
> >>width_str.erase(0,1);
> >>
>
Am Dienstag, den 07.09.2010, 12:20 +0200 schrieb Pavel Sanda:
Peter Kümmel wrote:
Fixed it: you must instantiate static members in the cpp file.
thanks, strange it worked in header with gcc.
pavel
Isn't is officially supported by C0++X? Have you used gcc 4.5?
Peter
Am Dienstag, den 07.09.2010, 12:20 +0200 schrieb Pavel Sanda:
> Peter Kümmel wrote:
> > Fixed it: you must instantiate static members in the cpp file.
>
> thanks, strange it worked in header with gcc.
> pavel
Isn't is officially supported by C0++X? Have you used gcc 4.5?
Peter
Am Dienstag, den 07.09.2010, 03:52 +0200 schrieb Uwe Stöhr:
why in cpp and not in header?
Because the compiler doesn't accept this.
the following patch doesn't link for you?
- line_style = line_solid, float line_width = 0.5) = 0;
+ line_style =
Am Dienstag, den 07.09.2010, 07:17 +0200 schrieb Kornel Benko:
Hi, lyx not compilable here, because of missing
#include cmath
...
/usr/src/lyx/lyx-devel/src/insets/InsetLine.cpp: In member function 'virtual
void lyx::InsetLine::metrics(lyx::MetricsInfo, lyx::Dimension) const':
Am Dienstag, den 07.09.2010, 07:32 +0200 schrieb Kornel Benko:
Am Dienstag, 7. September 2010 schrieb Peter Kümmel:
Am Dienstag, den 07.09.2010, 07:17 +0200 schrieb Kornel Benko:
Hi, lyx not compilable here, because of missing
#include cmath
...
/usr/src/lyx/lyx-devel/src/insets
Am Dienstag, den 07.09.2010, 03:52 +0200 schrieb Uwe Stöhr:
> > why in cpp and not in header?
>
> Because the compiler doesn't accept this.
>
> > the following patch doesn't link for you?
> >
> > - line_style = line_solid, float line_width = 0.5) = 0;
> > +
Am Dienstag, den 07.09.2010, 07:17 +0200 schrieb Kornel Benko:
> Hi, lyx not compilable here, because of missing
> #include
> ...
> /usr/src/lyx/lyx-devel/src/insets/InsetLine.cpp: In member function 'virtual
> void lyx::InsetLine::metrics(lyx::MetricsInfo&, lyx::Dimension&) const':
>
Am Dienstag, den 07.09.2010, 07:32 +0200 schrieb Kornel Benko:
> Am Dienstag, 7. September 2010 schrieb Peter Kümmel:
> > Am Dienstag, den 07.09.2010, 07:17 +0200 schrieb Kornel Benko:
> > > Hi, lyx not compilable here, because of missing
> > > #include
> > &
On 02.09.2010 07:54, Stephan Witt wrote:
Am 01.09.2010 um 08:01 schrieb Abdelrazak Younes:
On 09/01/2010 01:38 AM, Uwe Stöhr wrote:
However, this compilation error remains:
10..\..\src\LyX.cpp(288) : error C4101: 'message' : unreferenced local
variable
The attached patch fixes also
On 02.09.2010 09:29, Stephan Witt wrote:
Am 02.09.2010 um 09:03 schrieb Peter Kümmel:
On 02.09.2010 07:54, Stephan Witt wrote:
Am 01.09.2010 um 08:01 schrieb Abdelrazak Younes:
On 09/01/2010 01:38 AM, Uwe Stöhr wrote:
However, this compilation error remains:
10..\..\src\LyX.cpp(288
On 02.09.2010 13:24, Kornel Benko wrote:
Hi Peter,
since the revision 35258(the last working) the package is always installing
under /usr. This messes my
file system.
Because of many white-space differences in CMakeLists.txt, it is not easy to
see the relevant change.
At least, I could
On 02.09.2010 07:54, Stephan Witt wrote:
> Am 01.09.2010 um 08:01 schrieb Abdelrazak Younes:
>
>> On 09/01/2010 01:38 AM, Uwe Stöhr wrote:
>>>
>>> However, this compilation error remains:
>>>
>>> 10>..\..\src\LyX.cpp(288) : error C4101: 'message' : unreferenced local
>>> variable
>>>
>>> The
On 02.09.2010 09:29, Stephan Witt wrote:
> Am 02.09.2010 um 09:03 schrieb Peter Kümmel:
>
>> On 02.09.2010 07:54, Stephan Witt wrote:
>>> Am 01.09.2010 um 08:01 schrieb Abdelrazak Younes:
>>>
>>>> On 09/01/2010 01:38 AM, Uwe Stöhr wrote:
>>&
On 02.09.2010 13:24, Kornel Benko wrote:
> Hi Peter,
> since the revision 35258(the last working) the package is always installing
> under "/usr". This messes my
> file system.
> Because of many white-space differences in CMakeLists.txt, it is not easy to
> see the relevant change.
>
> At
On 01.09.2010 01:38, Uwe Stöhr wrote:
Am 31.08.2010 08:02, schrieb Stephan Witt:
I guess it's my change r35193.
Please try attached patch.
This fixes the setenv compilation errors - I committed it.
However, this compilation error remains:
10..\..\src\LyX.cpp(288) : error C4101:
First -Dmerge=0 and then -Dmerge_rebuild=1? This seems fishy...
In general when you are developping for debug, disable merge build. For
release mode I agree that this is faster.
Abdel.
these options are obsolete now. all options now start with LYX_ see cmake output
or cmake-gui.
I've
On 01.09.2010 01:38, Uwe Stöhr wrote:
> Am 31.08.2010 08:02, schrieb Stephan Witt:
>
>> I guess it's my change r35193.
>>
>> Please try attached patch.
>
> This fixes the setenv compilation errors -> I committed it.
>
> However, this compilation error remains:
>
> 10>..\..\src\LyX.cpp(288) :
> First -Dmerge=0 and then -Dmerge_rebuild=1? This seems fishy...
>
> In general when you are developping for debug, disable merge build. For
> release mode I agree that this is faster.
>
> Abdel.
>
these options are obsolete now. all options now start with LYX_ see cmake output
or
Am Montag, den 19.07.2010, 07:08 +0200 schrieb Kornel Benko:
Where can I find explanations of these new options? At least
LYX_CPACK, LYX_INSTALL, and LYX_NLS are opaque to me.
BH
This is all in flux now. Some very short explanations can be seen with
make edit_cache
from the
Am Montag, den 19.07.2010, 07:08 +0200 schrieb Kornel Benko:
> >
> > Where can I find explanations of these new options? At least
> > LYX_CPACK, LYX_INSTALL, and LYX_NLS are opaque to me.
> >
> > BH
>
> This is all in flux now. Some very short explanations can be seen with
> "make
Am Sonntag, den 18.07.2010, 10:42 +0200 schrieb Abdelrazak Younes:
On 18/07/2010 07:47, Peter Kümmel wrote:
if its question of just one routine we could include it and get rid
of openssh dependence...
Don't know how isolated the openssl code is. And there is another function
Am Sonntag, den 18.07.2010, 10:42 +0200 schrieb Abdelrazak Younes:
> On 18/07/2010 07:47, Peter Kümmel wrote:
> >> if its question of just one routine we could include it and get rid
> >> of openssh dependence...
> >>
> >>
> > Don't know how isola
Am Montag, den 19.07.2010, 13:41 +0200 schrieb Pavel Sanda:
Pavel Sanda wrote:
JMarc is away. i'll try to contact Lars, but its usually hard to get in
touch
fyi Lars answered and he is also away right now...
Seems we never learn anything. Why is it so hard to give several people
root
Am Montag, den 19.07.2010, 13:41 +0200 schrieb Pavel Sanda:
Pavel Sanda wrote:
JMarc is away. i'll try to contact Lars, but its usually hard to get in
touch
fyi Lars answered and he is also away right now...
current possibilities are either wait for somebody with acces to svn server,
I've tested the svn copy way of restoring trunk?
svn copy svn://svn.lyx.org/lyx/lyx-devel/tr...@34983
svn://svn.lyx.org/lyx/lyx-devel/trunk
Peter
Am Dienstag, den 20.07.2010, 00:25 +0200 schrieb Pavel Sanda:
Pavel Sanda wrote:
Peter Kümmel wrote:
Because we wait for svnadmin access anyway (with all the possibilities),
I've tested the svn copy way of restoring trunk? Maybe it is good
enough.
hmm svn blame works. git-svn
Am Montag, den 19.07.2010, 13:41 +0200 schrieb Pavel Sanda:
> Pavel Sanda wrote:
> > JMarc is away. i'll try to contact Lars, but its usually hard to get in
> > touch
>
> fyi Lars answered and he is also away right now...
Seems we never learn anything. Why is it so hard to give several people
Am Montag, den 19.07.2010, 13:41 +0200 schrieb Pavel Sanda:
> Pavel Sanda wrote:
> > JMarc is away. i'll try to contact Lars, but its usually hard to get in
> > touch
>
> fyi Lars answered and he is also away right now...
>
> current possibilities are either wait for somebody with acces to svn
> I've tested the svn copy way of restoring trunk?
svn copy svn://svn.lyx.org/lyx/lyx-devel/tr...@34983
svn://svn.lyx.org/lyx/lyx-devel/trunk
> Peter
>
>
>
Am Dienstag, den 20.07.2010, 00:25 +0200 schrieb Pavel Sanda:
> Pavel Sanda wrote:
> > Peter Kümmel wrote:
> > > Because we wait for svnadmin access anyway (with all the possibilities),
> > > I've tested the svn copy way of restoring trunk? Maybe it is good
> >
Stephan, Qt 4.7 could not compile lines like this:
zoom = !(ev-modifiers() (Qt::ShiftModifier || Qt::AltModifier));
It mixes flag (,|) and bool (,||) operations, so do you mean
zoom = !(ev-modifiers() (Qt::ShiftModifier | Qt::AltModifier));
or
zoom = !(ev-modifiers()
801 - 900 of 4099 matches
Mail list logo
