El Tue, 30 Mar 2010 09:54:51 -0400
rgheck escribió:
> Thanks for sending the license statement. I've added you to the credits.
> I've also committed part of this patch
I have decided that future versions of LyXBlogger will run as a python module
instead of as an executable script. Here is a pa
On Sat, Apr 10, 2010 at 01:10:55AM +0200, Vincent van Ravesteijn wrote:
> Jean-Marc Lasgouttes schreef:
> >
> >Le 9 avr. 10 à 21:03, rgh...@lyx.org a écrit :
> >>Log:
> >>Mark new files dirty. Otherwise, you can't save them, and maybe you want
> >>to do that right away.
> >
> >The rationale was th
Jean-Marc Lasgouttes schreef:
Le 9 avr. 10 à 21:03, rgh...@lyx.org a écrit :
Log:
Mark new files dirty. Otherwise, you can't save them, and maybe you want
to do that right away.
The rationale was that one should be ale to close the file immediately
without
a yes/no dialog, AFAIR. But I unde
Le 9 avr. 10 à 21:03, rgh...@lyx.org a écrit :
Log:
Mark new files dirty. Otherwise, you can't save them, and maybe you
want
to do that right away.
The rationale was that one should be ale to close the file immediately
without
a yes/no dialog, AFAIR. But I understand your concern too.
J
On 04/09/2010 03:06 PM, Uwe Stöhr wrote:
rgheck schrieb:
The display fonts for notes, etc, are actually controlled by the
InsetLayouts associated with them. At the moment, however, the
declared color has to be one of the color names known to LyX. A
simple idea would be to allow this:
Colo
rgheck schrieb:
i guess you are asking for r34086.
OK, well, I looked at that, and I think I now understand what is going
on here. Uwe was trying to get the DISPLAY color for e.g. greyed out
notes to match the color that the DOCUMENT wanted those notes to be
printed in.
Yes.
But it is
The attached is a patch I've had sitting around for a while. Currently,
we use FuncRequest::getArg(int) to retrieve arguments from an LFUN
argument string. The downside to this is that every such call completely
reparses the string, and we can do this as many as four times. I thought
about ca
Am 09.04.2010 um 16:24 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>
>>> after svn update leftovers from old builds can remain after any cleaning
>>> and mysterious bugs can happen (it did for me in the past). thats why
>>> i proposed completely new checkout.
>>
>> Since my checkout tree is unto
Stephan Witt wrote:
> Sorry, so it is. Should it?
>
> It stops with these messages:
>
> Makefile:1899: insets/.deps/InsetWrap.Po: No such file or directory
> Makefile:1900: insets/.deps/RenderButton.Po: No such file or directory
> Makefile:1901: insets/.deps/RenderGraphic.Po: No such file or dire
Am 09.04.2010 um 15:47 schrieb Pavel Sanda:
> Stephan Witt wrote:
So, you agree that there is a problem?
>>>
>>> maybe. which tree exactly do you have? make distclean didn't helped?
>>
>> "make distclean" does not work for builds not in tree.
Am 09.04.2010 um 16:02 schrieb Jean-Marc Lasgou
On 04/09/2010 10:00 AM, Enrico Forestieri wrote:
On Thu, Apr 08, 2010 at 10:25:38PM +0200, Pavel Sanda wrote:
for...@lyx.org wrote:
Author: forenr
Date: Thu Apr 8 22:22:20 2010
New Revision: 34095
URL: http://www.lyx.org/trac/changeset/34095
Log:
Use cheaper conversion method.
Mod
Enrico Forestieri wrote:
> I am not the one to be asked about the dispatch issue. Maybe you should have
> paid attention to other commits.
i didn't mean its your fault ;)
pavel
Stephan Witt writes:
> "make distclean" does not work for builds not in tree.
Uh?
JMarc
Pavel Sanda writes:
> to sum it up JMarc was recently changing the location of object files
> which looks connected.
Yes, probably :)
JMarc
On Thu, Apr 08, 2010 at 10:25:38PM +0200, Pavel Sanda wrote:
> for...@lyx.org wrote:
> > Author: forenr
> > Date: Thu Apr 8 22:22:20 2010
> > New Revision: 34095
> > URL: http://www.lyx.org/trac/changeset/34095
> >
> > Log:
> > Use cheaper conversion method.
> >
> > Modified:
> >lyx-devel/t
Stephan Witt wrote:
> >> So, you agree that there is a problem?
> >
> > maybe. which tree exactly do you have? make distclean didn't helped?
>
> "make distclean" does not work for builds not in tree.
>
> I'm using trunk.
of course, but you mentioned its not checkout, so i'm bit perplexed
what y
On 2010-04-09, Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
>> > I prefer to apply all those changes to trunk first, let them be tested
>> you are probably the one to commit it?
> Done:
> http://www.lyx.org/trac/changeset/34099
> http://www.lyx.org/trac/changeset/34100
> Günter, please check
On 04/08/2010 04:51 PM, Pavel Sanda wrote:
Richard Heck wrote:
On 04/08/2010 04:25 PM, Pavel Sanda wrote:
Modified: lyx-devel/trunk/src/Buffer.cpp
==
--- lyx-devel/trunk/src/Buffer.cpp Thu Apr
Am 09.04.2010 um 14:07 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> i mean change of automake files in svn, not during compilation.
>>> pavel
>>
>> So, you agree that there is a problem?
>
> maybe. which tree exactly do you have? make distclean didn't helped?
"make distclean" does not work fo
Stephan Witt wrote:
> > i mean change of automake files in svn, not during compilation.
> > pavel
>
> So, you agree that there is a problem?
maybe. which tree exactly do you have? make distclean didn't helped?
pavel
Am 09.04.2010 um 13:35 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 09.04.2010 um 13:21 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
But I would rate it as a workaround for a dependency problem.
IMHO the cycle "../lyx-devel/configure ; make ; make clean ; make" should
work
Stephan Witt wrote:
> Am 09.04.2010 um 13:21 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> But I would rate it as a workaround for a dependency problem.
> >> IMHO the cycle "../lyx-devel/configure ; make ; make clean ; make" should
> >> work.
> >
> > no it shouldn't in cases automake file
Am 09.04.2010 um 13:26 schrieb Stephan Witt:
> Am 09.04.2010 um 13:21 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
>>> But I would rate it as a workaround for a dependency problem.
>>> IMHO the cycle "../lyx-devel/configure ; make ; make clean ; make" should
>>> work.
>>
>> no it shouldn't i
Am 09.04.2010 um 13:21 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> But I would rate it as a workaround for a dependency problem.
>> IMHO the cycle "../lyx-devel/configure ; make ; make clean ; make" should
>> work.
>
> no it shouldn't in cases automake files change, which just happened.
But
Stephan Witt wrote:
> But I would rate it as a workaround for a dependency problem.
> IMHO the cycle "../lyx-devel/configure ; make ; make clean ; make" should
> work.
no it shouldn't in cases automake files change, which just happened.
pavel
Am 09.04.2010 um 12:38 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Currently I'm lost. Does anybody have an idea? Is it something with the
>> latest automake changes?
>> (The alpha1 tarball is working with my build script!)
>
> make clean is only soft version, there has been changes in makefil
Stephan Witt wrote:
> Currently I'm lost. Does anybody have an idea? Is it something with the
> latest automake changes?
> (The alpha1 tarball is working with my build script!)
make clean is only soft version, there has been changes in makefiles recently
so better to try make distclean; ./autogen
Am 08.04.2010 um 22:20 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> This patch is tested on Mac OS X 10.6.3 and OpenSuSE 11.2.
>>
>> It's unfinished now, as it doesn't include the aspell build script.
>> This one I want to integrate somehow in
>> "development/LyX-Mac-binary-release.sh".
>> But
Pavel Sanda wrote:
> > I prefer to apply all those changes to trunk first, let them be tested
>
> you are probably the one to commit it?
Done:
http://www.lyx.org/trac/changeset/34099
http://www.lyx.org/trac/changeset/34100
Günter, please check if everything is in place now.
Jürgen
29 matches
Mail list logo
