Reinhold Kainhofer kainhofer.com> writes:
>
>
> Am Freitag, 4. Juli 2008 schrieb Carl D. Sorensen:
> > What should I do different to avoid the merge commit every time I push?
>
> I do "git pull" very often, typically before I do a git commit locally. This
> way, your changes are then realativ
Quick check for convert rules, changing "\foo" to "\bar".
The early rules use escape chars:
@rule ((1, 0, 1), '\\accidentals -> \\keysignature,
specialaccidentals -> keyoctaviation')
def conv (str):
str = re.sub ('accidentals', 'keysignature',str)
But the later rules don't use an
Thanks, applied.
Cheers,
- Graham
On Wed, 2 Jul 2008 18:47:39 +0200
Wilbert Berendsen <[EMAIL PROTECTED]> wrote:
> Attached a (hopefully properly formatted) patch. I built and tested
> again, just to be sure, and it works well. I documented the decorator
> function and wrote the code a bit less
On Fri, Jul 4, 2008 at 7:58 PM, Neil Puttock <[EMAIL PROTECTED]> wrote:
> 2008/6/30 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
>
>> you need to issue the bt command, which will print the call interface.
>> Something is doing a
>>
>> NULL->set_property(..)
>>
>> which is obviously wrong
>
> Cheers for t
2008/6/30 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> you need to issue the bt command, which will print the call interface.
> Something is doing a
>
> NULL->set_property(..)
>
> which is obviously wrong
Cheers for the hint; I did a backtrace as suggested, and it turned out
to be Accidental_engraver
2008/7/4 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> Since these metronome marks look very strange at the beginning of a piece, I
> looked at the code and tried copying over staff from RehearsalMark (which
> actually uses the break-align-symbols, defined in scm/define-grobs.scm), but
> all I got was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 4. Juli 2008 schrieb Neil Puttock:
> Hi Libero,
>
> 2008/7/4 Libero Mureddu <[EMAIL PROTECTED]>:
> > I have two questions:
> >
> > Is there a way to have the \tempo or a custom \mark \markup that
> > behaves correctly according to those thr
Hi Victor,
2008/7/2 V!ctor Adán <[EMAIL PROTECTED]>:
> Hello All,
>
> I'm using Staff contexts with the "line-positions" property modified to fit
> my capricious needs.
> In doing so I'm running into 2 problems (please see attached png):
>
> 1. When I set lines to odd numbers, the duration dots of
Le 4 juil. 08 à 18:06, james a écrit :
I don't pretend to be all that great at building software from
source on OSX.
I've successfully built some software, but mostly I use pre-compiled
binaries.
The recent discussions on the lilypond-info have gotten me
interested in making
lilypond more c
I don't pretend to be all that great at building software from source on OSX.
I've successfully built some software, but mostly I use pre-compiled binaries.
The recent discussions on the lilypond-info have gotten me interested in making
lilypond more complete to the point that, since I have some ti
Hi,
On Thu, 3 Jul 2008, Carl D. Sorensen wrote:
> I'm now able to push changes to the repository, but every time I do a
> push, I get two commits -- one for the changes I made, and one for a
> merge.
Funny. For another project I am working on, I wrote an introduction for
exactly this, a coup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick McCarty wrote:
> On Tue, Jul 1, 2008 at 8:38 AM, John Mandereau <[EMAIL PROTECTED]> wrote:
>> I haven't tried 'make install', but 'make web' fails for me when Lily
>> generates the Internals docs (strangely, Lily doesn't segfault in
>> 'make'):
On 2008/07/03 15:07 +0200, Reinhold Kainhofer wrote:
> Ah, that's the place where new features should be mentioned. I looked for a
> Changelog, but didn't find any for version 2.11...
>
> I've now added that new \tempo features and the back-slashed figured bass.
Oops, I have been quite busy with
2008/7/4 Neil Puttock <[EMAIL PROTECTED]>:
> Hi Valentin,
>
> 2008/7/3 Valentin Villenave <[EMAIL PROTECTED]>:
>
>> So far I've been merging his branch without trouble, but now there's a
>> (minor) conflict in the C++ code that I don't know how to handle :-(
>> Could anyone with a clue have a look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 4. Juli 2008 schrieb Carl D. Sorensen:
> What should I do different to avoid the merge commit every time I push?
I do "git pull" very often, typically before I do a git commit locally. This
way, your changes are then realative to HEAD (=t
15 matches
Mail list logo
