Am 27.07.2012 21:14, schrieb Trevor Daniels:
Marc
If git push is still not working one thing to check is how you copied your
public key to Savannah. It must contain no embedded newlines, so you need to
display it using a program that doesn't word-wrap.
If that's not the problem try generatin
>> Be careful of newlines accidentally inserted in the public key
>> while entering it in the web interface!
>
> Opening the key file with Firefox is pretty reliable, IME, as FF
> doesn't break lines.
Good to know. My reason for writing was that I've experienced exactly
this problem, and others
>> At least for German, the current syntax is the only good one IMHO,
>> both for accidentals (for the twelve tones of an octave
>
> You mean the 35 tones. After all, we are talking printed output and
> not Midi.
Yes: cis, ces, fisis, feses, etc.
Werner
__
On 12-07-27 10:25 PM, Werner LEMBERG wrote:
It did not accept your key. Sure you uploaded the _public_ key to
Savannah and it got accepted?
Be careful of newlines accidentally inserted in the public key while
entering it in the web interface!
Werner
Opening the key file with Firefox
Reinhold Kainhofer writes:
> The text spanner implemented in scheme (which is also used as a basis
> for David's measure counter engraver) seems to work fine in the regtest,
> but apparently it is not quote-proof.
>
> In particular, if you try call \addQuote on some music that contains
> \schemeT
Werner LEMBERG writes:
>> This is kind of the nub of the issue. I agree that the notation for
>> staff pitches (and octaves) is going to remain stable -- but I'm
>> _not_ convinced that you can guarantee stability for accidentals or
>> durations.
>
> At least for German, the current syntax is th
> It did not accept your key. Sure you uploaded the _public_ key to
> Savannah and it got accepted?
Be careful of newlines accidentally inserted in the public key while
entering it in the web interface!
Werner
___
lilypond-devel mailing list
lil
> This is kind of the nub of the issue. I agree that the notation for
> staff pitches (and octaves) is going to remain stable -- but I'm
> _not_ convinced that you can guarantee stability for accidentals or
> durations.
At least for German, the current syntax is the only good one IMHO,
both for
On Tue, Jul 24, 2012 at 04:45:51AM +0200, Werner LEMBERG wrote:
>
> There are *zero* chances that CJK support
> (probably based on my package) will ever be added to texinfo for the
> original tex or pdftex engine.
I suspected this might be the case.
>
> With XeTeX and luatex, native CJK support
Marc
If git push is still not working one thing to check is how you copied your
public key to Savannah. It must contain no embedded newlines, so you need to
display it using a program that doesn't word-wrap.
If that's not the problem try generating another key. I think many of us had
to do t
> http://codereview.appspot.com/6447043/diff/1/Documentation/de/notation/rhythms.itely#newcode2271
> Documentation/de/notation/rhythms.itely:2271: % by default we beam in
> (6) due to beamExceptions
> are you sure you don't want German comments here?
Only Japanese has japanese comments, all other
- Original Message -
From: "Keith OHara"
To:
Sent: Thursday, July 26, 2012 3:32 AM
Subject: Re: Instrument names
Phil Holmes philholmes.net> writes:
I've done the looking into the code that I can manage. I know that
indents
are worked in output-def.cc:line_dimensions_int. This r
--
Phil Holmes
- Original Message -
From: "Phil Holmes"
To: "Graham Percival" ; "Keith OHara"
Cc:
Sent: Friday, July 27, 2012 2:41 PM
Subject: Re: Instrument names
- Original Message -
From: "Graham Percival"
To: "Keith OHara"
Cc:
Sent: Friday, July 27, 2012 12:48
On Tue, Jul 24, 2012 at 6:09 AM, Graham Percival
wrote:
> This summer hasn't been going as I'd hoped -- heh, who am I
> kidding, this whole year hasn't been going as I'd hoped. Anyway,
> we seem to have radically different concepts of what "input
> stabilization" might mean, or even if it's a goo
- Original Message -
From: "Graham Percival"
To: "Keith OHara"
Cc:
Sent: Friday, July 27, 2012 12:48 PM
Subject: Re: Instrument names
On Thu, Jul 26, 2012 at 02:32:42AM +, Keith OHara wrote:
Phil Holmes philholmes.net> writes:
> So it would be easy to add something to the
> i
On Fri, Jul 20, 2012 at 10:40:30PM +0200, David Kastrup wrote:
>
> Location is Waltrop near Dortmund in Germany, date is August 24th to
> 28th. Here is the web site, and the agenda for starters.
>
> http://news.lilynet.net/?LilyPond-meeting-in-Waltrop>
To get the ball rolling, I'm flying in to D
On 27/07/12 11:11, Graham Percival wrote:
Think of the stable notation as a subset, not the complete set.
Yes, fair enough -- it's very likely changes can be done additively and if not
for the traditional syntax to be maintained as syntactic sugar.
Hmm. I'll have to think about this more.
LGTM
http://codereview.appspot.com/6447043/diff/1/Documentation/de/notation/rhythms.itely
File Documentation/de/notation/rhythms.itely (right):
http://codereview.appspot.com/6447043/diff/1/Documentation/de/notation/rhythms.itely#newcode2271
Documentation/de/notation/rhythms.itely:2271: % by def
On Thu, Jul 26, 2012 at 02:32:42AM +, Keith OHara wrote:
> Phil Holmes philholmes.net> writes:
>
> > So it would be easy to add something to the
> > indent here to take account of intrument names.
>
> The InstrumentName spanners can change when an instrument changes, or
> whenever the user
Marc Hohl writes:
> Am 27.07.2012 12:35, schrieb David Kastrup:
>> David Kastrup writes:
>>
>>> Try calling
>>>
>>> ssh -v -v @git.sv.gnu.org/srv/git/lilypond
>>>
>>> This won't ever get you in (because you are not allowed to execute a
>>> normal shell), but it should fail in more informative wa
Reviewers: dak,
Message:
On 2012/07/27 05:10:50, dak wrote:
> I think this is the wrong way to do things since you can't refer to
old header
> values when defining the new one. Instead, you should start with
the
definition
> you are adding things to, like LAYOUT and similar do. So that
li
Am 27.07.2012 12:35, schrieb David Kastrup:
David Kastrup writes:
Try calling
ssh -v -v @git.sv.gnu.org/srv/git/lilypond
This won't ever get you in (because you are not allowed to execute a
normal shell), but it should fail in more informative ways.
Oops. Of course just
ssh -v -v @git.sv.
David Kastrup writes:
> Try calling
>
> ssh -v -v @git.sv.gnu.org/srv/git/lilypond
>
> This won't ever get you in (because you are not allowed to execute a
> normal shell), but it should fail in more informative ways.
Oops. Of course just
ssh -v -v @git.sv.gnu.org
--
David Kastrup
Am 27.07.2012 12:28, schrieb David Kastrup:
Marc Hohl writes:
After Trevor's mail, I found out that I already *had*
.ssh/config|id_rsa|id_rsa.pub etc.
due to some ssh connections to other servers a friend of mine created for me
(I was sitting next to him, but apparently he can type commands fa
Marc Hohl writes:
> After Trevor's mail, I found out that I already *had*
> .ssh/config|id_rsa|id_rsa.pub etc.
> due to some ssh connections to other servers a friend of mine created for me
> (I was sitting next to him, but apparently he can type commands faster
> than I
> could think, so I didn'
Phil, you wrote Friday, July 27, 2012 11:02 AM
> Compiles fine, AFAICS. See the attached.
Thanks Phil.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 27.07.2012 11:07, schrieb Phil Holmes:
- Original Message - From: "Marc Hohl"
To: "Trevor Daniels"
Cc: "David Kastrup" ;
Sent: Friday, July 27, 2012 8:28 AM
Subject: Re: git push doesn't work
I have saved my public key on savannah, and the instructions say that
it will take some t
On Fri, Jul 27, 2012 at 08:54:47AM +0100, Joseph Rushton Wakeling wrote:
> On 26/07/12 19:19, Graham Percival wrote:
> >I should add some more context. I've just remembered that we have
> >a tutorial (don't ask me how I forgot), and that covers pretty
> >much what I was thinking about "really simp
- Original Message -
From: "Marc Hohl"
To: "Trevor Daniels"
Cc: "David Kastrup" ;
Sent: Friday, July 27, 2012 8:28 AM
Subject: Re: git push doesn't work
I have saved my public key on savannah, and the instructions say that
it will take some time before it gets activated, so I have to
Just realized I sent my original reply straight to Graham and not to the list --
sorry for the double email :-(
On 26/07/12 19:19, Graham Percival wrote:
I should add some more context. I've just remembered that we have
a tutorial (don't ask me how I forgot), and that covers pretty
much what I
Reviewers: ,
Message:
Pushed to staging as
3573a92d92728dc8d6452e5cd3cfba73e49e6990
Closing
Description:
Doc: correct warning re tied chords (2690)
Restore original wording which restricts this
warning to the control points of ties
Please review this at http://codereview.appspot.com/6427058/
Am 27.07.2012 09:16, schrieb Trevor Daniels:
Marc Hohl wrote Friday, July 27, 2012 8:11 AM
I must admit that I am not very familiarwith the whole ssh stuff – is
there anything I can do
to make it work? The git instructions on
http://lilypond.org/doc/v2.15/Documentation/contributor
don't seem
Marc Hohl wrote Friday, July 27, 2012 8:11 AM
> I must admit that I am not very familiarwith the whole ssh stuff – is
> there anything I can do
> to make it work? The git instructions on
>
> http://lilypond.org/doc/v2.15/Documentation/contributor
>
> don't seem to cover the ssh protocol in combi
Am 27.07.2012 09:01, schrieb David Kastrup:
Marc Hohl writes:
[remote "origin"]
url = git://git.sv.gnu.org/lilypond.git/
fetch = +refs/heads/master:refs/remotes/origin/master
fetch = +refs/heads/staging:refs/remotes/origin/staging
So I think I am not using http, right?
It is n
Marc Hohl writes:
> [remote "origin"]
> url = git://git.sv.gnu.org/lilypond.git/
> fetch = +refs/heads/master:refs/remotes/origin/master
> fetch = +refs/heads/staging:refs/remotes/origin/staging
>
> So I think I am not using http, right?
It is not an authenticated protocal either, so
35 matches
Mail list logo
