> - estimated time: 30 minutes a week. (not counting normal reading
> of mailists)
Can you say how you do it in 30 minutes because each time I want to
update the NR after a small modification, its 15 to 20 minutes of
compilation...
Do you have a secret to make it quicker?
Frédéric
___
I have no idea what I am doing here. In particular not with the
\override, and the set-object-property!. Can somebody explain to me
just what data structures I happen to manipulate, and how a user is
actually _supposed_ to be mangling them?
% The default discant register set has been more or le
I'm taking care of a few recent doc contributions, but I
**REALLY** want somebody else to do this. I want to be working on
gub and the build system stuff. _You_ should want me to be
working on that stuff.
Required tasks for the documentation editor:
- estimated time: 30 minutes a week. (not cou
2009/11/17 Han-Wen Nienhuys :
> My worry is that this might not work correctly for
>
> \tweak #'bound-details #'foo #'bar #22
>
> If that works, please ignore my comment.
No, that can't work, since the level of nesting varies. I don't see
it as a problem though since users are encouraged to over
In message <87d43ekbg4@lola.goethe.zz>, David Kastrup
writes
Regression reports for existing regression tests can be put up more or
less automatically. And a few other things. No idea just how much
something like Gerrit would help.
I thought this rang a bell. This article was in lwn for
On 19 Nov 2009, at 13:28, Hans Aberg wrote:
One can also use pipes and RPC - files can be made looking like
streams and vice versa.
Sorry, it should be IPC - interprocess communications. Though RPC -
remote process call - is a type of IPC. :-)
Hans
__
On 19 Nov 2009, at 11:14, Francisco Vila wrote:
I think that it was changed. If the BOM is only allowed in the
beginning of
the file, it becomes a state-dependent character. For example, if one
includes two files verbatim in another, then the BOMs will no
longer be in
the beginning of the c
Valentin Villenave writes:
> Greetings,
>
> I've just stumbled upon this paper:
> http://lwn.net/Articles/359489/
>
> Looks like the folks at Google have managed to produce (yet) another
> useful toy; basically it's the equivalent of Rietveld (the code-review
> tool we're using right now), but in
2009/11/19 Patrick McCarty :
> I'll try to address this issue eventually, but I can't promise
> anything right away.
Why should'n work just commenting out the line in the code which
issues the error when it finds a BOM?
Some things are a mystery for a non-programmer and they always be. I
used to
2009/11/19 Hans Aberg :
> I think that it was changed. If the BOM is only allowed in the beginning of
> the file, it becomes a state-dependent character. For example, if one
> includes two files verbatim in another, then the BOMs will no longer be in
> the beginning of the combined stream. So there
Greetings,
I've just stumbled upon this paper:
http://lwn.net/Articles/359489/
Looks like the folks at Google have managed to produce (yet) another
useful toy; basically it's the equivalent of Rietveld (the code-review
tool we're using right now), but interfaced with git instead of svn --
current
On 2009.11.18., at 19:43, Alexander Kobel wrote:
> And I suppose this is already all you can hope for. The page-break algorithm
> takes everything in account, AFAIK, so it's impossible to know where the
> first page ends without typesetting the whole score.
> Of course, you don't have to output i
On 19 Nov 2009, at 00:41, Patrick McCarty wrote:
Also, the conditions and the stuff following might possibly be
removed. Something like:
{BOM_UTF8} {}
or
{BOM_UTF8}+ {}
If a language always zips out spaces, one can have rules:
[ \f\r\t\v]+ {}
\n+ { \* Maybe action here counting lin
On Thu, Nov 19, 2009 at 8:47 AM, Patrick McCarty wrote:
> Yes, please, if you don't mind.
There you go: http://code.google.com/p/lilypond/issues/detail?id=905
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.or
14 matches
Mail list logo
