Re: GDP: links to other doc sections

Graham Percival wrote: It was originally written this way, but I would rather keep all the links in the @seealso section at the bottom. If we absolutely must include some links in the main text, I suppose we could... but I am not (yet) convinced that this is one such case. Why move a

Re: beam bug?

See http://code.google.com/p/lilypond/issues/detail?id=60 for the bug report and a workaround. /Mats Stan Sanderson wrote: I believe I saw this previously reported, but haven't found the discussion (or a temporary resolution). An 8th followed by a 16th rest and 2 or more 16th notes results

forum?

Hi, Can't there be a lilypond forum instead of a lilypond mailinglist? Mailinglists are: somewhat dated, far from structured, and posts tend to become bloated when for instance ppl start quoting quotes of quotes of quotes of quotes, or simply quote a whole post and add one extra line to it,

RE: expressive first draft

Graham said: This is the first draft of Expressive marks. Planned work: REWRITE - articulations. clean up first example, rewrite with appendix list of articulations in mind. - rename to articulations and ornamentations ? Yes. Explain difference between -., ^. and _. Add real

Re: forum?

M.v.Strien wrote: Can't there be a lilypond forum instead of a lilypond mailinglist? No, this would not be helpful. Mailinglists are: somewhat dated, far from structured, and posts tend to become bloated when for instance ppl start quoting quotes of quotes of quotes of quotes, or simply

Re: forum?

One can think of archiving the list via Nabble. http://www.nabble.com/MailingListArchive.html It has been done e.g. on the SuperCollider mailing list (and many others). It has proven helpful. Best -a- On 18 Oct 2007, at 10:48, Graham Percival wrote: M.v.Strien wrote: Can't there be

Re: GDP: links to other doc sections

Mats Bengtsson wrote: Graham Percival wrote: It was originally written this way, but I would rather keep all the links in the @seealso section at the bottom. If we absolutely must include some links in the main text, I suppose we could... but I am not (yet) convinced that this is one such

Re: forum?

What, like this? http://www.nabble.com/Gnu---Lilypond---User-f1722.html Cheers, - Graham Andrea Valle wrote: One can think of archiving the list via Nabble. http://www.nabble.com/MailingListArchive.html It has been done e.g. on the SuperCollider mailing list (and many others). It has proven

RE: expressive first draft

Graham said: This is the first draft of Expressive marks. Planned work: REWRITE - articulations. clean up first example, rewrite with appendix list of articulations in mind. - rename to articulations and ornamentations ? Yes. Explain difference between -., ^. and _. Add real

Re: forum?

Of course (didn't checked) Sorry for the noise -a- On 18 Oct 2007, at 11:08, Graham Percival wrote: What, like this? http://www.nabble.com/Gnu---Lilypond---User-f1722.html Cheers, - Graham Andrea Valle wrote: One can think of archiving the list via Nabble.

RE: pitches second draft

This is the second draft of Pitches. Please have a look; it's been significantly updated. Remaining items are Please let us known if there are any other issues that should be addressed. Only three comments, all points of detail; otherwise looks good: 1. Sharps and flats are used in an

Re: GDP: links to other doc sections

2007/10/18, Graham Percival [EMAIL PROTECTED]: The recommended texinfo solution is to always use @ref{} at the end of a sentence; for more information, see @ref{foo}. This sometimes leads to awkward phrasing. If we group all the references to other sections in the @seealso section, then

Re: forum?

There is http://blog.gmane.org/gmane.comp.gnu.lilypond.general as well. 2007/10/18, Graham Percival [EMAIL PROTECTED]: What, like this? http://www.nabble.com/Gnu---Lilypond---User-f1722.html Cheers, - Graham -- Francisco Vila. Badajoz (Spain) http://www.paconet.org

ReheasalMark in Staff context is broken - can someone verify this snippet is a bug?

There is a problem when moving the RehearsalMark to the Staff context. In the case where the RehearsalMark remains in the Score context (comment out the layout block below), the first RehearsalMark aligns to a Clef and the rest align to staff-bars. This is the correct behavior. But if you move

Tagging Troubles

I'm trying to create a grand staff around two oboe parts when score.ly is compiled. The files I'm using are belowed. % piece.ly music = { % oboe I.II \tag #'woodwinds \new GrandStaff \tag #'woodwinds \tag #'ob12 \new Staff { \tag #'woodwinds \tag #'ob12 \set Staff.midiInstrument = oboe \tag

point-and-click in emacs on Ubuntu

When I install with the GUB, I can set: LYEDITOR=emacsclient.emacs-snapshot --no-wait +%(line)s:%(column)s %(file)s and put urlCommand lilypond-invoke-editor %s into my .xpdfrc, point-and click works for me in lilypond 10.33 on my Ubuntu Feisty system with emacs-snapshot installed.