Hi again,
I mentioned that in the tremolo example the
\repeat "tremolo" 4 c16
doesn't work.
I made a simple file with one measure.
I added the tremolo example from the doc page:
% Generated automatically by: lilypond-book.py
% options are filename=/home/hanwen/usr/src/savannah/lily/li
Hello,
In the following source I'm having a problem with lyrics lining up with
the right notes. After "fear", which starts on an eighth note, I want
to display an extender, but it isn't getting shown, which causes the
rest of the lyrics to be off by one note. Here is the source. I'm
using v
How can I make the quarter note for the tempo indication smaller? I'm
not sure what object property to modify. Also, I want to provide a
tempo range, such as \tempo 4 = 84-92, but it croaks when I try to add
stuff after the first number. Is there a way to do this?
Thanks,
Carl Youngblood
sm
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> The "manual with comments" format might still help you,
>> though. Whenever you take a documentation-day before a
>> release, you could review the new comments, and
>> incorporate good suggestions into the docs. It lowers
>> the barrier for users,
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
What about the change in slash size from 2.1.2 to 2.1.6 which I see from
the regression tests works for percussion parts but used to be the
standard distance between two lines for rhythm slashes. I guess this
can be set to what we need also?
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys wrote:
>
> >[EMAIL PROTECTED] writes:
> >
> >
> >>What about the change in slash size from 2.1.2 to 2.1.6 which I see from
> >>the regression tests works for percussion parts but used to be the
> >>standard distance between two lines for rhythm slas
[EMAIL PROTECTED] writes:
>
> I mentioned that in the tremolo example the
>
> \repeat "tremolo" 4 c16
>
> doesn't work.
>
> When I run lilypond on it I get:
>
> /home/aamehl/asimple.ly:18:23: warning: Chord tremolo with 1 elements. Must have two
> elements.:
> { \repeat "tremolo" 4
Our US Licensed Doctors will
Prescribes Your Medication For Free
Medications Shipped Overnight To Your Do.
show
Me more
blaspheme ashamed needham amphibious dixieland incongruity gerhard descriptive naturopath inhibition calla dairylea classify jenny drastic dc land oscillatory snatch
On Thu, 8 Jan 2004, Mats Bengtsson wrote:
> The step from basic to advanced user is clearly a major threshold but
> does not involve learning all about Scheme but rather to learn the
> mechanisms to set properties and the syntax used. The sections on
> "Setting Variables" and "Fine Tuning layout"
how much space/bandwidth would be involved?
I wouldn't know how to set it up by myself but I do have some space.
Aaron
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Hi,
Thank you for that information. Jan also pointed out that it was under
"Articulation" in the 1.6 Docs. I'm not sure why I didn't look under there
(I had never checked the 1.8) but it works just as needed. My only excuse
is the sinus medication I'm on :)
Thank you both!
Bryan
On Thu,
[John Williams]
> Han-Wen Nienhuys wrote:
> > Why not edit the texinfo source directly, and send a patch?
> You are asking the users to learn texinfo, diff and patch before they
> can help you. And as someone else pointed out, if they install a prebuilt
> version, they don't even have the texinfo
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys wrote:
> > Why not edit the texinfo source directly, and send a patch?
>
> You are asking the users to learn texinfo, diff and patch before they
> can help you. And as someone else pointed out, if they install a prebuilt
> version, they don't even have
Han-Wen Nienhuys wrote:
> Why not edit the texinfo source directly, and send a patch?
You are asking the users to learn texinfo, diff and patch before they
can help you. And as someone else pointed out, if they install a prebuilt
version, they don't even have the texinfo source.
(Personally, gnu
Hi I saw the format for the new tremolo section and it is indeed clearer.
Since I didn't understand a word about how to update the documents.
I need a link that will show me how I get access etc.
As I see it Seealso
becomes
In this manual
intenals
examples
I looked at few examples and see how it
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Nick Busigin wrote:
Is there a way of placing rhythm marks (slashes) on a staff instead of
notes?
melie Zapf provided this but:
1. The part that sets the stem length to zero doesn't work.
Setting it to transparent is more effective, I
I would like to report that v2.1.6 corrected a problem with printing
the bass clef on certain printers. With v.2.0.1, an unidentifiable
artifact was included at the top of the clef grob when printed, e.g.,
on a Brother laser printer. It did not appear when printed with a HP
laser. I assume it h
[EMAIL PROTECTED] writes:
> First of all I agree that add work for the maintainer of lilypond is in
> the long run a very bad idea.
> Making Hans fiddle with the docs means less improvement to the program
> that said.
>
> There are many levels to improving the docs. Some issues are infact
> rea
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
First of all I agree that add work for the maintainer of lilypond is in
the long run a very bad idea.
Making Hans fiddle with the docs means less improvement to the program
that said.
There are many levels to improving the docs. Some issues a
[EMAIL PROTECTED] writes:
> >
> >this is intentional, but I can understand that it is confusing.
> >
> >I've updated the tremolo entry of the manual with links. I've also
> >changed the SEEALSO section like this
> >
> > In this manual: *Tremolo subdivisions::, *Note Repeats::.
> >
> > Inter
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
this is intentional, but I can understand that it is confusing.
I've updated the tremolo entry of the manual with links. I've also
changed the SEEALSO section like this
In this manual: *Tremolo subdivisions::, *Note Repeats::.
Interna
Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys writes:
Come to think of it, this form of \with is superfluous. It is possible
to write it with something like
\apply #(nest-props '((Stem thickness 4) (Slur transparent #t)))
{ .. }
Very nice.
Well, yes except for the syntax. Definitely something t
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Ferenc Wagner writes:
>
>> Bugreports are not the best way to improve documentation,
>
> For the developers, they are.
I humbly find it unfair that you didn't quote the clause:
>> unless the reporter literally includes the piece of text
>> she want
[EMAIL PROTECTED] writes:
> > and then we use
> >
> > \translator Staff = up {
> > \consists ".."
> > Stem \override #'thickness = #4
> > Slur \override #'transparent = ##t
> > } ..music..
>
> Then why not use \apply #up-staff-properties { .. } here?
because the properties ne
Han-Wen Nienhuys writes:
> Come to think of it, this form of \with is superfluous. It is possible
> to write it with something like
>
> \apply #(nest-props '((Stem thickness 4) (Slur transparent #t)))
>{ .. }
Very nice.
> and then we use
>
> \translator Staff = up {
> \consists ".."
[EMAIL PROTECTED] writes:
> > I'm OK with everything, as long as it improves the documentation *and*
> > decreases the time that I have to spend on it. In practice, this means
> > that I don't want to setup the site, monitor it, get the patches, or
> > edit the text. This means that in the end, so
[EMAIL PROTECTED] writes:
> I'm not convinced! Since the curly braces are used for so many
> different purposes, I think it's much harder to detect the '}'
> that ends a certain set of property settings than to find the
> \revert command. If you think the setting and reverting involves
> too much t
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> I also sketched a slightly more elaborate instruction in
> an email some months ago, thinking that it might a good
> addition to the manual but haven't yet received any
> response on if it is useful or not.
Hey Mats, that *really* was a wonderful piece
[EMAIL PROTECTED] writes:
> A first step to improve the usability of the "programmer reference"
> (which in my opinion is a misnomer)
It's called program reference; suggestions for better names
appreciated.
> would be to give more explicit
> explanations of the possible values for each property.
[EMAIL PROTECTED] writes:
> Nick Busigin wrote:
>
> >Is there a way of placing rhythm marks (slashes) on a staff instead of
> >notes? There is a bar in one of my lead sheets where there is no
> >melody, but there are some chords shown as names above the staff. I'd
> >like to have slashes on the s
Offshore Credit card, quaranteed approval!
enable squalid cyst antwerp godfather vasquez neumann windstorm pathogenesis decant countermen bit nirvana bricklay irvin dogtrot dearborn applicable biopsy titular derogatory billiard applicable execute emmett griswold adipic rosenzweig breadboard exo
I have often clicked a link to find more about a subject instead of
infact finding more about that subject I find scheme stuff.
These issues are not exactly bugs but style issues and matters of
opinion, ie a programmer will think that more information about tremolos
should be the scheme stuff,
Nicolas Sceaux wrote:
Indeed that would be great if \with could be used inside a existing
context:
\context Staff {
BLI
\with { Stem \set #'thickness = #4 }
{ BLA }
BLU
}
I'm not convinced! Since the curly braces are used for so many
different purposes, I think it's much har
Ferenc Wagner writes:
> Bugreports are not the best way to improve documentation,
For the developers, they are.
> It is more work (and more effort) than typing the
> same text straight into the documentation you are reading.
That may be a bit less work for the reporter, but it is much more work
Bryan Koschmann writes:
> Is there a way to print fingerings on a sheet (1, 2 ,3, 4,)? I'm using
> Lilypond 1.7.16.
Dou you mean like:
gis-3 a-4
See also:
http://www.lilypond.org/doc/v1.6/Documentation/user/out-www/lilypond/Articulations.html
http://www.lilypond.org/doc/v2.1/Doc
If you look in the index of the reference manual (since you use 1.7.16,
I looked at the manual for 1.8 which is the closest match to your
version available on-line), you will find an entry "fingering" that
points to
http://lilypond.org/doc/v1.8/Documentation/user/out-www/lilypond/Fingering-instruct
First of all I agree that add work for the maintainer of lilypond is in
the long run a very bad idea.
Making Hans fiddle with the docs means less improvement to the program
that said.
There are many levels to improving the docs. Some issues are infact
really bugs: The doc says do x but it does
37 matches
Mail list logo
