On 08.05.2009 (09:56), Jonathan Kulp wrote:
> Does this mean that, for instance, Debian's repo will have more
> up-to-date versions of things like texi2html and fontforge? I've had
> problems with outdated versions of certain packages on Ubuntu. I've used
> Ubuntu for 18+ months now, and it
On 15.01.2009 (16:43), Jan Nieuwenhuizen wrote:
> Hi,
>
> After 2.12 I decided to do my small round checking of distributions
> again (should we add something like this to release tasks?).
>
> Fedora already has 2.12 (yay!), while Debian and Ubuntu already had 2.12
> wishlist bugs filed (great
I don't know if this is a pie in the sky, but the gregorian notation system
could use a caring hand, especially the spacing stuff.
Eyolf
On 15.01.2009 (13:45), Han-Wen Nienhuys wrote:
> Other pie-in-the sky: completely redo the part-combiner, using the
> music streams infrastructure.
>
> (unfort
On 12.01.2009 (15:18), Reinhold Kainhofer wrote:
> I use Alt+F2, typing "kai" + Return (auto-completes to
> kainhofer.com/~lilypond) in KDE's runner ;-) Beats everything in terms of
> speed.
Not really; with a QuickMark in vimperator/firefox, I type "gol" (or "gnl"
to open it in a new tab). THA
On 28.12.2008 (13:05), Trevor Daniels wrote:
> At present the MensuralVoice context sets the NoteHead style to 'petrucci,
> but does not set the style for rests. I know nothing of ancient music,
> but it seems to me that rests should be set to 'mensural style? Advice
> please, from anyone who
On 11.12.2008 (22:00), Valentin Villenave wrote:
> Both sides are equally important, because it's the feature count that
> makes users *and devs* stick with Lily.
I don't know about the devs -- you're probably right that to them, new
features are more interesting -- but THIS user sticks with LilyP
On 02.12.2008 (17:01), Jonathan Kulp wrote:
> Mats Bengtsson wrote:
>> A couple of minor comments:
>>
>> - At the main page, I would expect to quickly find my way to a page like
>> your Getting Help, if I looked below the title "Dive into ... the
>> LilyPond" and followed the link to "More about
On 12.11.2008 (05:14), Graham Percival wrote:
> On Tue, Nov 11, 2008 at 11:12:11PM -0800, Mark Polesky wrote:
> > Currently, "a few interesting options" are listed
> > with a mention of -dhelp to show the rest. Why not
> > list them all?
>
> Because they change relatively often and are advanced op
On 02.11.2008 (22:15), Till Rettig wrote:
> Trevor Daniels schrieb:
>> Eyolf
>>
>> More comments on Ancient now seem unlikely. T
> Oops, I totally forgot about it. I would like to review this, but I am
> not really fast at the moment. I might just start next week, or would it
> be better to wa
On 25.10.2008 (23:06), Francisco Vila wrote:
> It's me, or aren't there too many adjacent parenthesized phrases in
> the Doc main page?
Now that you mention it: yes. Another thing on that page: is the music
glossary really only for non-English users? I think not.
Eyolf
--
Speaking of Godzil
On 13.10.2008 (09:06), Trevor Daniels wrote:
> Valentin, you wrote Sunday, October 12, 2008 12:38 PM
>
>> 2008/10/3 Trevor Daniels <[EMAIL PROTECTED]>:
>>
>>> This is good. I'm very happy with this.
>>
>> Greetings Trevor,
>>
>> I have pushed a new reordering for 2.1 "Vocal music"; please tell me
On 02.10.2008 (12:01), Kieren MacMillan wrote:
> Hi Reinhold,
>
>> Yes, texi2html creates HTML 4.01 ;-)
>
> That's a pretty darned good reason! =)
... for leaving behind this horrible beast called texinfo :)
In addition to an xml-compliant format.
eyolf
--
"Ann and I will carry out this equi
On 02.10.2008 (00:04), Juergen Reuter wrote:
>
> Very nice, I like the structure and your explanatory add-ons!
Thanks
> Just a few nitpicking comments:
>
> * 2.8.3 (Typesetting mensural music): "There are no rests in Gregorian
> chant notation; instead, it uses Divisiones." I would have expecte
The section on Ancient music is now ready for comments. It has been
completely rewritten and reorganized, so please have a look at it and
comment, correct, or criticize.
Here's a "changelog":
- The main change is that the general organization has been revised into
two main sections: Gregorian c
On 01.10.2008 (02:11), John Mandereau wrote:
> On 2008/09/30 22:46 +, Eyolf Oestrem wrote:
> > Since yesterday, I haven't been able to build the docs --
> > fresh git checkout and a newly compiled lilypond.
>
> Are you sure? (see below)
> Do
>
> make -C python
Arghh, I had forgotten about
On 27.09.2008 (02:16), Juergen Reuter wrote:
>
>
> On Wed, 24 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote:
>
> Originally, I borrowed the term "Episem" from the OpusTeX implementation of
> Gregorian Chant. Just a couple of minutes ago, I did a small search on
> Google and have to agree that t
On 25.09.2008 (04:09), Graham Percival wrote:
>
> Remember that nobody is maintaining the code for ancient music.
> If you can supply a patch, great! If not, then don't hold your
> breath.
One can't remember sth one never knew. Now that I know, I'll start
breathing again.
e
--
Aliquid meliu
It is mentioned as one of the known issues in the ancient section of the
documentation that "The episema line is not displayed in many cases." That
in itself does not make it very useful, but it's doubly bad when it doesn't
even show up in the example that illustrates it.
I also noticed that ther
On 24.09.2008 (21:51), Neil Puttock wrote:
> Hi Eyolf,
>
> 2008/9/24 Eyolf Østrem <[EMAIL PROTECTED]>:
>
> > 1. Is there a good reason why it takes the monstruous
> > \override Staff.Accidental #'glyph-name-alist =
> > #alteration-mensural-glyph-name-al
I'm working on the docs for ancient music, and I've come across a number of
things that relate not primarily to the documentation, but to the program
itself:
1. Is there a good reason why it takes the monstruous
\override Staff.Accidental #'glyph-name-alist =
#alteration-mensural-glyph-name-alist
On 01.01.2008 (02:52), Graham Percival wrote:
> With the end of 2007, I am announcing my intention to leave
> LilyPond.
Many thanks for all your hard work. Much appreciated.
So who's now going to say "can't be done"? :)
Eyolf
--
Linux: the operating system with a CLUE... Command Line User Env
On 28.12.2007 (08:09), Graham Percival wrote:
> I hate to be a wet blanket
No, you don't -- just admit it: you love it! :) ...
> but everything that I've
> learned about documentation project management is screaming "not
> worth the effort".
... and you're probably right.
eyolf
--
Quid me a
On 01.12.2007 (08:28), Joe Neeman wrote:
> On Sat, 1 Dec 2007 03:27:37 Mats Bengtsson wrote:
> > It seems that this property has been removed in the implementation and
> > that the Volta_engraver by default has been moved to the Score context
> > (I seem to recall that I proposed a similar solution
voltaOnThisStaff is documented as follows in the IR:
Normally, volta brackets are put only on the topmost staff. This variable
overrides this behavior, when set to #t or #f.
However, taking a snippet from LSR and trying out various combinations,
always gives the same result: the volta bracket is
On 21.11.2007 (15:16), Mats Bengtsson wrote:
> In the IR, it's very clear what properties are context properties and what
> are
> object properties. This is something I will try to explain in the overview of
> property settings that I have promised in
> http://lists.gnu.org/archive/html/lilyp
On 21.11.2007 (11:34), Han-Wen Nienhuys wrote:
> 2007/11/21, Rune Zedeler <[EMAIL PROTECTED]>:
> > The following gives a syntax error:
> >
> > \set Staff.Tie #'transparent = ##t
> >
> > but if I replace with
> >
> > \revert Staff.Tie #'transparent \override Staff.Tie #'transparent = ##t
> >
> > the
On 14.11.2007 (13:56), Mats Bengtsson wrote:
> Fixed in GIT!
That was quick! Great.
Eyolf
--
"...[Arthur] leapt to his feet like an author hearing the
phone ring..."
- Who says that the character of Arthur isn't autobiographical?
___
lilypond-d
In the following example --
\version "2.11.34"
\relative c' {
\time 3/2
c32 c c c c c c c
c c c c c c c c
c c c c c c c c
c c c c c c c c
c c c c c c c c
c c c c c c c c
}
... all the notes are grouped by four -- except for the 7th and 8th groups,
where eight notes are joined in the same beams.
The improvisationOn/Off command produces squashed noteheads -- fine -- but
if there are accidentals in the input code -- as in the example in the docs
(1.1.4 Note heads in the GDP version of the docs) -- these are retained,
which looks strange and defies the purpose of the squashing: to remove the
On 01.11.2007 (10:11), Mats Bengtsson wrote:
> Cross-staff arpeggios already work in StaffGroups and GrandStaffs, without
> adding any extra engraver:
Ah, great! Thanks. Why didn't I think of that...?
e
--
"To make a bad day worse, spend it wishing for the impossible." -Calvin
In the section about arpeggios in the documentation, there is an
example of cross-staff arpeggios in a PianoStaff context:
@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
\new PianoStaff <<
\set PianoStaff.connectArpeggios = ##t
\new Staff { \arpeggio }
\new St
On 31.10.2007 (00:14), Graham Percival wrote:
> Mats Bengtsson wrote:
> >Actually, the answer is different for different articulations. Some, like
> > \fermata
> >are always placed above the stave, whereas others like \accent are placed
> >opposite to the stem. All this is specified in the file sc
I'm working on the articulations for the GDP, and I've ran into some
things that I would need assistance on:
1. Automatic placement. I think there should be a brief note about
what the rules are for how they are placed by default. Opposite of the
stem? How about polyphony? According to the voice
33 matches
Mail list logo
