Mats observed:
> Of course it would be nice to be able to view pictures with
> examples also in the info version of the document, but I see
> absolutely no reason for LilyPond to be a pioneer for this
> feature.
This is a very sensible observation. LilyPond is a music typesetter, hence
I'm happy
> I'm ambivalent. The danger is that the number of functions to create
> and manipulate data structures explodes, and becomes harder to
> learn. We have to find a balance between having a small "interface"
> and an interface that is ultra-ergonomic to use.
I think at the moment that Lilypond is a
> Do you think that could actually be interesting? ie: should I go on
> implementing and documenting this?
This sort of thing is great. There's a lot of potential to implement
higher-level convenience stuff that LilyPond currently lacks, but that
doesn't need to be written into the core.
--
http
> Yes, but it also takes me extra time. (I'm a lazy bum). You can
> subscribe to [EMAIL PROTECTED] to get the latest scoops.
Thanks for the tip. You should mention this list on
http://lilypond.org/web/documentation.html
where you should also change "Bugreports" to "Bug reports".
--
http://www.
The problem with not removing the old x.y.zz directory because of the rm
of the ls-R file being in the wrong place is now fixed.
However, when I upgrade I get the error
install-info: menu item `Glossary' already exists, for file `music-glossary'
although now if I look in my info dir file, it o
As well as the cumulative 2.0->2.1 release notes, it would be very helpful
to have per-release release notes, so one can see what has changed between
individual releases.
Also, it seems the 2.0->2.1 release notes is getting a bit inconsistent:
for example, in one place it says LyricVoice no longer
> I think that's not right. E.g. in Hungarian tradition extender lines are
> rarely used, because melismata are indicated by the slurs. So the user must
> be able to disable this feature (if it would be the default).
Of course, I was speaking only of the engraving rules I know about, which
are Eng
> No, what you're seeing is legacy stuff. If you're willing to spend
> some time coding, I'll gladly take on patches that fix this.
If you can give me some pointers, I will. Since I don't know Python,
barely know C++ (but I know C very well) nor Scheme (but I know elisp
quite well) I may be a bit
I've just been entering lyrics for a song, and I've come up with a puzzle:
what is the point of -- and __ ? As far as I can see, there should be a --
between every pair of syllables in a word, and a __ at the end of every
word. Hyphen (-) at the end of a syllable is unnecessary AFAICS.
Of course,
> On Mon, 23 Feb 2004 00:25:55 +0100 (CET) Reuben Thomas <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure who's currently responsible for lilypond-indent.el, so I'm
> > sending this to the list and to Heikki, who seems to be the main
> > author.
> >
> No, no, no! I don't think that it is a good idea to have two different
> default values for a property such as raggedright: if you do not specify a
> \paper block at all, the default would be ##t, but if you say \paper{},
> the default would be ##f. This would be totally confusing for a new
> l
> Funny.
>
> I always have to add
>
> \paper{ raggedright = ##t }
But only if you want raggedright!
> Maybe that's a sensible solution? Having \paper{}/\midi{} correspond to
> \paper { raggedright = ##t } ?
But that would have confused me when I typeset a short score without a
\paper declarati
I can't find any evidence that LilyPond supports source \specials for the
ability to click on a place in a DVI score and be taken to the source (as
with LaTeX) but it seems to me this ought to be fairly straightforward to
implement. Is there any interest in this?
--
http://www.mupsych.org/~rrt/ |
> The default is to supply a \paper{} declaration if no output (paper,
> midi) is specified. Perhaps this default should be changed?
I'm happy with the default as it fits the common case. I'd just it to be
documented (as otherwise the docs are a bit confusing).
--
http://www.mupsych.org/~rrt/ |
> Actually, the settings are changed from the Emacs' menus, and it is Emacs who
> writes the 'custom-set-variables' lines to the initialisation files.
That's true, but I still don't understand what you were after!
--
http://www.mupsych.org/~rrt/ | God is the name of our ignorance (Grayling)
__
> The patch was applied smootly. Thanks. BTW, maybe there are more such
> mistakes.
If I find any more, I'll correct them. Since I'm currently getting to
grips with LilyPond as a new user with a big score, I'm not being
systematic, but just fixing things that annoy me.
> With an example, I referr
16 matches
Mail list logo
