Han-Wen,
do you remember why the dynamic signs `m' and `p' have a different
height? Ditto for essentially all other dynamic signs. At small
resolutions this looks really bad due to the PostScript hints applied
by FontForge...
Werner
___
lilyp
John Mandereau wrote:
> There is really no risk of collision with a previous
> existing repository: if there was one, 'git init' would
> barf.
Except that once I designate a remote branch `origin', I
need to name the other branch something else? My
understanding is hazy, but from the build direc
On 2009/12/21 00:33:59, Ian Hulin wrote:
New patch-set uploaded with regressions in engraver-init.ly fixed.
Now OK to push?
LGTM, applied.
Thanks,
Neil
http://codereview.appspot.com/180095
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2009/12/21 Translation Project Robot :
> A new POT file for textual domain 'lilypond' has been made available
> to the language teams for translation. It is archived as:
>
> http://translationproject.org/POT-files/lilypond-2.13.7.pot
We the four main languages are at 100%. Many strings are
non
On Mon, Dec 21, 2009 at 02:10:15PM -0800, Mark Polesky wrote:
> Marc Hohl wrote:
> > I found something useful here:
> > http://code.google.com/p/pymc/issues/detail?id=230
> >
> > The program is simple but seems to work:
>
> Why not use a sed one-liner?
Because not all OSes have sed. And even th
Marc Hohl wrote:
> I found something useful here:
> http://code.google.com/p/pymc/issues/detail?id=230
>
> The program is simple but seems to work:
Why not use a sed one-liner?
sed -i 's/[ \t]*$//' filename
*
$ echo -e "Trailing spaces: \nTrailing tabs:\t\t" > ws-test
$ cat -A ws-test
Tr
Hi Mark,
Le dimanche 20 décembre 2009 à 22:06 -0800, Mark Polesky a écrit :
> $ mkdir lilypond; cd lilypond
> $ git init
> $ mkdir lilypond-translation; cd lilypond-translation
> $ git init
Although I already read this section in the CG, I missed this detail
you're pointing out. If you're still
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'lilypond' has been made available
to the language teams for translation. It is archived as:
http://translationproject.org/POT-files
On 12/20/09 1:57 PM, "James Lowe" wrote:
>> One recommendation: every time you modify a source file, run
>> a macro or something to trim the trailing whitespaces
> As someone who wouldn't know what to run and who does get this occasionally in
> doc patches I push, can someone give me some advi
On 12/21/09 1:52 PM, "Marc Hohl" wrote:
> [...]
>> I like it much better. But I think that the bulb on the bottom of the clef
>> needs to shift slightly to the right with this change.
>>
> Like the attached one?
> You may use the pdf file for a printout.
This may be a bit too much differen
On Sun, Dec 13, 2009 at 11:53 AM, Graham Percival
wrote:
> I wanted to wait until GOP started, but it seems there's a lot of
> interest in this now. Here's my proposed new classifications for
> issues.
Apparently there wasn't all _that_ much interest.
I've updated the instructions in CG 6.2. T
Thanks Joe, I can confirm that a doc build from scratch (with that patch) works.
Colin: sorry for the rocky introduction; this normally doesn't happen.
Update git (git pull -r, or the gui, or whatever) and try again. :)
Cheers,
- Graham
On Mon, Dec 21, 2009 at 5:08 PM, Joe Neeman wrote:
> On
Could somebody add this to the CG? The beginning of the "producing a
patch" would be good, I think, but I'm not certain where that fits
into Mark's restructuring.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu
Reinhold, you wrote Monday, December 21, 2009 4:37 PM
Please note the ^ in the command, which means the commit
**before** HEAD, so
this command takes all commits since HEAD-1 (i.e. it takes only
the last
patch) and corrects all trailing whitespace in it.
You're right - I'd missed that. Th
Carl Sorensen wrote Monday, December 21, 2009 4:41 PM
On 12/21/09 9:11 AM, "Trevor Daniels"
wrote:
Carl Sorensen wrote"
so you can do
git rebase --whitespace=fix HEAD^
Hhm. I don't think this works.
The whitespace option is simply passed to apply
for actioning, but in this case appl
On Mon, 2009-12-21 at 16:34 +, Graham Percival wrote:
> On Mon, Dec 21, 2009 at 4:26 PM, Graham Percival
> wrote:
> > On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels
> > wrote:
> >>
> > I'm trying a full rebuild now; I'm getting some errors, but I'm not
> > certain if they're just the expect
On Sun, Dec 20, 2009 at 9:33 PM, Marc Hohl wrote:
> Graham Percival schrieb:
>>
>> There's some git command that removes whitespaces at the end of
>> lines. There's also a tracker issue to find a command (ideally
>> with python, maybe?) that removes those whitespaces. Either it's
>> a hard issue
Graham Percival writes:
> On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels wrote:
>>
>> Colin Campbell wrote Monday, December 21, 2009 3:33 PM
>>>
>>> After building LP 2.13.10 from git, I wanted an HTML copy of the docs, so
>>> I cd to /Documentation and did make doc. The result was a segfault:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 21. Dezember 2009 17:11:54 schrieb Trevor Daniels:
> Carl Sorensen wrote"
> > so you can do
> >
> > git rebase --whitespace=fix HEAD^
>
> Hhm. I don't think this works.
>
> The whitespace option is simply passed to apply
> for actioning,
On Mon, Dec 21, 2009 at 4:26 PM, Graham Percival
wrote:
> On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels wrote:
>>
> I'm trying a full rebuild now; I'm getting some errors, but I'm not
> certain if they're just the expected random errors from using
> CPU_COUNT, or whether they're more serious.
On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels wrote:
>
> Colin Campbell wrote Monday, December 21, 2009 3:33 PM
>>
>> After building LP 2.13.10 from git, I wanted an HTML copy of the docs, so
>> I cd to /Documentation and did make doc. The result was a segfault:
>
> Try make doc in the directory
Colin Campbell wrote Monday, December 21, 2009 3:33 PM
After building LP 2.13.10 from git, I wanted an HTML copy of the
docs, so I cd to /Documentation and did make doc. The result was a
segfault:
Try make doc in the directory above /Documentation,
whatever you chose to call it.
Trevor
On Mon, Dec 21, 2009 at 3:33 PM, Colin Campbell wrote:
>> "/home/colin/lilypond/out/lybook-db/snippet-names-5301286380616983105.ly"
>
> The error is repeatable, at least to the extent that it has died the same
> way twice. I looked at each of the files in snippet-names-530...105.ly but
> nothing c
Carl Sorensen wrote"
On 12/21/09 8:08 AM, "Trevor Daniels"
wrote:
As far as I know it can't. The rebase command rebases
one git branch on another, so you have to be using branches
to take advantage of it.
Rebase combines all the changes between two different git commits
into a
single
On 12/21/09 8:51 AM, "Trevor Daniels" wrote:
>
>
> Graham Percival wrote Monday, December 21, 2009 3:18 PM
>
>
>> On Mon, Dec 21, 2009 at 3:08 PM, Trevor Daniels
>> wrote:
>>>
>>> Graham Percival wrote Monday, December 21, 2009 2:46 PM
>>>
>>> git rebase --whitespace=fix master mymo
Graham Percival wrote Monday, December 21, 2009 3:18 PM
On Mon, Dec 21, 2009 at 3:08 PM, Trevor Daniels
wrote:
Graham Percival wrote Monday, December 21, 2009 2:46 PM
git rebase --whitespace=fix master mymods
If git
can be configured to automatically fix whitespaces, then I'll
copy&pas
Good morning, all
After building LP 2.13.10 from git, I wanted an HTML copy of the docs,
so I cd to /Documentation and did make doc. The result was a segfault: >
[feta-alphabet20_7.029296875]Segmentation fault
command failed: /home/colin/lilypond/out/bin/lilypond -dbackend=eps --formats=ps,png,
Mats, you wrote Monday, December 21, 2009 12:40 PM
I tried it here and it works well.
Try the following:
- Start emacs with the scm file:
emacs myfile.scm &
- If Emacs just shows a welcoming screen, press CTRL-g.
- On the status line towards the bottom of the window, it should
say
myfi
On 12/21/09 8:08 AM, "Trevor Daniels" wrote:
>
>
> Graham Percival wrote Monday, December 21, 2009 2:46 PM
>
>
>> On Mon, Dec 21, 2009 at 12:56:51AM -, Trevor Daniels wrote:
>>>
>>> Graham Percival wrote Sunday, December 20, 2009 11:13 PM
>>>
> git rebase --whitespace=fix master
On Mon, Dec 21, 2009 at 3:08 PM, Trevor Daniels wrote:
>
> Graham Percival wrote Monday, December 21, 2009 2:46 PM
>
> git rebase --whitespace=fix master mymods
>> If git
>> can be configured to automatically fix whitespaces, then I'll
>> copy&paste the command and then stop pushing commi
Graham Percival wrote Monday, December 21, 2009 2:46 PM
On Mon, Dec 21, 2009 at 12:56:51AM -, Trevor Daniels wrote:
Graham Percival wrote Sunday, December 20, 2009 11:13 PM
git rebase --whitespace=fix master mymods
Can that be written as a universal preference? and added to CG
1.1?
On Mon, Dec 21, 2009 at 06:52:18AM -0700, Carl Sorensen wrote:
>
> On 12/20/09 11:06 PM, "Mark Polesky" wrote:
>
> > In reality, contributors working with both branches should
> > have them in the same directory, right? There's no need
> > for having two repos, one for each branch, or am I miss
On Mon, Dec 21, 2009 at 12:56:51AM -, Trevor Daniels wrote:
>
> Graham Percival wrote Sunday, December 20, 2009 11:13 PM
>
>>> git rebase --whitespace=fix master mymods
>>
>> Can that be written as a universal preference? and added to CG
>> 1.1? (I think it's that section; it might have moved
On Sun, Dec 20, 2009 at 10:04:50PM -0700, Carl Sorensen wrote:
> But when I click on the link for the 2.13.9 manuals, I get this link
>
> only contains the words "The node you are looking for is at Development",
> and the Development link points to the same page.
Intresting; I only saw this when
Carl Sorensen wrote Monday, December 21, 2009 1:44 PM
You can find out more about ssh on windows by searching for
"windows ssh
client".
PuTTY is probably the most common ssh client for Windows, in my
experience.
I never managed to make PuTTY work with savannah and git.
None of the key pair
On Mon, Dec 21, 2009 at 6:33 AM, Andreas Wenger wrote:
> I didn't want to bother you with technical details, but since asked, here
> are the reasons why we use SVG symbols (in ascending importance):
>
> (1) I think, fonts are designed to write texts. Think about features like
> kerning, which I d
On 12/21/09 3:08 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>> Jan Nieuwenhuizen xs4all.nl> writes:
>>
>>
>>> Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
>>> Tatham:
>>>
>>>
It's interesting that you should mention that: that actually reminds
me o
On Mon, Dec 21, 2009 at 8:08 AM, Marc Hohl wrote:
It's interesting that you should mention that: that actually reminds
me of one of my specific issues with Feta, namely that the curved
centre line of its treble clef _does_ make it look to me as if it's
leaning over backwards. G
On 12/21/09 1:55 AM, "Trevor Daniels" wrote:
>
>
> Carl Sorensen wrote Monday, December 21, 2009 12:58 AM
>
>> I've never had anybody turn down a patch by me because I had the
>> wrong
>> number of indents, ore even call me on it, because the rules are
>> not well
>> enough understood by us
On 12/20/09 11:06 PM, "Mark Polesky" wrote:
> CG 1.1.3 "Main source code" suggests putting the `master'
> branch in a dir called `lilypond/':
>
> $ mkdir lilypond; cd lilypond
> $ git init
>
>
> CG 1.1.4 "Documentation translations source code" suggests
> putting the `lilypond-translations'
On 12/20/09 8:37 PM, "Mark Polesky" wrote:
> In CG 1.1.6 "Other locations for git", this is listed as a
> location for the LP repo:
>
> ssh://git.sv.gnu.org/srv/git/lilypond.git
>
> Can only project members pull from it? Or can anyone,
> provided SSH is set up properly (whatever that means)
Tried it, compiles fine for me on Linux (the Lilybuntu virtual machine).
Thanks!
thSoft
On 2009.12.21., at 12:42, Nicolas Sceaux wrote:
> I've commited a fix. I hope it does not break things on other platforms...
> If it does, please revert patch 6b78efc2ea0cb064850c264ff225d9930353a178.
>
> Huh
I tried it here and it works well.
Try the following:
- Start emacs with the scm file:
emacs myfile.scm &
- If Emacs just shows a welcoming screen, press CTRL-g.
- On the status line towards the bottom of the window, it should say
myfile.scm ... (Scheme)
If it doesn't say "(Sch
Le 15 déc. 2009 à 07:20, Patrick McCarty a écrit :
> On 2009-12-14, Harmath Dénes wrote:
>> On 2009.12.13., at 20:31, Patrick McCarty wrote:
>>
>>> 2009/12/12 Harmath Dénes :
And yes, this solved the problem! You're right, flex is among the
dependencies.
Concluding it, I think two
I tried the Emacs indenting script from
CG 8.5.5 but it doesn't seem to do anything
useful. Maybe I'm missing something, so I
need some help from an Emacs literatus so
I can get it working and fix the CG instructions.
As I don't know what the script is supposed
to do maybe it's working correctly
Marc Hohl wrote Monday, December 21, 2009 10:08 AM
Carl Sorensen schrieb:
Jan Nieuwenhuizen xs4all.nl> writes:
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef
Simon
Tatham:
It's interesting that you should mention that: that actually
reminds
me of one of my specific issue
Carl Sorensen schrieb:
Jan Nieuwenhuizen xs4all.nl> writes:
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
It's interesting that you should mention that: that actually reminds
me of one of my specific issues with Feta, namely that the curved
centre line of
Carl Sorensen wrote Monday, December 21, 2009 12:58 AM
I've never had anybody turn down a patch by me because I had the
wrong
number of indents, ore even call me on it, because the rules are
not well
enough understood by us mere mortals (it's all in the indenter
code).
I think if you always d
Mark Polesky wrote Monday, December 21, 2009 1:42 AM
Trevor Daniels wrote:
Actually, I don't think rebase is mentioned in the CG. I
can't see it on a quick trawl. It should be, as a branch
should be rebased before a patch is generated from it if
master has been updated since the branch was
Mark Polesky wrote Monday, December 21, 2009 3:37 AM
In CG 1.1.6 "Other locations for git", this is listed as a
location for the LP repo:
ssh://git.sv.gnu.org/srv/git/lilypond.git
Can only project members pull from it? Or can anyone,
provided SSH is set up properly (whatever that means)?
50 matches
Mail list logo
