On 04/11/2010 10:30 PM, BH wrote:
Stephen Witt has been doing some great things for LyX/Mac. Given that
I have not had time or expertise to really advance LyX/Mac, and given
his abilities and enthusiasm, I have asked him if he would like to
take over as LyX/Mac maintainer. He has agreed.
For
- : action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
+ : argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
y_(0),
What's the rationale about initializing a docstring with 0 ? (Does it
even compile ?)
Vincent
Vincent van Ravesteijn - TNW wrote:
-: action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
+: argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
y_(0),
What's the rationale about initializing a docstring with 0 ? (Does it
even compile ?)
hrmpf, i only wanted to add something
On 04/12/2010 11:31 AM, Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
- : action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
+ : argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
y_(0),
What's the rationale about initializing a docstring
Richard Heck wrote:
I've tried restoring the initialization order. Otherwise, yes, it is VERY
strange. Note that this comes from LyX.cpp:531:
lyx::dispatch(FuncRequest(LFUN_WINDOW_NEW, geometryArg));
So the constructor was actually this one:
FuncRequest::FuncRequest(FuncCode act,
ehh, i thought from the one without argument, no?
FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
Please read further:
#11 0x081a00c8 in static_initialization_and_destruction_0 ()
at FuncRequest?.cpp:28
This is your 0
Vincent van Ravesteijn - TNW wrote:
ehh, i thought from the one without argument, no?
FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
Please read further:
#11 0x081a00c8 in static_initialization_and_destruction_0 ()
at
On 04/12/2010 02:25 PM, Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
ehh, i thought from the one without argument, no?
FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
Please read further:
#11 0x081a00c8 in
Richard Heck wrote:
We should perhaps add this to our bug reporting comments: If you are seeing
the bug in checkouts from svn, then you might want to try a fresh checkout.
already done in FAQ :)
p
Le 12 avr. 10 à 21:16, Pavel Sanda a écrit :
Richard Heck wrote:
We should perhaps add this to our bug reporting comments: If you
are seeing
the bug in checkouts from svn, then you might want to try a fresh
checkout.
already done in FAQ :)
But this should not happen...
JMarc
On 12/04/2010 6:05 AM, Helge Hafting wrote:
Of course, embedding lilypond code in LyX would be even less work. But I
don't know a quick way to program that. Anything not supported directly
by latex, is kept in separate files. This is the way it is for graphics,
as well as music.
The current
Am 12.04.2010 um 04:30 schrieb BH:
Stephen Witt has been doing some great things for LyX/Mac. Given that
I have not had time or expertise to really advance LyX/Mac, and given
his abilities and enthusiasm, I have asked him if he would like to
take over as LyX/Mac maintainer. He has agreed.
I'm looking for a tighter coupling of the build script and the compiled code.
There has to be a strict coherence between the strings the build script uses
and the strings for runtime lookup by LyX binary. So I want to pass a define
here. To convert it to a string I couldn't find a useable macro in
On 04/11/2010 10:30 PM, BH wrote:
Stephen Witt has been doing some great things for LyX/Mac. Given that
I have not had time or expertise to really advance LyX/Mac, and given
his abilities and enthusiasm, I have asked him if he would like to
take over as LyX/Mac maintainer. He has agreed.
For
>- : action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
>+ : argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
y_(0),
>
What's the rationale about initializing a docstring with 0 ? (Does it
even compile ?)
Vincent
Vincent van Ravesteijn - TNW wrote:
> >-: action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
> >+: argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
> y_(0),
> >
>
> What's the rationale about initializing a docstring with 0 ? (Does it
> even compile ?)
hrmpf, i only wanted to add
On 04/12/2010 11:31 AM, Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
- : action_(LFUN_NOACTION), origin_(o), x_(0), y_(0),
+ : argument_(0), action_(LFUN_NOACTION), origin_(o), x_(0),
y_(0),
What's the rationale about initializing a docstring
Richard Heck wrote:
> I've tried restoring the initialization order. Otherwise, yes, it is VERY
> strange. Note that this comes from LyX.cpp:531:
> lyx::dispatch(FuncRequest(LFUN_WINDOW_NEW, geometryArg));
> So the constructor was actually this one:
> FuncRequest::FuncRequest(FuncCode
>ehh, i thought from the one without argument, no?
>
>FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
>o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
Please read further:
#11 0x081a00c8 in static_initialization_and_destruction_0 ()
at FuncRequest?.cpp:28
This is your 0
Vincent van Ravesteijn - TNW wrote:
> >ehh, i thought from the one without argument, no?
> >
> >FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
> >o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
>
> Please read further:
>
> #11 0x081a00c8 in
On 04/12/2010 02:25 PM, Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
ehh, i thought from the one without argument, no?
FuncRequest? (this=0x8c0111c, act=lyx::LFUN_UNKNOWN_ACTION,
o=lyx::FuncRequest::INTERNAL) at FuncRequest?.cpp:39
Please read further:
#11 0x081a00c8 in
Richard Heck wrote:
> We should perhaps add this to our bug reporting comments: If you are seeing
> the bug in checkouts from svn, then you might want to try a fresh checkout.
already done in FAQ :)
p
Le 12 avr. 10 à 21:16, Pavel Sanda a écrit :
Richard Heck wrote:
We should perhaps add this to our bug reporting comments: If you
are seeing
the bug in checkouts from svn, then you might want to try a fresh
checkout.
already done in FAQ :)
But this should not happen...
JMarc
On 12/04/2010 6:05 AM, Helge Hafting wrote:
Of course, embedding lilypond code in LyX would be even less work. But I
don't know a quick way to program that. Anything not supported directly
by latex, is kept in separate files. This is the way it is for graphics,
as well as music.
The current
Am 12.04.2010 um 04:30 schrieb BH:
> Stephen Witt has been doing some great things for LyX/Mac. Given that
> I have not had time or expertise to really advance LyX/Mac, and given
> his abilities and enthusiasm, I have asked him if he would like to
> take over as LyX/Mac maintainer. He has agreed.
I'm looking for a tighter coupling of the build script and the compiled code.
There has to be a strict coherence between the strings the build script uses
and the strings for runtime lookup by LyX binary. So I want to pass a define
here. To convert it to a string I couldn't find a useable macro in
26 matches
Mail list logo
