> (font-file-as-ps-string name full-name):
> /Users/Carl/lilypond-working/out/share/lilypond/current/scm/framework-ps.scm
> :293:28: Wrong number of arguments to # (name file-name font-index)>
>
> It appears to me that the call to font-file-as-ps-string is missing
> a font-index argument.
>
> Any
It seems that lilypond computes incorrect bbox values for EPS images.
While the top, left, and right side is OK, the bottom is always too
far away by a certain (fixed?) amount. Looks like a bug...
Werner
<>___
lilypond-devel mailing list
lilypond-
Jan,
can you add a list of exceptions to your copyright year update script?
Some files like the mf2pt1 stuff are contributed and should stay
as-is. I've fixed that manually in the git, but an automatic process
would be better.
Werner
___
lilypo
> > can you add a list of exceptions to your copyright year update
> > script? Some files like the mf2pt1 stuff are contributed and
> > should stay as-is.
>
> Why is this necessary?
Well, I think it is a kind of courteousy to leave `external' files
unchanged. Additionally, it simplifies updatin
> Do you have a list of files to exclude?
These files come to my mind:
COPYING
tex/texinfo.tex
tex/txi-de.tex
tex/txi-en.tex
tex/txi-es.tex
tex/txi-fr.tex
scripts/build/mf2pt1.pl
mf/mf2pt1.mp
scripts/build/help2man.pl
Werner
__
The output of -dhelp should be more readable now; I've updated also
almost all help doc strings. Please check. Additionally, following
GNU standards, its output is now sent to stdout.
BTW, is it possible to internationalize these help strings? This is
rather important IMHO.
Werner
> And last but not least: what about our own documentation builds?
> Info docs are missing here altogether! Should we include info docs
> and re-root the documentation ball to look like
>
>share/doc/lilypond/Documentation/*
>share/info/dir
>share/info/*
I'm all for it.
Werner
> I'd especially like someone to look at some of the problems with
> lilypond-book. Particularly the margin settings.
What exactly do you mean?
> I would think the reason those problems haven't been fixed is that
> it's more than a few hours to do it, but I would really be surprised
> if it wer
> In several places, but not all, you replaced the text
>
> Default 1.0.
>
> with the text
>
> defa...@tie{}1.0.
>
> I understand that the @tie{} is there to prevent the 1.0 from being wrapped
> onto a line by itself.
>
> Is there a reason that you didn't do it on all of them, or was it just
> > This patch fixes `make web'. Can someone apply it?
>
> ...but it didn't fix `make all'. Sorry about the early post.
>
> This revised patch should fix the issue.
Applied, thanks.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.or
Folks,
a long time ago, if I remember correctly, there was a difference
between lilypond-book's handling of \lilypond and a `lilypond'
environment: The former was (mainly) for inline use, the latter
(mainly) for use in a paragraph of its own.
I would like to restore this behaviour. While it is
The main argument for having `eps-box-padding' was vertical alignment
in LaTeX and texinfo documents due to bar numbers sticking out to the
left. However, the output is already aligned properly with lilypond
1.12.1 even without this option. Since a global value for
`eps-box-padding' is questiona
> The other one is the attached lilypond file, which looks good if you
> just run lilypond on it, but if you run lilypond-book on the
> attached .lytex file, you don't really get a usable piece. I
> reported this issue a few months ago, and someone did do some work,
> so that the music no longer
> someone added a japanese translation of the docs, but after enabling
> it (so it is distributed), I get error (see below). Can someone fix
> this, or disable the translation? This is a blocking issue for
> releasing 2.12.2.
The Japanese translation is for texi2html only, I believe. I can't
s
> We would need a texi2latex translation so that we could use my CJK
> package (to be more precise, my CJKutf8.sty file).
Alternatively, texinfo.tex needs to be hacked for (hard-coded)
Japanese support.
Werner
___
lilypond-devel mailing list
lil
Writing to lilypond-user, I got no reply, thus I'm sending it again to
lilypond-devel.
Werner
==
The following problem:
\score {
\relative {
c1 | c1 | c1 | c1 |% Bars 1-4
}
\score {
\relativ
> currentBarNumber must be an integer, so the value is computed at
> parsing time. If it could be a procedure, which evaluation would be
> delayed at music interpretation time, then it would be possible.
> That requires modifying LilyPond code (unless I'm missing
> something).
>
> For a possible
> There are many LilyPond users in Japan and they need information
> about LilyPond in Japanese. I want them to join to LilyPond
> community without hesitating. They are solving their problems
> individually.
Since there is such a great number of Japanese LilyPond users not
fluent of English, i
> Patch to add the glyph to the feta font and define a corresponding
> \snappizzicato articulation: http://codereview.appspot.com/12862
>
> Werner, can you please take a look at the metafont code and check if
> I did it the right way?
Everything looks fine.
Werner
___
There's an interesting discussion (since five years!) why lilypond
can't be integrated into wikipedia yet:
https://bugzilla.wikimedia.org/show_bug.cgi?id=189
A resumé of the discussion is this last comment (from about a week
ago):
We want LilyPond to be as safe to call as, say, ImageMagick
> The reason to put @c at the end of each line is because a line break
> in a TexInfo file produces a white space in its document and
> Japanese texts usually do not use any white space. @c at the end of
> line prevents texi2html from converting it's line break to a white
> space.
This is a subopt
> `make all' is currently broken on git master. This patch fixes the
> problem.
Applied, thanks.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Compiling the documentation in current git with `make web', texi2html
(CVS version from 2009-01-09) produces zillion warnings like this:
texi2html --I=/home/wl/lilypond/out/xref-maps \
--I=. \
--I=./out-www \
--output=out-www/lilypond-snippets/ \
>> Compiling the documentation in current git with `make web', texi2html
>> (CVS version from 2009-01-09) produces zillion warnings [...]
>
> This was the simplest way I found to make TOC links for individual
> snippets effective, and I guess "makeinfo --html" won't return
> non-zero status with
> while working on an update of the openbsd port of lilypond, i see
> lots of fontforge whinings like this one: [...]
>
>
> What (hopefully newer) version fontforge is typically used for
> lilypond?
I'm currently using a CVS version dated 2009-Jan-23, and I don't get a
single warning.
> And: do
> Hopefully it is really caused by the rounding errors Werner
> mentioned.
Definitely. George says that he fights a never-ending battle :-)
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilyp
LSR files sometimes refer to the manual. Example:
makam-example.ly:
(see the `Learning Manual @version{}, 4.6.3 Other sources of
information' for the location of this file)
Such references to absolute section numbers are error-prone;
additionally, there is no proper hyperlink. Any ide
>> LSR files sometimes refer to the manual. Example:
>
> I almost consider this a bug, especially if they reference the LM.
Yep.
> ... we *could* add a special "html" command for these in LSR. They
> would do nothing in the main LSR view, but when we run makelsr.py,
> we could change the new
> Hidoi! Boku wa oyaji desu? Boku wa tada san-juu-sai! :(
Soo desu ne!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Keyword completion in lilypond-mode.el is by default assigned to
. With my openSuSE 11.1 X11 setup, this key apparently
doesn't exist in Emacs 22.3.1 by default; I've only TAB (which is
translated from ).
It's easy to redefine this with .emacs, but I wonder why
is used at all instead of plain .
> ah is this why I've never been able to get completion working in
> LilyPond-mode?
Probably. Add this to your .emacs file:
(load-library "lilypond-mode")
(define-key LilyPond-mode-map [tab] 'LilyPond-autocompletion)
Werner
___
lilypond-
> [...]. This all looks nice in Ghostview, Acrobat distiller handles
> it and it prints on a Ricoh printer that I have access to. However,
> I cannot make it work on any HP PS printers. I don't think the
> problem is the binary data. It seems that the HP printers don't know
> about the FontSet r
> If one uses the --sort option, one gets dozens of fonts. The Type1
> font is at the second place and increasingly dissimilar fallbacks
> follow. The fontformat= entry does not seem to change anything any
> which way. Using foundry=urw in contrast helps. But that probably
> is asking more tha
>> I don't think so. AFAIK, we want *exactly* the URW versions, so
>> this looks like a good alternative.
>
> Do we really want to use these particular clones in case there are
> supposedly metrically identical fonts installed in a preferred
> setting?
IMHO yes. Those fonts are intended as fall
> Maybe another solution is requiring other fonts, IIRC Werner
> proposed TexGyre Schola a while ago.
If we do the switch (which I still want to do but my usual lack of
time prevents this), we enforce exactly the new font as the default,
so the solution should be the same.
> It looks like a good
>> Sorry, I don't understand the problem. Why will this lilypond fix
>> break something in Canorus or vice versa?
>
> Canorus installs Truetype versions of some of those fonts,
> system-wide. The Lilypond configure command finds some of those
> truetype fonts via fc-match in preference of the us
> May I apply the patch below?
>
> - NCSB_FILE=`$FCMATCH --verbose "Century Schoolbook L:style=$style" |
> - grep 'file:' | grep -v "\.ttf"`
> + NCSB_FILE=`$FCMATCH --verbose "Century Schoolbook
> L:style=$style:foundry=urw" | grep 'file:' | grep -v "\.ttf"`
Looks good to me (if you use
> However, Werner made it sound like Lilypond should come with its own
> version of the fonts and use that, in which case it would seem sort of
> pointless looking for the system-wide installation of those fonts.
We need to find the system's Type 1 fonts to generate OTFs out of
them, with fixed l
> And wait, once we've founded our new group and taken over the world,
> they'll have to call themselves ZEBRA Zebra" :-)
This is not uncommon. For example, the common toad is called `Bufo
bufo' in Latin; the human race is `Homo sapiens sapiens', etc., etc.
Werner
___
> Please review my patch for dashed slurs on rietveld:
Very nice! What do you think about making `dash-definition' either
accept a list of four parameters or a list of lists (with four
parameters each)? Then we could write
#'(a b c d)
and are not forced to use
#'((a b c d))
if the slur i
>> Very nice! What do you think about making `dash-definition' either
>> accept a list of four parameters or a list of lists (with four
>> parameters each)? Then we could write
>>
>> #'(a b c d)
>>
>> and are not forced to use
>>
>> #'((a b c d))
>>
>> if the slur is not split into diffe
> An example of a useful dashed bezier-sandwich arpeggio would be when
> indicating arpeggios presumed to have been accidentally omitted from
> a manuscript, within an urtext edition.
I don't think so. The proper way would be rather to use an arpeggio
typeset with a smaller design size. IMHO a
> Using a smaller design size might work with a squiggle-arpeggio, but
> for composers who use the slur-arpeggio (I think Grieg was one?),
> typesetting a thinner curve might be too subtle a difference.
Ah, I haven't thought of the slur-arpeggio. Yes, I've meant the
squiggle-arpeggio.
Werne
>> Please review this patch here:
>>
>> http://codereview.appspot.com/8874/show
>
> Looks good!
I'm not a good lisp programmer, but isn't the standard method for
searching like that to not use a loop but recursive calls? It doesn't
really matter, but Han-Wen likes to use recursive calls a lot
> I'm a lot more willing to rename this section. I've seen
> somewhere between 3-10 people confused by this in the past 5
> years. "Titular material"? "Headers and footers"? Any
> suggestions for the name?
Perhaps
Headings, headers, and footers
Werner
__
> Or even
>
> Titles, Headings, and Headers/Footers
I don't see an immediate difference between titles and headings. The
latter includes the former AFAIK.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/ma
> Since "Heading" and "Header" are extremely similar, explicitly
> including the word "title" decreases the likelihood of
> miscommunication and misunderstanding, which is what we're trying to
> solve here.
>
> Kieren.
Then I suggest
Titles, Headings, Headers, Footers
or something similar to
>> Then I suggest
>> Titles, Headings, Headers, Footers
>> or something similar to avoid the nasty `/'.
>
> Headings (Titles) and Margin Text (Headers and Footers)
If I read `margin' I only think of left and right margins.
Werner
___
lilypond
Folks,
the files
lily-50e2bfee.ly
lily-7d242e8d.ly
fail to be properly built during `make doc'. Using gs 8.64, I get
messages like
Substituting .notdef for glyphIndex11C in the font IPAGothic
while converting the EPS. Older gs versions like 8.62 abort with an
error, BTW. Reason is t
> A quick fix is to handle those two files specially, explicitly
> activating font embedding while lilypond processes the files.
An alternative is that lilypond itself forces embedding of the whole
font if it detects that the font doesn't provide glyph names.
On the other hand, it would be *very*
[git from today]
Running
lilypond lily-7d242e8d.ly
makes lilypond crash. Below is the full backtrace (I configured with
--disable-optimisation, BTW); not very informative, but...
valgrind gives the following:
Invalid read of size 4
at 0x80519A6: ly_car(scm_unused_struct*) (lily-guile.h
W.r.t the current discussion this might be of interest.
Werner
--- Begin Message ---
This package has been put up at tug.ctan.org and should soon be at your local
mirror
Thanks,
Jim Hefferon
Saint Michael's College
..
> But, the key players dismissed it, did nothing and yes...2 years
> later I am a bit frustrated. My post yesterday asking why after 2
> years nothing had been done, was not really too out of line if you
> think about it.
One of the key players, Rune, has passed away.
We can answer your request
> BTW, I completely agree this thread was not handled well, not only
> by me, but by everyone from its inception to the present entry which
> I hope is its termination. Quite an ugly business! Very bad form
> shown by all! I do offer my apologies for my part, and yes - by all
> means I hope ever
> What do you guys think of including a sample Makefile somewhere in
> the documentation?
Good idea! Perhaps we can manage to avoid GNU make extensions so that
poor Windows users have a chance to try nmake.
Werner
___
lilypond-devel mailing lis
> parts:
> $(LILY_CMD) $(wildcard Parts/*.ly)
> mv *.pdf $(OUTDIR)/
`wildcard' is a GNU extension. It can be circumvented with shell
commands, however, I suggest to name the part files explicitly.
>> $(OUTDIR)/%.pdf: Scores/%.ly
Percent rules are a GNU extension.
>> define movemen
> Pity. In that case, the original approach is best for portability I
> suppose. Here's how I have the "parts" target now:
>
> parts:
> for LILYFILE in Parts/*.ly ; do $(LILY_CMD) "$$LILYFILE" ; done
> mv *.pdf $(OUTDIR)/
>
> It works exactly as it did with the GNU wildcard, except
> My bash-fu is minimal to non-existent, but couldn't you do something
> like
>
> for LILYFILE in Parts/*.ly ; do $(LILY_CMD) "$$LILYFILE" & ; done
> wait
> mv *.pdf $(OUTDIR)/
>
> ?
>
> I'm sure there's a command, and I think it is "wait", that says to
> wait and collect status from all
> I changed the ` backticks to the $() construct on recommendations
> from one of my scripting books, which alleges that backticks are
> old-fashioned.
BTW, you might read the `autoconf' documentation which has a few,
quite long chapters on writing portable make and shell scripts.
http://www.g
> Werner's point about multiple invocations of lilypond is very valid,
> but on a multi-processor machine my technique will use all
> processors. It'll probably be a bit slower on a uni-processor,
> though.
This is getting error prone. If you want to support multi-processor
engines, just write
> [...] I'm wondring about a portable way to determine the number of
> cores/CPUs present to adjust job-count value.
On Linux:
CPU_CORES=`cat /proc/cpuinfo | grep -m1 "cpu cores" | sed s/".*: "//`
Werner
___
lilypond-devel mailing list
lilypo
> INPUTS= $(wildcard *.ly)
IMHO, exactly THIS statement should be replaced with an explicit list
of all input files so that you can disable or enable files at your
wish. Using the `\' character to suppress the end of line, you can
structure this very nicely:
INPUTS = \
foo-a.ly \
foo-
> The terminal output for individual jobs is lost, but it processes
> much faster.
Redirect the logging output to log files.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> A limitation is that the directories in `VPATH' are not expanded and
> must be given directly (this seems to be undocumented; I'll contact
> the GNU make people):
This was my mistake. I forgot about the `shell' function. Here's a
revised version of the Makefile.
Werner
===
>> A limitation is that the directories in `VPATH' are not expanded
>> and must be given directly (this seems to be undocumented; I'll
>> contact the GNU make people):
>
> This was my mistake. I forgot about the `shell' function. Here's a
> revised version of the Makefile.
And two other correct
> Does this now resemble something I can make generic and put in the
> docs?
Not yet. See below for something which fits better the 80 chars line
length limit.
You've forgotten the driver files for the full score and the
movements; I've added it now. Note that it wouldn't be necessary to
menti
> PS: There might be typos in my modifications, so please test them.
Uff, indeed there are typos. Attached an improved version.
Werner
==
#
# This is a Makefile for `GNU make'!
# It uses extensions not available in most
> Are these typos in the block below? It looks as if the $(piece)I.pdf
> after the colon should read "$(piece)I.ly".
Yes, of course these are typos. :-)
> Ok I'm trying to figure a way to make the output file names add
> $(piece)- to each one automatically instead of changing the source
> file na
> For the moment I've added a crude method of putting the midi files in
> the MIDI/ dir:
>
>mv PDF/*.midi MIDI/
>
> If there's a way to automate this it would look nicer. Also, it only
> works on the "make movements" command. I tried "make stamitzIV.pdf"
> just now and it kept the midi file
> i am using a 2.13 lilypond compiled from today's git repo, and i am
> observing - in comparison to a version from around 10th of April -
> that the page breaking strategy seems to have changed significantly.
> Which leads me in one case of a before 47page piano reduction score
> (1 to 4 staves p
>> I don't know what
>> $(LILY_CMD) $<; \
>> means,
This calls lilypond -- or rather the contents of the variable LILY_CMD
-- with the prerequisite (the *.ly file) as the argument.
>> but the two if statements seem to check if there are any pdf or
>> midi files around and then move them to
>> I've made some progress. When I try to run "make score" on Windows
>> XP,
As it stands, the Makefile doesn't work with Windows. For
documentation purposes I strongly suggest to cook up a special
Windows Makefile with the same functionality.
>>%.pdf %.midi: %.ly
>> $(LILY_CMD) $<; \
>> If there is at least one blank (on a german Windows the home
>> directory is called "c:\Dokumente und Einstellungen\")
>> searching does not work.
I suggest that you contact the help-m...@gnu.org mailing list,
providing a minimal (trivial) example demonstrating the VPATH problem.
Either this i
>> Uuh, you are using `%.midi' in the rule but you are moving *.mid
>> files! You should use `%.mid' too since this is what lilypond
>> creates if run on Windows, right? The comment should be updated
>> accordingly.
>
> You're right, but oddly, it worked as expected even without fixing
> the patt
> Here are my candidates:
> "warning: impossible or ambiguous (de)crescendo."
> "warning: impossible or ambiguous (de)crescendo (MIDI)."
> "warning: ignoring impossible or ambiguous (de)crescendo."
> "warning: ignoring impossible or ambiguous (de)crescendo (MIDI)."
> "warning: MIDI found
> warning: lilypond cannot interpret a (de)crescendo.
> MIDI output ignoring (de)crescendo starting at line .
>
> This way the diagnostic states why Lily can't do what the user has
> coded, what it's doing as a result, and the consequences of the
> error condition detected.
This is not
> [...] why not define a function that takes a function and a list of
> pairs? It's usual to have procedure arguments:
>
> (define (map-on-pairs fn pairs)
> (cons (apply fn (map car pairs))
> (apply fn (map cdr pairs
>
> (map-on-pairs + '((1 . 1) (2 . 3) (5 . 8))) => (8 . 12)
> (map
> shortest note playing here.")
> (shortest-starter-duration ,ly:moment? "The duration of the
> shortest note that starts here.")
> + (hide-tied-accidental-after-break ,boolean? "If set, an accidental
> +that appears on a tied note after a line break will not be displayed")
> (sid
The lilypond grammar contains some extremely long lines which look
very bad in formatting (and are difficult to comprehend), for example
206 music_function_chord_body: music_function_identifier_musicless_prefix
EXPECT_MUSIC function_arglist_nonmusic
In the docs there are references to both `beam-grouping' and
`beat-grouping'. This is confusing. However, `beam-grouping' doesn't
exist in the source code. I thus suggest to replace `beam-grouping'
with `auto-beam beat-grouping' just to avoid the term `beam-grouping'
altogether. The snippet `b
Currently, `to-barline' is set to ##f for trills. What about changing
it so that ##t is the default?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> A git grep for beam-grouping returned only the snippet you referenced above.
>
> A git grep for "beam grouping" returned only one reference which was in the
> snippet you referenced above.
>
> Can you be more specific about where the doc references to
> beam-grouping are?
Sorry, for being imp
> What do people think about adding an extra mailing list:
> lilypond-proposals?
I dislike that. Two lists are fully sufficient IMHO. Probably all
lilypond-devel readers would subscribe that too, so where's the
benefit? It makes discussion more complicated if someone is
discussing a problem on
> http://www.jonathankulp.com/makefiles.pdf
. What does the `$' in the directory structure stands for?
. There's a severe error in the `%.pdf %.midi' rule: Its command is
not indented! You have to convert the `tab' characters into
something different (probably eight spaces) to get proper
> I think I've cleaned up all of the indentation problems Werner
> pointed out [...]
I'm still not happy. Use only tabs (which translates to eight spaces)
where necessary. In all other cases I suggest an indentation of two
spaces or nice vertical alignment. Additionally, you should add the
exce
> This makes sense. I think I have it now...
Thanks! A last question: Why is the contents of build.bat
double-spaced?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
>> Why is the contents of build.bat double-spaced?
>>
>
> No particular reason. Should it be single-spaced?
It doesn't matter, but single spacing looks better IMHO in the info
PDF.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
h
> http://www.jonathankulp.com/stable-devel.pdf
BTW, to run stable and development versions in parallel, I do it a bit
differently:
. `stable': Configure and install as normal.
. `devel': Configure with
./configure --prefix=/usr/local/test
and install as normal.
. If I want to
> Maybe I should add your method as well?
I think it's not worth the trouble. I'm just used to my habit, and it
probably really hasn't great benefits.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/l
> I made this change in music-functions-init.ly:
>
> -...@var{\addinstrumentdefinition}.")
> +...@code{\addinstrumentdefinition}.")
>
> However, the \a is still showing up as a control character 0x07,
> [...]
>
> Can someone explain why it works in one file but not in the other?
Documentation
> Clicking on the lilypond.org W3C HTML 4.0 validator button yields errors:
>
> http://validator.w3.org/check?uri=http%3A%2F%2Flilypond.org%2Fweb%2F;accept=text%2Fhtml%2Capplication%2Fxhtml%2Bxml%2Capplication%2Fxml%3Bq%3D0.9%2C*%2F*%3Bq%3D0.8;accept-language=en-us%2Cen%3Bq%3D0.5;accept-charset=I
> (again, I'm happy to dump whatever suggestions people throw at me
> in the CG)
A very nice IDE with editor and debugger (the latter is really nice
IMHO) for python -- both available for Linux and Windows -- is Eric:
http://eric-ide.python-projects.org/
Werner
> Please don't extend the syntax lightly. Try to make something based
> on music functions or \tweak first; if it finds wide spread
> adoption, you can always add cute syntax later.
Given the infrequency of this request, I second this.
Werner
>> > Please don't extend the syntax lightly. Try to make something
>> > based on music functions or \tweak first; if it finds wide spread
>> > adoption, you can always add cute syntax later.
>>
>> Given the infrequency of this request, I second this.
>
> Just found this... (:
>
> http://lists.g
>> > Alphabetical order makes the most sense to me in this case, with
>> > the grob alist.
Yes.
> I prefer case-insensitive so X-offset and Y-offset are near the
> bottom (where I expect to find them). Let me know if you object.
Please use the alphabetical ordering used in other SCM files. I do
>> The formatting is bad.
>>
>> > #(begin
>> >(define foo 0)
>> >(define bar 1))
>>
>> Parentheses are never left alone on a line.
>
> I respectfully* disagree: [...]
Well, putting trailing parentheses into separate lines is useful while
writing code -- I do this too, but finally they get
> Alternatively, a new .scm file (similar to define-grobs.scm or
> define-grob-interfaces.scm) could be created: define-predicates.scm.
> This would define an alist of predicate types and predicates, and
> any predicates that were found by your routine and were not included
> in the define-predicat
> Any thoughts on how to debug this segmentation fault in gdb?
You might try to run valgrind on lilypond, ignoring the zillions of
warnings regarding Scheme (or use a valgrind suppress file -- a few
years ago Han-Wen has posted something): This should give you the `hot
spot' which causes the segf
>> Thanks, these are both fixed now. I've configured PianoStaff to
>> stretch by default, but by a smaller amount than the other staff
>> groups. At this point, though, all of the default settings are
>> provisional (ie. if someone would try out different values and
>> choose something that looks
I would like to see the following implemented, which would *greatly*
enhance typesetting, reducing manual positioning a lot.
The problem: A symbol like `f' is normally positioned below the note
it is attached to. However, since `f' is quite a tall glyph, it needs
a large amount of vertical space
1 - 100 of 3522 matches
Mail list logo
