When I left hacking the accidental engraver some 4 years ago, we were
talking about how to implement cautionary extra naturals - that is, so
that modern cautionaries would yield
| # O| (n)b O |
(where O is a whole note and n is a natural)
Until we came up with a solution for how best to
Attached patch fixes bug 106 as well as afaihf unreported bug that
\score {
\new Staff {
\relative c' {
#(set-accidental-style 'modern)
d4 dis'4 d,2
}
}
}
would not put a natural sign on the last d even though it should.
-Rune
---
Han-Wen Nienhuys wrote:
also, maybe you can document the bit going below, and remove the above.
Okie.
Good thing, actually, in the previous patch I made an unneccesary
change. Was unaware that the local key sig was default defined at so
many places.
---
Bugfix bug 94. Now key signature naturals are placed at the same
location as the accidental that they cancels.
Added support for extraNatural in key engraver.
-Rune
--- ../lilypond-2.11.2/lily/key-engraver.cc 2006-11-14 21:28:39.0 +0100
+++ lily/key-engraver.cc 2006-12-18
Han-Wen Nienhuys wrote:
Schhh, don't tell that!
I'm trying to get them hooked on Git :-)
:-)
I promise to take a look at Git.
Would you please do as Johannes suggests, then :-)
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Just made a change with git commit -a, but it does not appear on
http://git.sv.gnu.org/gitweb/?p=lilypond.git.
What is wrong?
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mats Bengtsson wrote:
That you commited the change to your local repository.
You need a git push ... to push it to the sv.gnu.org
repository. See the mailing list archives for more explanations.
Thanks.
Worked! :-)
-Rune
___
lilypond-devel mailing
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Jesse Engle wrote:
1) There is no way that I have yet discovered to notate rhythms for all
four limbs,
Where did you look?
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Percussion-staves
2) LilyPond does not provide ratio-notation for odd groupings. For
instance, if I notate a
somebody forgot to attach include/object-key.hh to git.
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
(going back to the list)
Joe Neeman skrev:
Doesn't work for piano scores, sorry. The VerticalAlignment in a
PianoStaff has its distance fixed so that cross-staff beaming works.
Oh...
I thought that the whole point of the two pass stretching was to get
piano staves to work :-(
Well,
Han-Wen Nienhuys skrev:
Don't forget x-staff slurs and arpeggios.
Works already.
\version 2.11.10
{
\new PianoStaff \relative c''
\set PianoStaff.connectArpeggios = ##t
\new Staff = up {
s1*3 c e1\arpeggio
\overrideProperty
#Score.NonMusicalPaperColumn
Mats Bengtsson wrote:
Wasn't the issue if it worked without the fixed spacing,
No, the issue was whether it worked with setting the fixed spacing
manually for each system - as illustrated in the example.
-Rune
___
lilypond-devel mailing list
I serched the archives without finding this question asked.
We hopefully agree that having to trace the fonts is an ugly hack that
contradicts everything that lilypond stands for.
The natural question is:
Why use fonts instead of pdf templates?
Using templates would allow for the
Han-Wen Nienhuys wrote:
I think the proper solution is to convert all fonts to outlines, and use
mf2pt1. This bypasses the tracing step. See the archives for more details.
I agree.
Would it be to cumbersome to add a two-part font-conversion, using
mf2pt1 for the glyphs that consists of
Han-Wen Nienhuys wrote:
I think the proper solution is to convert all fonts to outlines, and use
mf2pt1. This bypasses the tracing step. See the archives for more details.
Will it be acceptable to require FontForge? I.e. will it be acceptable
to allow overlapping paths?
-Rune
Han-Wen Nienhuys wrote:
Do you have a specific reason why you want to ditch the traced fonts?
You must be kidding.
A huge amount of effort has been made in producing a perfect font. We
have spend hours and hours with magnifying glasses, tweaking the symbols
to get them just right.
Then
Han-Wen Nienhuys wrote:
Well, you have a point, but I suspect that this is hardly visible at normal
printer resolution.
Well.
Tried to produce 1200 dpi version. (by setting zoom-level to 1667% in
acroread).
Attached.
-Rune
___
lilypond-devel
Joe Neeman wrote:
No, Mats is right. If you supply a fixed spacing, everything is easy.
Yeah, easy, I don't know.
But I do know that it does not work today even if you supply a fixed
spacing for each system.
I don't mind having to have to set the spacing manually. It is not
perfect, but it
Johannes Schindelin wrote:
Sorry. Now I actually checked: the url is
http://git.sv.gnu.org/r/lilypond.git
(Note that not only http://; is new, but also /r/).
Still doesn't work here.
$ git pull http://git.sv.gnu.org/r/lilypond.git web/master:web/master
/usr/bin/git-fetch: line 287:
Graham Percival wrote:
What OS are you using?
ubuntu dapper
curl is the default file downloading tool in OSX
(it's like wget). I think the *BSDs also use curl, but git certainly
shouldn't be depending on curl being installed.
Thanks.
Don't know why the hell I didn't try searching for
Trying to get a copy of jneemans branch to try out the new page breaking
and score stretching stuff.
I clone the repository with
$ git clone git://git.sv.gnu.org/lilypond.git
Then I create .git/remotes/jneem containing
URL: git+ssh://[EMAIL PROTECTED]/srv/git/lilypond.git
Push:
Wondering how to solve the absolute pitch-compare-problem I mentioned in
the ambitus bug report, I took a look into how pitches and scales are
represented in lily.
I see that the diatonic scale is represented as
(ly:make-scale #(0 1 2 5/2 7/2 9/2 11/2)
thereby effectively hardcoding a
In System_start_delimiter::print we the check to see whether a
staff-group-symbol should suicide is
if (ext.is_empty ()
|| (robust_scm2double (me-get_property (collapse-height), 0.0)
= ext.length ())
|| (glyph_sym == ly_symbol2scm (bar-line)
non_empty_count = 1))
Rune Zedeler skrev:
Why do we have the explicit check against (glyph_sym == ly_symbol2scm
(bar-line) non_empty_count = 1)?
Oh, well, the check is made to ensure that we do not get a system start
delimiter on a one-staff score.
IMO a better way of achieving this would be setting
It seems that the following bug has not made it to the tracker:
When repeat tremolo 3, one tremolo-beam is missing.
In this example, all staves should get 4 tremolo bars, but staves 2 and
4 only get 3 tremolo bars.
\version 2.10.25
\paper { ragged-right = ##t }
\repeat tremolo 8 { c64 e64
Okay, I took a look.
I understand why the viewers have problems with lilypond's pdfs: For
some reason lilypond does loads of conversions to and from millimeters.
I think it has something to do with lily defining one point to be
1/72.27 inch, whereas a postscript (and pdf) point is 1/72 inch.
Rune Zedeler skrev:
I understand why the viewers have problems with lilypond's pdfs: For
some reason lilypond does loads of conversions to and from millimeters.
Oh, I never learn not to post comments late at night.
The above really had nothing (afaics) to do with the problem.
It should
Han-Wen Nienhuys skrev:
Sounds like bullock's manure to me.
You are right - the problem is not really related to this.
I still think that we should change to 1/72 inch instead if 1/72.27 inch
because this way all staff lines will have same distance on paper and on
screen, whereas with
Valentin Villenave skrev:
If I understand you request correctly, the only new feature needed is
the ability to distinguish between a note that has just ended, and a
note that ended somewhat earlier in the same measure.
Yes, it's much simpler this way :-)
I have thought a bit about it, but
Graham Percival skrev:
LIMITED DISCUSSION
To keep discussion focused and as un-confused as possible, this is a
discussion *only* about the arrangement of subsections. Other parts of
GDP will be discussed later.
This means:
- propose new/changed chapter/sections
- propose renamings of
Citat Graham Percival [EMAIL PROTECTED]:
Just one general comment for the moment: I'd rather propose longer than
shorter subsections. I think that there already is too much fragmentation
at some places for the moment, which means that you never get the chance
to see the full picture as a
Graham Percival skrev:
Well, don't I feel like a complete newbie. :/Does anybody know how
to make Thunderbird treat text like pure bloody text, and not change the
displayed text when it sends an email out? thanks in advance. :(
I don't know what you did wrong.
I just copypasted the
Trevor Bac(a skrev:
As a first pass, I took a look at chapter 8 Advanced notation,
because I've never been very comfortable with the distinction between
basic, advanced and contemporary notation in the current
structure.
It seems like your comments are meant to the online 2.11 documentation,
Very first I comment on the stuff I wrote below: When I wrote it I
didn't really notice / think about the fact the the first five sections
are left out. Probably some of my comments are not totally valid. Well,
I will think some more, and post another message about the overall
structure of the
Citat Graham Percival [EMAIL PROTECTED]:
The all-in-one HTML page is **5 megs**. I'm astounded that so many
people (ie more than 0) are choosing to download that monster _every
time_ they want to look something up in the docs.
We don't.
Browsers have caches, you know :-)
Let me phrase this
Citat Valentin Villenave [EMAIL PROTECTED]:
I think CSS allows to do this without needing an extra (ugly) frame.
It is possible with css, but you would have to redownload the entire toc each
time.
With frames the toc stays and you only load the pages themself.
We were talking loading times :-)
Graham Percival skrev:
Look, the regression tests are not _intended_ as documentation, and they
_should not_ be intended as documentation. They are regression tests!
I agree.
But they should still be easily readable.
Having to search through the lsr for each and every regtest is hopeless.
Trevor Bac(a skrev:
Criterion 1: There's a *complete* enumeration of acceptable values for
each property, and
This will be very difficult make.
And lots of properties takes infinitely many different arguments.
For instance 'stencil can take any scheme function.
I seriously think that
Kieren MacMillan skrev:
development of lilypond will run faster than any effort to try
and keep up with such extended documentation of properties.
Possibly... but an *automated* page -- containing a listing exactly as
Trevor outlined BUT WITH ONLY THE DEFAULT SETTING/VALUE -- would keep up
Kieren MacMillan skrev:
Oops... In that last email, I meant #'staff-position (from
staff-symbol-referencer-interface). =\
Clefs don't have a default staff-position - staff-position depends on
which clef you select.
For G clef it is -2, for C clef it is 0, etc. I do not really see how we
After we dropped the Cello-Woman, we haven't really had a logo.
I suggest to use Valentin's happy LilyPond-note as a logo. I could start
arguing a lot, but hope that it won't be nessesary. The note is just
brilliant.
Comments?
http://valentin.villenave.info/lilypond/music_expression.png
Peter Danenberg skrev:
Comments?
Nice graphically, but contrapuntally offensive; that second example
has a direct fifth.
I wasn't asking for comments on the cartoons - I was asking for comments
on using the note (just the note) as a logo.
-Rune
Why do we have both currentBarNumber and internalBarNumber?
Is there a situation where they differ?
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
This msg. is crossposted to bug and devel.
Please follow-up to only one of the lists.
In latest git, the score-function of Accidental_result looks like the
following:
int score () const {
return need_acc ? 1 : 0
+ need_restore ? 1 : 0;
}
The intention is clearly to sum the
The doc-page refers to http://lists.gnu.org/archive/html/lilypond-devel/
for the mailinglist-archives.
Unfortunately this list only goes back to july 2001.
Where is the complete archive?
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
The current accidental-implementation is not flexible enough.
The webern accidental requires an ugly hack, and Valentins suggestion
for distinguishing neighboring notes is currently not possible.
I therefore suggest:
- Extend localKeySignature to for each local accidental also to contain
Han-Wen Nienhuys skrev:
I have another request though. If you are going to rewrite the thing,
can you think of a representation which is less fragile than the
arcane nesting of lists?
I am not sure what you mean with 'nested lists'.
The current implementation uses lists of symbols and pairs:
Mats Bengtsson skrev:
I hope you have checked the mailing list archives for related feature
requests,
there have been a few such requests over the last years.
Yep, I checked, but I did not find anything - except for valentins
request for recognizing sequences of notes at the same pitch.
I
Rune Zedeler skrev:
I have another request though. If you are going to rewrite the thing,
can you think of a representation which is less fragile than the
arcane nesting of lists?
I am not sure what you mean with 'nested lists'.
Unless, ofcourse, you are referring to the localKeySignature
I would really appreciate my own git branch.
I have some communication going on with Valentin, and it would ease it
alot if he could check out my source code more easily.
Would this be possible?
-Rune
___
lilypond-devel mailing list
I have restructured the representation of the key signature so that each
alteration is a smob of type Key_entry. Now the local key sig knows the
measure-position where the notes associated with the accidentals ends.
I have changed the key engraver og acc engraver to use the new
representation.
Citat Rune Zedeler [EMAIL PROTECTED]:
I would like some comments on
the representation of the key-sig.
Eh, whoops, forgot to mention the branch.
I have pushed it to the branch dev/rune
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Rune Zedeler skrev:
git push [...] dev/rune
...
git checkout dev/rz
Sorry for the noise.
-Rune (really getting annoyed with git)
Sorry.
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
I (think I) made my own branch:
[EMAIL PROTECTED]:~/lilypond/lilypond git push
ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git/ dev/rune:dev/rune
updating 'refs/heads/dev/rune'
from 8505bf3b6810af409fb83e12eba32ff6599a1d17
to 1982a5513e92f4f01605e9dbfdbb997f314b1cac
Generating pack...
It seems that the problem is that I changed MY_PATCH_LEVEL to rz1.
Problem is, that master just updated PATCH_LEVEL from 32 to 33, and
because MY_PATCH_LEVEL and PATCH_LEVEL are defined right next to each
other, the automerge fails.
I resolved the conflict manually.
Try again, Valentin.
What
Thanks for comments.
Han-Wen Nienhuys skrev:
+ int octave_;
+ int notename_;
+ Rational alteration_;
Why don't you use a Pitch object for this combination? You would get
Scale* for free.
Primarily because the two values octave_ and has_octave_ are very
closely related.
They really
Is it not possible to see who have written a given snippet?
If one has corrections for a snippet, what should you do?
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I am looking into splitting pitch into pitchclass and pitch.
Therefore I need to understand what is going on in the pitch class.
Some questions (inserted as c++-comments):
void
Pitch::normalize ()
{
Rational pitch = tone_pitch ();
while (notename_ = (int) scale_-step_tones_.size ())
{
Mats Bengtsson skrev:
Please read under Bugs in the section on Repeat Syntax in the manual.
Isn't the phrasing wrong? Is says so after a repeat timing information
must be reset by hand. Should't that be so between alternatives timing
information must be reset by hand?
-Rune
Joe Neeman skrev:
Did this work before (and if so, what version)? Putting \new Staff before
each voice makes it work for me.
Yep, it works in 2.10.
The staff contexts should be created automatically because pianostaves
do not accept voice contexts.
It also still works in 2.11 if you
Valentin Villenave skrev:
After a lot of work I managed to build 2.6.5. Phew.
(off-topic) Why did you have to build it?
Eh.
I feel SO stupid.
I totally forgot about the binaries.
Thanks.
(The binaries install without problems)
-Rune
___
Carl D. Sorensen skrev:
When I get the latest git release and build it on my system, the build seems to
go fine.
However, when I try to process an input file that contains a key signature
other than c \major, I get the following warnings:
I can't reproduce.
It looks like a font problem.
Reinhold Kainhofer skrev:
Hi,
I understand that for nested StaffGroups, one needs to use InnerStaffGroup for
the inner groups, however, this seems to add only one more possible level to
the hierarchy. Attached is an example where the innermost InnerStaffGroup is
not shown in the correct
Reinhold Kainhofer skrev:
From a user's POV, even requiring InnerStaffGroup instead of StaffGroup is not
obvious.
I agree.
Actually, you might be able to circumvent the problems with the circular
references.
If you insert
\layout {
\context {
\StaffGroup
\accepts StaffGroup
}
Because I by mistake did a merge of the master into dev/rune before the
last time I pushed to git.sv.gnu.org, I undid these changed in my local
branch before making my new changes locally.
But now, if I do
$ git push -f ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git/
dev/rune:dev/rune
Back in 2001 I made a patch to allow for nested StaffGroups.
Unfortunately the introduced cycle in the context-hierarchy introduced a
infinite loop in lilypond, leading to a stack overflow.
I therefore replaced the nested StaffGroups with StaffGroup and
InnerStaffGroup - as some sort of
Jan Nieuwenhuizen skrev:
In software there's no such thing as a temporary solution.
Quoting the changelog:
1.3.142.rz1
===
* Added hacky drum notation/midi. See input/tricks/drums.ly and
ly/drumpitch.ly. Moved midi-instruments to scm.
* Added temporary nested
Johannes Schindelin skrev:
For shared repositories (such as on git.sv.gnu.org), non-fast-forwarding
pushes are not allowed.
Ok.
It would be nice with a better error message.
If I understand it correctly, what you just said is that the --force
option cannot be used on shared repositories.
Johannes Schindelin skrev:
Rune, can you upgrade your git?
That is not so easy - am still running ubuntu dapper.
Dapper official only has git 1.4.4. Trying to install the 1.5.4-debs
from the git-homepage gave dependency problems (libc6 and
libcurl3-gnutls). Building the git sources works
On the 29th of october I posted a beta-fix for nested contexts.
Before we polish it and include it in lily we need to ensure that it works.
For now the fix only allows for directly nested contexts so that
staffgroups can contain staffgroups and choirstaves can contain
choirstaves. We still do
On the 29th of october I posted a beta-fix for nested contexts.
Before we polish it and include it in lily we need to ensure that it works.
For now the fix only allows for directly nested contexts so that
staffgroups can contain staffgroups and choirstaves can contain
choirstaves. We still do
Rune Zedeler skrev:
To test the patch, just download and apply it,
I also managed to get git to work again (thanks Johannes!) so you can
also checkout dev/rune from git.
Though, dev/rune also contains some relatively untested work on pitches,
accidentals and key signatures, so you might also
Ben Fagin skrev:
I have a program that generates random notes. It turns each of the
notes into variables that scheme can understand (noteone = ees'
notetwo = g,, etc).
I am sorry, I still don't understand what you want.
Why do you want scheme to understand the notes?
If you just want to add
(sorry, sent to devel instead of user by mistake. Resending)
Ben Fagin skrev:
I have a program that generates random notes. It turns each of the
notes into variables that scheme can understand (noteone = ees'
notetwo = g,, etc).
I am sorry, I still don't understand what you want.
Why do you
Reinhold Kainhofer skrev:
Notes with n flags can always be composed by stacking more single flags on top
of each other, there does not necessarily have to be a glyph in the font for
this, right?
Hmm. This definitely does not hold for rests.
And we should imo allow for the same durations for
I am a bit surprised that I found no git-documentation on how to test
whether it will be possible to merge two branches without actually
recording the merge.
If I understand the docs correctly, this has to be done like this:
$ git merge --squash ...
$ git reset --mixed HEAD
... (test whether
Johannes Schindelin skrev:
I'd do the merge, but undo it right after that.
Okay that's what I figured, more or less.
Thanks.
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I cannot pull from gnu.org :-(
I have not made any local changes in master branch.
$ git branch
...
* master
...
$ git status
# On branch master
# Untracked files:
# (use git add file... to include in what will be committed)
#
# scm/accidentals-auto.scm.not
nothing added to commit but
I cannot pull from gnu.org :-(
I have not made any local changes in master branch.
$ git branch
...
* master
...
$ git status
# On branch master
# Untracked files:
# (use git add file... to include in what will be committed)
#
# scm/accidentals-auto.scm.not
nothing added to commit but
Johannes Schindelin skrev:
However, in your particular case I would just git pull origin branch
where branch is the branch you actually want to merge.
Thanks! :-)
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
John Mandereau skrev:
building docs in lilypond/gdp and master branch now require Texinfo
4.11.
Hmm, btw, please update the configure-script so that it barks if texinfo
is not at the right version.
-Rune
___
lilypond-devel mailing list
John Mandereau skrev:
that's why
building docs in lilypond/gdp and master branch now require Texinfo
4.11.
This was already discussed on -devel,
Was it?
I cannot find any discussion about this in the archive.
The latest ubuntu - 7.10 - less than one month old - is still at texinfo
4.8.
Am I
Graham Percival skrev:
Hmm, btw, please update the configure-script so that it barks if
texinfo is not at the right version.
That was done at least a week ago on GDP, and a few few days ago on master.
Does not work here :-/
$ git log
commit 2dfa0cc490adf856b7aaa8f637b1c1e127d21b53
Author:
Graham Percival skrev:
Actually, now that I think about it, I had to install something like
libncurses on Ubuntu... but it looked like a standard development
library, so I didn't twice about it.
That did it - thanks!
How did you figure out that you had to install that?
Here, configere didn't
I have put the first attempt at moving accidentals to scheme in dev/rune
branch.
(Please check that VERSION is 2.11.32.rz3 - I have had some git-problems)
* Split pitch into pitchclass and pitch - pitchclass not containing
octave information.
Han-Wen please comment on code. I had some problems
Rune Zedeler skrev:
%%% BEGIN
\version 2.11.32
#(define (start-of-measure-acc-rule context pitch barnum measurepos)
(cons #f (equal? measurepos (ly:make-moment 0 1
mus = {
\key des \major
\transpose c c' {
g16 g g g' g' d' d' d' g' g' f f gis gis g g' ges1
}
}
\new Staff
Mats Bengtsson skrev:
So, why would you bother to use extra key strokes to specify
a note with an accidental?
Of course you wouldn't. But as the notes are represented as notes, they
transpose.
So even though you do not enter an accidental, it might appear after
transposition.
-Rune
Mats Bengtsson skrev:
+ \override TextSpanner #'style = #line
This is wrong - should be #'line
The result will be the same because the result of an undefined variable
is '() and lilypond uses a solid line if the style is not set to a
sensible value.
-Rune
Eduard Drenth skrev:
Can anyone give me a hint? Is there documentation available to start
looking when I have questions like these? Should I learn scheme? Should
I learn something else?
First of all, welcome!
Yes, you should definitely learn scheme - there is a tutorial in the
lilypond docs,
Han-Wen Nienhuys skrev:
what's
midt i at ændre pitch og tilføje pitchclass
Huh?!
I cannot come up with other explanations than that it must be a bug in
git 1.4 that has been fixed in 1.5 because I am unable to reproduce.
I made some changes in some files and added some new files, and
I have made a check for cycles at any length - pushed it to dev/rune.
See files context-def.cc and context-def.hh
Main problem is that Context_def::path_to_acceptable_context cannot
anymore be marked as const because it needs to flag the contexts that it
visits.
Is this ok?
I still haven't
Han-Wen Nienhuys skrev:
I don't think that will work. We can change all these definitions on
the fly using
\with {
\accepts ..
}
Even if this might not be working right now, but it should be in the future.
That is true. It won't work then.
But otoh, afaics the whole
Han-Wen Nienhuys skrev:
+ SCM virtual_smobbed_copy () { // AAARGH!
+return smobbed_copy ();
+ }
for this, we usually have a clone() method, see the
VIRTUAL_COPY_CONSTRUCTOR method; so I suggest to use a smobbed_clone()
function.
DECLARE_SIMPLE_SMOBS (Pitch);
This looks bad. You
Han-Wen Nienhuys skrev:
I think that you it will be trivially easy to use a set iso. writing
into the Context_def.
In dev/rune
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mats Bengtsson skrev:
It is indeed documented in the TupletBracket internal documentation, just
click on the link to tuplet-bracket-interface. Note that the
properties listed
at the main page for TupletBracket in the internal documentation only
contains
the properties that are set by default
Han-Wen Nienhuys skrev:
\set Staff.Tie #'transparent = ##t
\revert Staff.Tie #'transparent \override Staff.Tie #'transparent = ##t
I do not understand this - the two constructs should be synonymous.
No, you're wrong. Perhaps it's confusing due to the terminology from
the time you last
Graham Percival skrev:
What does the \revert command do? It is not mentioned in the RM.
By RM, do you mean LM -- learning manual ?
No, I meant reference manual. I now see that you call it NR.
Section 6.2.7 in the 2.11 version.
-Rune
___
Sorry you totally lost me in this thread.
Afaics the previous post was the first in this thread and it was clearly
a reply to some correspondance between Trevor and Graham.
I could not find this correspondance. Please when changing subject, add
a was statement in the subject line :-(
Which
Kieren MacMillan skrev:
\version 2.11.33
\paper{ ragged-right=##t }
drumStuff = \relative
{
\override TextSpanner #'dash-fraction = #1
\override TextSpanner #'bound-details #'left #'text = \markup {
\musicglyph #scripts.open \hspace #0.2 } c'4 c c c |
c\startTextSpan c c c |
1 - 100 of 255 matches
Mail list logo
