On Fri, Sep 14, 2012 at 10:13:00PM +0200, Marc Hohl wrote:
\include guitarSettings
\include choirSettings \with { \SATBoptions }
So you are thinking along the lines of the LaTex package system.
I would go along with that.
Bernard.
___
On Mon, Sep 03, 2012 at 08:07:07PM +, d...@gnu.org wrote:
flex documentation is pretty clear about backing up being very
expensive. I don't remember whether it was only expensive when it
happens, or whether the expense was more or less a fixed cost. However,
things like a4 are not
On Fri, Aug 10, 2012 at 12:28:35PM +0200, Jan Nieuwenhuizen wrote:
David Kastrup writes:
Keith OHara k-ohara5...@oco.net writes:
But beware that this uses mixed tabs and spaces, unless you have
configured emacs to use spaces only, as most people prefer today,
Should we put up
On Thu, Aug 09, 2012 at 10:05:14AM +0100, Graham Percival wrote:
** Subset for first phase
In greater detail: I’m suggesting that we have multiple rounds of
syntax stabilization. The proposed elements of current lilypond
notation which we will stabilize is captured by these two files:
On Tue, Jul 31, 2012 at 12:59:16PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
On Mon, Jul 30, 2012 at 11:44:28PM +0100, Bernard Hurley wrote:
On Mon, Jul 30, 2012 at 10:14:37PM +0100, Phil Holmes wrote:
- Original Message - From: gra...@percival
On Mon, Jul 30, 2012 at 02:57:06PM +0100, Graham Percival wrote:
ok, but are we stepping in the right direction here? I mean, if
\relative c' {
\tempo Allegro 4. = 60
}
works but
\midi {
\tempo Allegro 4. = 60
}
fails, I wouldn't blame anybody for being surprised.
On Mon, Jul 30, 2012 at 10:14:37PM +0100, Phil Holmes wrote:
- Original Message - From: gra...@percival-music.ca
lily/output-def.cc:38: Real long_name_len = 0.0;
could these be class member variables instead of global variables?
I don't believe so. I'd be happy to be corrected by
On Tue, Jul 24, 2012 at 04:45:51AM +0200, Werner LEMBERG wrote:
There are *zero* chances that CJK support
(probably based on my package) will ever be added to texinfo for the
original tex or pdftex engine.
I suspected this might be the case.
With XeTeX and luatex, native CJK support
On Tue, Jul 24, 2012 at 11:48:13AM +0200, Francisco Vila wrote:
Take this as the result of a quick reading of the summary. My comment
as a non-expert is that probably a good, reliably working convert-ly
is a substitute for syntax stability,
I disagree. For one thing it is often very difficult
On Mon, Jul 23, 2012 at 03:26:22AM +0200, Werner LEMBERG wrote:
An even better solution would be to
provide a big square with four small digits in it, giving the
character's Unicode value.
An even better solution would be for Texinfo to support these characters.
- Just saying - I wouldn't
On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote:
[1] why oh why does the main GNU editor not use the official
extension language for the GNU operating system??
Same reason why its keyboard shortcuts are only so-so compatible with
CUA and/or GNOME: its development was
On Sat, Apr 21, 2012 at 01:49:38PM +0200, David Kastrup wrote:
Bernard Hurley bern...@marcade.biz writes:
On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote:
[1] why oh why does the main GNU editor not use the official
extension language for the GNU operating system
On Sun, Feb 20, 2011 at 11:08:05PM -0300, Han-Wen Nienhuys wrote:
2011/2/20 Han-Wen Nienhuys hanw...@gmail.com:
This change is default over current lily, so let's put it in. I can't
this change is an improvement over current lily
It took me a lng time see any difference between the
On Sun, Feb 13, 2011 at 03:08:11AM +0100, Francisco Vila wrote:
Lyric ties are essential for vocal music in Spanish because of the
high percentage of the Spanish-language words that end in a vowel.
Also, multiple-syllable words are much more common in Spanish, which
makes notes that share
On Sat, Feb 12, 2011 at 09:04:23PM +, Graham Percival wrote:
We have two ways of making it not a Critical issue:
2) metaphorically look our users in the eye and tell them that we
no longer support that feature. This means adding the following
line to Documentation/changes.tely:
On Sat, Feb 12, 2011 at 11:29:34PM +, Graham Percival wrote:
On Sat, Feb 12, 2011 at 09:55:34PM -, Phil Holmes wrote:
TBH, I'd be disappointed if this issue prevented a release of 2.14.
I think it's a regression, but I also think it's a minor feature,
and the alternatives are
On Wed, Feb 02, 2011 at 07:38:45PM +, Graham Percival wrote:
Let me rephrase / alter my initial suggestion: might it be worth
having some predefined scales for actually well-defined scales?
Like \major or \locrian or the like? They could go in a new
ly/*-init.ly file, or maybe something
On Thu, Feb 03, 2011 at 07:42:21PM +0100, Xavier Scheuer wrote:
On 3 February 2011 16:36, Mike Solomon mike...@ufl.edu wrote:
Hey all,
I have scanned examples from Boulez's Third Piano Sonata, Elliot Carter's
Night Fantasies, Elliot Carter's Sonata, and Stockhausen's Klavierstücke II
On Wed, Feb 02, 2011 at 11:20:22AM +, tdanielsmu...@googlemail.com wrote:
Might it be worth having some predefined scales,
i.e. \diatonicScale and \pentatonicScale and the like?
I don't think so; they are not unique.
I'm not sure what you mean by this. For instance:
\majorScale c is
On Sat, Jan 29, 2011 at 09:46:23AM +0100, Marc Hohl wrote:
What about something like
\draftModeOn / \draftModeOff ?
How about four named modes:
Screen mode - Fastest but good enough for checking on screen. Useful if lily
is being used as a composition tool.
Draft mode - Not that beautiful
Hi
On Fri, Jan 28, 2011 at 11:14:56PM -0800, Dennis Raddle wrote:
I am completely new to LilyPond, but it seems like a good way to get
beautiful notation, and, I hope, experiment with playback algorithms that
add human touch. What I wonder is whether the Scheme extension language
would let me
with the file rtti.c
Of course it is possible that someone may have added them recently with
a view to using them for something, but it looks like historical cruft
to me.
I append a pathch
From 401a52fa2e01da22b8d220e26d5fcb6217fb3556 Mon Sep 17 00:00:00 2001
From: Bernard Hurley bern
Hi,
On Sun, 2011-01-23 at 06:36 -0700, Carl Sorensen wrote:
On 1/23/11 6:22 AM, Bernard Hurley bern...@marcade.biz wrote:
Hi,
In order to understand the lily code better I read Erik Sandberg¹s
master's thesis. The idea of a music stream seems very interesting. Is
this anywhere near
Hi,
In order to understand the lily code better I read Erik Sandberg’s
master's thesis. The idea of a music stream seems very interesting. Is
this anywhere near being implemented?
Cheers,
/Bernard
___
lilypond-devel mailing list
On Sat, Jan 22, 2011 at 10:34:29AM +, c.m.bryan wrote:
Hi, I have an interesting question. I know lilypond is not really
meant for playback. HOWEVER :)
I am wondering if there is a way to hack the source to change the midi
pitch values which are output when it renders. I want to do
Hello,
On Sat, 2011-01-22 at 15:08 -0500, David Santamauro wrote:
On Sat, 22 Jan 2011 12:09:26 +
Bernard Hurley bern...@marcade.biz wrote:
On Sat, Jan 22, 2011 at 10:34:29AM +, c.m.bryan wrote:
Hi, I have an interesting question. I know lilypond is not really
meant
On Sat, 2011-01-22 at 18:37 -0700, Carl Sorensen wrote:
On 1/22/11 5:09 AM, Bernard Hurley bern...@marcade.biz wrote:
On Sat, Jan 22, 2011 at 10:34:29AM +, c.m.bryan wrote:
Hi, I have an interesting question. I know lilypond is not really
meant for playback. HOWEVER :)
snip
On Wed, 2011-01-19 at 20:48 +, Keith OHara wrote:
Carl Sorensen c_sorensen at byu.edu writes:
So what is the current status on 1474?
I think that the latest proposal from Keith O'Hara was to revert ee0488.
Issue 1474 looks like intentional behavior to me, and non-regressive to
I'll take on 1474
Bernard
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
I would find it useful if \keepWithTag and \removeWithTag could take
more than one tag as an argument. so that:
\keepWithTag #'A #'B
would mean keep anything tagged with #'A or with #'B. Would it be
possible to implement this easily?
Actually a Boolean combination of tags as an
/msg00635.html
/Mats
Bernard Hurley wrote:
Hi,
I would find it useful if \keepWithTag and \removeWithTag could take
more than one tag as an argument. so that:
\keepWithTag #'A #'B
would mean keep anything tagged with #'A or with #'B. Would it be
possible to implement this easily
, comments are welcome.
On Dec 29, 2005, at 8:08 AM, Bernard Hurley wrote:
Hi Michael,
On Tue, 2005-12-27 at 16:45 -0500, Michael Haynie wrote:
I had a good look at the proposed alternative mechanism as described
in
lilypondmacros. It mostly worked, but left me with a fair amount
On Sun, 2006-01-01 at 13:12 -0500, Michael Haynie wrote:
Some more thoughts on markup:
1] My method of dealing with this does not currently handle lilypond
markup at all. This is because it uses regular expressions to handle the
header block and assumes the first } is the end of the block. It
is first to do something that I know will work and then to
re-factor it into something more sensible. What I actually want to do is
extract the headers as a list of header,value pairs without having to
know, in advance, what headers exist.
--
Bernard Hurley [EMAIL PROTECTED
try putting the directive:
RemoveHandler .ps
in a file called .htaccess in the same directory as the Perl script.
On Sat, 2005-12-31 at 15:35 -0800, Graham Percival wrote:
On 31-Dec-05, at 5:09 AM, Bernard Hurley wrote:
Looks interesting but I don't seem to be able to download
Sorry, should have said:
RemiveHandler .pl
I've been doing things with postscript files recently and have got the
extention etched into my brain!
On Sun, 2006-01-01 at 12:59 +, Bernard Hurley wrote:
try putting the directive:
RemoveHandler .ps
in a file called
for displaying something readable for lily-47382973.ly
when there is an error.
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
/lilylib.py, line 139, in exit
raise _ ('Exiting (%d)...') % i
Exiting (1)...
lilypond-macros
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, 2005-12-01 at 14:02 +, Bernard Hurley wrote:
Hi,
This discussion, started on the user list. However it now seems more
appropriate for the developer. We started discussing how header fields
might be used in lilypond-book and got on to discussing a possible
extension
to the preamble.
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Thanks, fixed it!
On Sun, 2005-11-27 at 11:46 +0100, Han-Wen Nienhuys wrote:
upgrade/reinstall GS. png16m is a ghostscript file device.
Bernard Hurley wrote:
make web fails with:
/usr/bin/python ../../scripts/lilypond-book.py --psfonts -I ./
Converting to PNG...Unknown device
It's a pity that there is no way of using TeX in markup as it used to be
a very easy way of getting unusual symbols into a score. For Instance I
have a metafont font that prints recorder fingerings and a set of macros
for accessing them (It could be adapted to other woodwind instruments).
In the
Mats Bengtsson wrote:
With the default treatment in lilypond-book, where each score line
is typeset in its own .eps file, it would be extremely tricky to
implement a \lpbookPageBreak, since then lilypond would have to
report information back to lilypond-book on where it should insert
the
This is a problem in all programming languages - what to do with
undefined variables. There are 3 common solutions:
1) Stop with an error message
2) Ignore any statements that contain the variable and optionally issue
a warning.
3) Assume a default value (e.g. {}) and optionally issue a warning.
://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
, schreef Bernard Hurley:
Hi,
ChangeLog entry:
applied.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Sorry, i meant scm/x11-color.scm
/Bernard
Bernard Hurley wrote:
scm/x11-color is missing. cvs diff -u patch only patch files that
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Changelog Entry:
==
2005-04-25 Bernard Hurley [EMAIL PROTECTED]
* scm/lily.scm (ly:load): Add x11-color.
===
The entry in lily.scm had been removed (presumably because x11-color.scm
was missing!). This puts it back.
/Bernard
Attached
It's just my perverse sense of humour
/Bernard
Ralph Little wrote:
I am converting the colour (sorry for the British spelling!)
Don't apologize (or apologise depending on which dictionary you use!)
for spelling it correctly!
___
lilypond-devel
Is this needed? I have the mftrace 1.1.8-1 from debian/unstable
installed and am able to install the latest cvs version of lily.
/Bernard
Erik Sandberg wrote:
Hi,
I've created a mftrace 1.1.9 debian package, if anyone is interested. It's
just a quick hack but it seems to work.
:
Mmmm, what if the text and background color both are not recognized? It
would be neat if there could be a different default for each, unless these
colors can only affect the fonts.
Stephen
- Original Message -
From: Bernard Hurley [EMAIL PROTECTED]
To: Lilypond Development lilypond
OK I'll re-think this one. But not just now as I'm just off to sing in a
choir!
/Bernard
On Thu, 2005-04-21 at 18:26 +0200, Han-Wen Nienhuys wrote:
Op do, 21-04-2005 te 09:52 +0100, schreef Bernard Hurley:
Hi,
No one got back to me on this but I am submitting a patch anyway
I am converting the colour (sorry for the British spelling!) codes
in /etc/X11/rgb.txt, distributed with XFree86, into the format in
scm/output-lib.scm. This is for my own use so that I can say things
like:
\override Staff.StaffSymbol #'color = #AliceBlue
All the multi-word colours have
As of 2.5.19, lilypond-book scours through all EPS files collecting all
fonts used, and outputting a separate file. You should run dvips with
-h file.fonts.ps
I hadn't realised this. Maybe this will solve a problem I had with
printing
If anyone can figure out a sane way to make
On Tue, 2005-04-19 at 15:05 +0200, Mats Bengtsson wrote:
Jan Nieuwenhuizen wrote:
Han-Wen Nienhuys writes:
lilypond-book does not (and never did, afaik) run dvips
Should that not be an option? lilypond-book has all the information
about LILYPONDPREFIX, TEXMF, lilypond.map or
On Tue, 2005-04-19 at 15:14 +0200, Han-Wen Nienhuys wrote:
Op di, 19-04-2005 te 14:54 +0200, schreef Jan Nieuwenhuizen:
Han-Wen Nienhuys writes:
lilypond-book does not (and never did, afaik) run dvips
Should that not be an option? lilypond-book has all the information
about
On Tue, 2005-04-19 at 14:10 +0200, Han-Wen Nienhuys wrote:
As of 2.5.19, lilypond-book scours through all EPS files collecting all
fonts used, and outputting a separate file. You should run dvips with
-h file.fonts.ps
this should provide both the feta and other fonts. If it doesn't,
(lily-893995012.ly)'
can you investigate what went wrong if you run
ps2png.py --verbose by hand on this file? I suspect a GS problem.
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
On Sat, 2005-04-16 at 01:08 +0200, Han-Wen Nienhuys wrote:
When called from lilypond-book, LilyPond does _not_ take care of
formatting the pages. This is precisely the reason I started using it.
So that I can have a multi-movement score with fancy headers, table of
contents, etc. What it
Added to changelog:
2005-04-16 Bernard Hurley [EMAIL PROTECTED]
* framework-eps.scm: code added so that a macro \betweenLilyPondSystem
with one parameter can be defined in a LaTeX file when processed
by lilypond-book this will be evaluated between the systems
What's an Implementation documenter? Is this providing documentation
for programmers?
Cheers,
- Graham
Yes, so that programmers can find their way around the code. I'm not
sure that Implementation Documenter is that best term to use, but I
can't think of a better one at present. The idea
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
Added to Changelog:
2005-04-17 Bernard Hurley [EMAIL PROTECTED]
* scm/framework-eps: When \betweenLilyPondSystem is defined
systems are in separate paragraphs.
Rationale:
Some LaTeX commands do not take effect until the end of the paragraph -
in this case after all
It `normalises' the `@' character, so it no longer is of type
`letter'. I also wonder why it's here. Additionally, it should
be
[EMAIL PROTECTED]
to make TeX stop parsing after the `2'.
Isn't his what \makeatother is for?
This isn't defined for plain TeX.
I would appreciate if I in latex could get the first and last \piece,
\mark number, and bar number on a page to be able to put it in page
headers/footers, or add some footnotes from within the music,
as some editors do.
These are things I would like to be able to do(especially the
\includegraphics.
Yes, I agree. Go forth and provide a patch!
Werner
Will do -as soon as I have convinced myself I havn't broken anything!
/Bernard
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Laura Conrad wrote:
Getting latex to not render a footnote marker is pretty easy. You
just say:
\footnotetext[1]{Here's the first footnote.}
Of course, I've been away from LaTeX for too long!
The sort of thing I had in mind was to get lilypond-book to (optionally)
produce a LaTeX
I have somewhat rashly volunteered to be Implementation documenter.
Han-Wen informs me that various abortive starts have already been made
on this. So if you have any material that would be useful, please e-mail
it to me.
thanks
/Bernard
___
.
regards
Bernard
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
,
Bernard
--
Bernard Hurley [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
71 matches
Mail list logo
