Le vendredi 07 août 2009 à 21:00 -0700, Patrick McCarty a écrit :
> Personally, I browse git history on the command line quite often when
> working with LilyPond.
So do I, or sometimes with gitk.
There are already many Git features to master for daily use, I'm not
keen on adding to the CG the sha
Carl Sorensen schrieb:
[...]
The generic approach has now been pushed to git
247f0b6d46fd8f3253a99f95a70ce14345daa5f9
There's a generic styledNoteHeads music function that applies a note style
to music whether or not it's in a chord construct.
deadNotes and palmMute have been redefined to use
Patrick McCarty wrote Saturday, August 08, 2009 5:00 AM
On Fri, Aug 07, 2009 at 08:39:16PM -0700, Mark Polesky wrote:
Patrick McCarty wrote:
> I've just tested git's shallow cloning feature. It's pretty
> neat.
> :-)
>
> From what I can see, shallow clones would be okay for *casual*
> co
2009/8/7 Werner LEMBERG :
>
> This is not a clue, this is clearly a bug.
Not just "a" bug: now the famous #826 bug! :-)
http://code.google.com/p/lilypond/issues/detail?id=826
Regards,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
htt
2009/8/5 Kieren MacMillan :
> I want to [automagically] conditionally eliminate lyric extenders when
> (1) the end of the syllable which has the extender is after [i.e., to the
> right of] the melisma's last note; and,
> (2) the distance to the following syllable is less than the minimum
> ex
2009/8/7 Trevor Daniels :
> Sounds reasonable. Do we make it clear anywhere what html
> markup is permitted in snippets destined for the docs (defined
> by tags that are doc-related)? Just so people don't use markup
> that isn't going to be translated to texinfo.
The point would be that all stan
On Fri, Aug 07, 2009 at 11:20:29PM -0700, Patrick McCarty wrote:
> On Fri, Aug 07, 2009 at 11:02:49PM -0600, Andrew Hawryluk wrote:
> > On Fri, Aug 7, 2009 at 8:45 PM, Patrick McCarty wrote:
> > > I think it would be nice to have an entire CG section devoted to
> > > explaining what "rebasing" mean
Le samedi 08 août 2009 à 01:46 -0700, Graham Percival a écrit :
> Despite my above paragraph, I'm not opposed to adding links to
> people's favorite git tutorial. However, I don't expect any
> contributor to read them, and I certainly won't be reading any.
FWIW I usually expect translators to rea
Ok, it's time for our yearly "how should people get started with
git" debate. There's three contenders: git clone, git clone
--depth=1, and the complicated "getting everything on the main
branch" thing that's in the CG currently.
After the init, I see the following sizes of the .git dir:
1) git c
On Sat, Aug 08, 2009 at 07:44:44AM +0200, Werner LEMBERG wrote:
>
> >> becomes @qq{}
> >
> > One small concern: produces double-quotes, whereas our texinfo
> > @q{} produces single quotes. I don't think it's a big deal, but
> > it might confuse somebody down the road.
>
> Read it again, Graha
2009/8/8 Graham Percival :
> Despite my above paragraph, I'm not opposed to adding links to
> people's favorite git tutorial. However, I don't expect any
> contributor to read them, and I certainly won't be reading any.
*I* for one would certainly have read such links when I got started
with git.
2009/8/8 Graham Percival :
> I don't think I missed anything? A doc editor knows that @q
> produces a single quote, so they might expect that would
> also produce a single quote. Conversely, somebody who's been
> editing lots of snippets and starts doing doc work might be
> unpleasantly surprise
Le vendredi 07 août 2009 à 23:27 -0600, Andrew Hawryluk a écrit :
> I can't speak for the future content of
> http://lilypond.org/~graham/Text-input.html, but I will be working on
> the next version of the essay (once the directory structure for images
> in Documentation/ stabilizes), and it should
This is because line-spacing is done earlier than page-spacing - Lily
needs a value for line-width when doing horizontal spacing. Therefore
line-width isn't really discarded - but later in page.scm it is
overwritten, so you can't see it in the page layout.
What I wasn't unable to figure out is
Graham Percival wrote:
> But evidently other people don't share my pathological
> hatred of git...
Umm, hello?
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, Aug 08, 2009 at 01:59:50AM -0700, Graham Percival wrote:
>
> A few people talked about browsing the history, which surprised
> me. Whenever I want to look at history, I use the web git
> interface. But evidently other people don't share my pathological
> hatred of git, so I guess that "a
In notation.pdf, section 1.8.3, `Single entry fonts', the `Charter'
font is used. However, on my GNU/Linux platform, I have both bitmap
and outline Charter fonts installed. Specifying `Charter' only
selects the bitmap variant which is of course rejected by lilypond.
What about changing the font
2009/8/8 Patrick McCarty :
> On Sat, Aug 08, 2009 at 01:59:50AM -0700, Graham Percival wrote:
>>
>> A few people talked about browsing the history, which surprised
>> me. Whenever I want to look at history, I use the web git
>> interface. But evidently other people don't share my pathological
>>
Le samedi 08 août 2009 à 12:37 +0200, Werner LEMBERG a écrit :
> What about changing the font name to `Bitstream Charter'? Can you
> please check, with a call to
>
> fc-match "Bitstream Charter"
>
> whether this works on other platforms too (I use fontconfig 2.7.1),
> selecting an outline vari
> On my Fedora 11 box, I get
>
> $ fc-match "Bitstream Charter"
> bchr.pfa: "Bitstream Charter" "Regular"
Good.
> [lily...@freemousse master]$ fc-match "Charter"
> DejaVuSans.ttf: "DejaVu Sans" "Book"
OK, this means that `Charter' alone even fails on your platform
(because you apparently don't
Hi folks,
I refer to that portion of the documentation:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-pitches#Automatic-accidentals
I think that the fact that automatic accidentals should apply at voice
or staff level should be set separately from the type of automatic
acci
This is a bug: automatic accidentals do not take into account
alternatives after volta repeat:
{
#(set-accidental-style 'modern)
\time 2/4
\repeat volta 2 { cis'4 dis' }
\alternative { { c' d'8 eis'8 } { d'4 c'8 e' } }
}
in the second alternative: we should have:
- natural d, natural c, n
On Sat, Aug 08, 2009 at 07:53:37PM +0200, Werner LEMBERG wrote:
>
> Anyone else who can test this, please?
Here are my results (Arch Linux):
$ fc-match "Bitstream Charter"
c0648bt_.pfb: "Bitstream Charter" "Regular"
$ fc-match "Charter"
charR12.pcf.gz: "Charter" "Regular"
-Patrick
_
> Jay, Mark, anyone: are you interested in submitting a full patch, with
> appropriate documentation, NEWS item etc? If so, we can officially
> submit it for inclusion.
Attached is a patch which adds "SmallStaff" to engraver-init.ly.
Everywhere that \accepts "Staff" was used I just added \accepts
> Here are my results (Arch Linux):
>
> $ fc-match "Bitstream Charter"
> c0648bt_.pfb: "Bitstream Charter" "Regular"
>
> $ fc-match "Charter"
> charR12.pcf.gz: "Charter" "Regular"
I get exactly the same, BTW, with my openSuSE 11.1.
Werner
On 8/7/09 8:45 PM, "Patrick McCarty" wrote:
> On Fri, Aug 07, 2009 at 07:34:01PM -0700, Mark Polesky wrote:
>>
>> Regarding CG 1.2.2:
>> http://kainhofer.com/~lilypond/Documentation/contributor/Update-command.html
>>
>> What does "-r" do in "git pull -r"? I don't see "-r"
>> listed as an opt
Frederic,
On 8/8/09 12:01 PM, "Frédéric Bron" wrote:
> Hi folks,
>
> I refer to that portion of the documentation:
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-pitches#A
> utomatic-accidentals
>
> I think that the fact that automatic accidentals should apply at voice
Doesn't this mix up meaning and appearance? What will you do when
people come asking for LargeStaff, TinyStaff, LittleGreenStaff (for
Martian music), and so forth?
I'm not saying it isn't useful, but maybe it should be named according
to the purpose it serves rather than how it looks.
Quo
Hi Jay (et al.):
Attached is a patch which adds "SmallStaff" to engraver-init.ly.
Everywhere that \accepts "Staff" was used I just added \accepts
"SmallStaff". Let me know if this looks good.
Just a small point: has anyone confirmed that -3 is a "standard"
magstep?
1. When looking at hand-en
Werner LEMBERG schrieb:
Here are my results (Arch Linux):
$ fc-match "Bitstream Charter"
c0648bt_.pfb: "Bitstream Charter" "Regular"
$ fc-match "Charter"
charR12.pcf.gz: "Charter" "Regular"
I get exactly the same, BTW, with my openSuSE 11.1.
Werner
Same here on Ubunt
On Sun, Aug 09, 2009 at 12:42:05AM +0300, Till Paala wrote:
> Werner LEMBERG schrieb:
> >>Here are my results (Arch Linux):
> >>
> >> $ fc-match "Bitstream Charter"
> >> c0648bt_.pfb: "Bitstream Charter" "Regular"
> >>
> >> $ fc-match "Charter"
> >> charR12.pcf.gz: "Charter" "Regular"
> >
> >I
On Sat, Aug 8, 2009 at 12:57 PM, Dan Eble wrote:
> Doesn't this mix up meaning and appearance? What will you do when people
> come asking for LargeStaff, TinyStaff, LittleGreenStaff (for Martian music),
> and so forth?
On Sat, Aug 8, 2009 at 1:45 PM, Alexander Kobel wrote:
> Oh, and by the way...
On Sat, Aug 08, 2009 at 05:18:12PM -0700, Jay Anderson wrote:
> If it is a snippet ideally I'd want to do something like:
>
> \include "small_staff.lyi"
BTW, the latest discussion was to use .ily
> How would one make small_staff.lyi so this worked? This way it would
> be bundled with the other g
Hello,
First of all, thanks go out to Carl and Trevor for reworking the
autobeaming implementation. The new way of working with beam
settings is greatly simplified now.
However, one of the most common complaints we've had is about the
default groupings for 4/4 time. Let me outline the evolution
On Sat, Aug 08, 2009 at 07:21:42PM -0700, Patrick McCarty wrote:
>
> However, one of the most common complaints we've had is about the
> default groupings for 4/4 time. Let me outline the evolution that
> has taken place:
>
> 1) 2.12.3
>- 4 eighth notes that span from beat 1 through beat 2 (
Hi Nick,
From my point of view the main use for smallStaff (or whatever it
gets called) is for ossia staves.
Except IIRC ossia staves and solo/cue staves are usually of different
sizes, yes?
Cheers,
Kieren.
___
lilypond-devel mailing list
lily
36 matches
Mail list logo
