being discussed.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
x27;ll find a first attempt to disentangle
> them.
>
> What do you think?
I have to take a look first. I've been dry-musing yet.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
David Nalesnik writes:
> On Mon, Jul 31, 2017 at 9:08 AM, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> Hi David,
>>>
>>> this refers to
>>> http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html
>>> I opened a
Carl Sorensen writes:
> On 7/31/17 8:08 AM, "lilypond-devel on behalf of David Kastrup"
> d...@gnu.org> wrote:
>
>>
>>Now the thing is that with the new change in place, we would not
>>necessarily _need_ different arguments: an integral multiplier l
Stream events are generated from music expressions during iteration of
music expressions (the interpretation phase making use of engravers
etc).
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Charles Winston writes:
>> On Aug 14, 2017, at 1:20 PM, David Kastrup wrote:
>>
>> Charles Winston writes:
>>
>>> Here is the function inside chord-name.scm
>>>
>>>
>>> ;; chordmode-to-exceptions
>>> (define-safe-publ
David Kastrup writes:
> Charles Winston writes:
>
>>> On Aug 14, 2017, at 1:20 PM, David Kastrup wrote:
>>>
>>> Charles Winston writes:
>>>
>>>> Here is the function inside chord-name.scm
>>>>
>>>>
>>&
Charles Winston writes:
>> On Aug 14, 2017, at 1:34 PM, David Kastrup wrote:
>>
>> David Kastrup writes:
>>
>>> Charles Winston writes:
>>>
>>>>> On Aug 14, 2017, at 1:20 PM, David Kastrup wrote:
>>>>>
>&g
. We want some assurance that recent
changes did not come with big followup problems. And we want the
translation teams to have a chance of catching up to the current state.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https:
on into 2.20.0
are regression and documentation fixes and the completion (or more
likely reversal) of half-finished business.
This is filtered through my personal judgment, of course. Feel free to
volunteer as release manager for 2.22 if you are unhap
James writes:
> On Wed, 16 Aug 2017 22:25:38 +0200
> David Kastrup wrote:
>
>> Ok, I've started sorting out stable and master branch and pushed some
>> 2.21-change on top of some already 2.21-only changes in master.
>
> As I cannot remember what we did in the
David Kastrup writes:
> James writes:
>
>>> What should be done in stable/2.20?
>>>
>>> Documentation/changes.tely should be reorganized: it is currently in
>>> chronological order which does not make sense for the stable release.
>>> I
James writes:
> David,
>
> On Thu, 17 Aug 2017 09:21:03 +0200
> David Kastrup wrote:
>
>
>>
>> Can't think of anything right now.
>>
>
> How about the 'Fixed_x_x_x' label we use in the tracker when a patch is
> pushed. So for exampl
Better luck next time, I guess -- if any.
which apparently reverts an attempt to change it. I don't know or at
least remember the history behind that.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
back delivering music expressions. Those can have a
structure and/or length determined at callback time.
Kicking this into orderly operation does not seem like it would be
reasonably workable.
Iterators are not user-definable at the moment. Either a general
facility or a more specific "
David Kastrup writes:
> Jan-Peter Voigt writes:
>
>> Do you have another idea how to do that?
>
> Timing is established by iterators and they work on music expressions,
> not events. So you need to have an iterator in the race from the start.
> Few iterators ha
David Kastrup writes:
> David Kastrup writes:
>
>> Jan-Peter Voigt writes:
>>
>>> Do you have another idea how to do that?
>>
>> Timing is established by iterators and they work on music expressions,
>> not events. So you need to have an iterator
David Kastrup writes:
> David Kastrup writes:
>
>> Jan-Peter Voigt writes:
>>
>>> Do you have another idea how to do that?
>>
>> Timing is established by iterators and they work on music expressions,
>> not events. So you need to have an iterator
ted it to do when
it happened to end up shelved.
But I guess as a starting point it's likely still a step forward from
having nothing.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
"Phil Holmes" writes:
> - Original Message -----
> From: "David Kastrup"
>
>> If we can agree on stopping unstable releases right now (it just makes
>> version management less of a headache), I'll push outstanding matter to
>> the unstabl
ly
already does the job. I don't think that this warrants a convert-ly
rule though: the Merge_rests_engraver hasn't been around long enough.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
mmit
this as a merge commit from the rebased branch (use --no-ff when merging
or the result will be just the same). But I don't think this is the
case here, and cherry-picking from inside a branch is a recipe for
trouble anyway.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
uainted with the
pushing procedures (in particular our policy of never pushing to master,
of rebasing your feature branches before pushing and so on), I see
nothing to be gained from not letting him cater for pushing his patches
himself at this stage.
--
David Kastrup
___
ject/memberlist.php?group=lilypond>. Don't
> know, just assuming here though.
I should have thought you already got the confirmation mail from
Savannah.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
t that adds
this directory to the loadpath and then calls the real executable.
Hats off, I guess. Probably not a perfect fit as a development
platform, but at least good for running.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e install
and then you have to use something like
CONFIG_GUILE=/opt/guile-1.8/bin/config-guile ./autogen.sh
in order to configure LilyPond.
Compiling LilyPond will produce an inordinate amount of warnings on
current GCC.
--
David Kastrup
___
lily
Urs Liska writes:
> Am 11.09.2017 um 11:23 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Yes, indeed better than nothing (sudo apt install lilypond => "package
>>> lilypond has no release candidate").
>>> OTOH it may take some press
Urs Liska writes:
> Am 11.09.2017 um 14:47 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 11.09.2017 um 11:23 schrieb David Kastrup:
>>>> Urs Liska writes:
>>>>
>>>>> Yes, indeed better than nothing (sudo apt insta
Knut Petersen writes:
>> Hm, will I be able to get a system where I can build LilyPond again?
>
> Urs, building guile 1.8 is a pretty trivial and fast process. Just do
> it and don't care about debian
Depends on the GCC and Texinfo versions
or similar) has
become an established phrase due to the German T9 algorithm's remarkable
reinterpretation (I think on a Siemens M45 mobile or so) of "suspekt".
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ready did not work with gs-9.22rc1.
Did they give a rationale? What kind of PostScript code would have a
chance to work here instead?
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
resulting two fonts will be smaller than the
> original two fonts.
>
> Risking incorrect output for the minimal benefit of a slightly smaller
> file seems unwise to me.
I think "slightly smaller" was something like a factor of 10. We are
talking about files
ocessing (despite the risks that Ken mentioned)
> can use extractpdfmark.
extractpdfmark requires that capability in Ghostscript for doing its
work. It is not a "separate tool" as such.
--
David Kastrup
___
lilypond-devel mailing list
Ken Sharp writes:
> At 20:38 18/09/2017 +0200, David Kastrup wrote:
>
>
>>I think "slightly smaller" was something like a factor of 10. We are
>>talking about files including literally thousands if not ten thousands
>>of graphics (manuals close to a thousan
Ken Sharp writes:
> At 11:33 19/09/2017 +0200, David Kastrup wrote:
>
>>The question is what the complaint should be, namely what LilyPond does
>>wrong. Producing large comprehensive manuals using TeX including lots
>>of example images generated using the same fonts
Ken Sharp writes:
> At 13:42 19/09/2017 +0200, David Kastrup wrote:
>
>>So the mechanisms mostly out of our own control are Ghostscript in its
>>ps2pdf facility, various TeX engines when including lots of
>>ps2pdf-generated PDF files into a main document.
>
> To me
w.youtube.com/watch?v=5BIP_N9qQm4
Are there any example documents with thousands of pages and ten
thousands of PDF inclusions one could look at?
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Ken Sharp writes:
> At 15:44 19/09/2017 +0200, David Kastrup wrote:
>
>
>>Are there any example documents with thousands of pages and ten
>>thousands of PDF inclusions one could look at?
>
> I would suggest that the fact you want to 'include' tens of thous
either lilypond or lilypond-book has an option for
leaving intermediate files around)?
I suspect that those may be of high interest since that is where what
LilyPond does is reflected directly.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-de
fference?
> When we have customers wanting to send us 125GB files I have to say
> that a concern over file sizes in the few megabytes seems a bit picky.
Those 125GB files, I wager, are for one-time printing or further
compression, not for public download from a website. So the comparison
n so, should we take other methods (e.g. using non-embedded PDFs)?
If we figure out a working alternative, we should take it. The current
set of Ghostscript bugs in 9.22 is still a bit in flux, so it's not
clear yet which alternative actually could work.
Is that a reasonable summary of t
for "optimum" rather than "better than awful"
regarding the resulting file sizes. This seems like being close enough.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Ken Sharp writes:
> At 00:41 22/09/2017 +0200, David Kastrup wrote:
>
>
>> > Or, even so, should we take other methods (e.g. using non-embedded PDFs)?
>>
>>If we figure out a working alternative, we should take it. The current
>>set of Ghostscript bugs in
So while I am
not especially thrilled about this particular honor, that doesn't mean
that I don't consider LilyPond to be in high public standing.
All the best
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Francisco Vila writes:
> On 22/09/17 16:47, David Kastrup wrote:
>>
>> Well, the exposure is a bit limited, given that their list is not
>> accessible from their home page and is not even listed on their site
>> map.
>>
>> I am somewhat afraid that at
Graham Percival writes:
> On Fri, Jul 28, 2017 at 08:01:06AM +0200, David Kastrup wrote:
>> ElRay writes:
>>
>> > FYI: This has been reported as a bug -- in 2012.I will see if this is
>> > something I can take-on in the next month or two.
>>
>> I
of Ghostscript?
At any rate: is there any reason for us to actually use glyphshow at all
considering its apparent drawbacks? Or is it intended more for things
that should be treated like glyphs but are produced on-the-fly? Like
beams and stems and such:
ably all of, uh,
BizX? is down.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
>> --few-fonts and --all-fonts
>
> --optimize-fonts and --no-optimize-fonts
No, I don't think that captures the gist of the problem.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 'TeX-GS'
>
> LGTM, thanks!
>
> BTW, is there any chance to reduce the width of the help screen to
> stay within 78 characters?
While we are at it, it may make sense not to refer to the no longer
existing Gmane page for bug reports.
--
David Kastrup
translation until Monday 9th.
>
> I might just be able to read some mails on my father's old windows computer.
Take care.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ittle related to
LilyPond internals and a lot related to Guile and C and C++.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e 2.0 was terribly slow. Is there any progress?
Respective to 2.0, yes. But it's still decidedly awful compared to 1.8
as used in LilyPond.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
hallenge to find good input syntax for it and something to map
it through.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
it to my mentor. Because I have neither a mentor nor
> push ability I assume it’s ok to send the patch files to this list
> instead? See attachment.
I took the liberty of pushing to staging after adding a newline before
EOF on the regtest (git log --check will tell you about whitespace
er
7;16[( b' a']) }
> }
>
> Or is there an undocumented change without a convert-ly rule?
I can actually still see the beam smashed into the left edge of the
page. But it is unlikely to have survived its injuries.
--
David Kastrup
__
those dependencies but have not been able to
find and/or eliminate all.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
r/local/tmp/guile-1.8/bin/guile-config ./configure ...
I got the same problem. However, this appears to be because avoiding
the check for guile-config in this manner appears to _also_ disable the
check (and any useful default) for Guile. So I have to do
GUILE=/usr/bin/guile GUILE_CONFIG=... ./config
>
>
> 4981 Web: Remove links to gmane throughout Website - James Lowe
> https://sourceforge.net/p/testlilyissues/issues/4981
> http://codereview.appspot.com/333900043
According to your web page, those patches are on countdown. I don't
t
>>
>> Now I've removed guile-2.0.
>> I've built and installed guile-1.8 in /usr/local. /usr/local/bin is
>> in my path.
>>
>> But I get this error:
>>
>> checking for guile-config... no
If your configure script is _checking_ for guile-config, you don't have
GUILE_CONFIG set.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ent_iterator will check for stuff
like { g'\repeatTie } whether there is an engraver listening before
deciding whether to leave the event to the discretion of the likes of
"New_fingering_engraver" and keep it on the g' or whether to strip it
off and announce
*lv_tie = make_item ("LaissezVibrerTie", cause);
into
SCM cause = tie_ev->self_scm ();
Grob *lv_tie = make_item ("LaissezVibrerTie", cause);
if (!lv_column_)
lv_column_ = make_item ("LaissezVibrerTieColumn", lv_tie->self_scm ());
I don't think
David Kastrup writes:
>> Is this appropiate?
>
> "cause" here is the actual tie event triggering the column. I think
> that it should rather be the first tie, making the
> LaissezVibrerTieColumn a grob with ultimately identifiable cause but not
> a directly
ssez-vibrer tie
;;
;; Backward compatibility alias
;;
(define-public laissez-vibrer::print ly:tie::print)
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
r. Copying file.
> stepmake/autogen.sh is newer. Copying file.
> processing .
> Running autoconf ...
> Skipping configure process.
>
>
> ~/lilypond-git/build (dev/2-16-test)$ make
> /home/hermann/lilypond-git/stepmake/stepmake/po-targets.make:41: ***
> recipe commences before first target. Stop.
>
>
> Any hints to make it work?
make clean
before calling autogen.sh .
Possibly make distclean .
Or just cloning into a fresh directory.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Thomas Morley writes:
> 2017-10-26 23:26 GMT+02:00 David Kastrup :
>
>> make clean
>>
>> before calling autogen.sh .
>>
>> Possibly make distclean .
>
> Being at lilypond-git/build (dev/2-18-test) I did:
>
> make clean
> make distclean
> cd .
Thomas Morley writes:
> 2017-10-27 8:21 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2017-10-26 23:26 GMT+02:00 David Kastrup :
>>>
>>>> make clean
>>>>
>>>> before calling autogen.sh .
>>>>
>>
Thomas Morley writes:
> 2017-10-27 13:19 GMT+02:00 David Kastrup :
>
>> Maybe make check and/or test-baseline doesn't like a separate build
>> directory? That's the only thing I can think of right now.
>
> Ok, will try later, have to leave soon.
> Though,
of the exercise at
> https://sourceforge.net/p/testlilyissues/issues/5217/#ae0c/7c60/8bbe
> ff
It's a bit tricky. Maybe we should cherry-pick the necessary
compatibility patches to the stable branches' tips? If you want to
bisect, you'd need to skim them in as well, I guess.
Thomas Morley writes:
> 2017-10-27 23:13 GMT+02:00 David Kastrup :
>>
>> It's a bit tricky. Maybe we should cherry-pick the necessary
>> compatibility patches to the stable branches' tips? If you want to
>> bisect, you'd need to skim them in as w
Thomas Morley writes:
> 2017-10-28 18:27 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2017-10-27 23:13 GMT+02:00 David Kastrup :
>>>>
>>>> It's a bit tricky. Maybe we should cherry-pick the necessary
>>>> co
nthesis.
>
> But I must admit I cannot reproduce this misalignment. When I compile
> this single regtest file with 2.19.65 it looks ok. Only when compiled
> using make test it doesn’t. Strange.
There have been changes in the tempo formatting to b
o old test case archives.
It's better to add new test cases. Putting too many tests into one test
case also makes it hard for the regtesters to figure out significant
differences.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@g
responsible for.
Well, it may be workable. At least the current way of putting inversion
and root information on chords is just cryptic.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Charles Winston writes:
>> On Nov 2, 2017, at 11:40 AM, David Kastrup wrote:
>>
>> \chordmode << c >>
>
> When there is no ChordSemanticsEvent (i.e. when chords are entered in
> node mode and not in chord mode) the chord name engraver listens to
> the
> three groups with three beats each.
Can you please come up with actual quotes/evidence for those statements?
Neither of those make much sense, so I'd guess you'd been
over-paraphrasing either. Or alternatively, there are grave errors in
the respective description which warran
Urs Liska writes:
> Am 11.11.2017 um 11:42 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> So, now the first question ...
>>>
>>> The terminology of baseMoment, beats and groups is inconsistent
>>> between the NR
>>> (http:/
Urs Liska writes:
> Am 11.11.2017 um 12:30 schrieb David Kastrup:
>> I find "grouping" without "beat" fine. I could have been responsible
>> for the terminology in the code (pretty sure I wasn't, but it matches
>> the terminology I use quite bet
But, well, that's a weak
argument against it.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
you said the last half dozen times.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Joram writes:
> Hi David, Étienne et al.
>
> Am 02.12.2017 um 09:46 schrieb David Kastrup:
>> Étienne Beaulé writes:
>>
>>> What is the status of this? ...
>> You don't make a better case by repeating yourself endlessly. I heard
>> what you said
x27;t trust me to be capable of doing that job that they
would rather someone else do it.
Which would be fine with me.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
become a matter of time until someone else volunteers.
> Does that make it clearer why I am confused (and perhaps why Étienne
> was asking again)? It is really not meant as an offence. I am just
> trying to understand in which state this issue is.
The same as before, except that I am a whole lot more pissed.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
le release is not high enough for LilyPond users that I could
afford central heating.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
inting out further such problems:
sometimes things like that just happen.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
erly different. Totally so.
Anybody has an idea what may be the cause here? Maybe some
documentation merge gone wrong?
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Chris Yate writes:
> Hi David,
>
> I'm not sure, but I think you're specifying different ranges.
Yes, the rebase needs to be the other way round: I need to rebase on the
_stable_ branch because that's what I start with.
ds to be done.
I'll upload a different and more generic patch today that doesn't change
as much but sort-of opens a different can of worms. But it would need
testing on Windows and I don't really know how to do that even
half-reliably.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
uture.
>
> Does that accord with your understanding, David?
"Shelved" to me more means like it has been assessed and judged to be
outside of the scope that the assessor would consider justifiable in
effort for a stock LilyPond improving programmer.
--
David Kastrup
_
ne complete properly (and
thus also get an image/PDF) though with a warning.
I actually thought I did change this at one time. At any rate, a
_fatal_ error at least seems silly. There is no reason not to continue
here.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Urs Liska writes:
> Am 22. Dezember 2017 15:42:39 MEZ schrieb David Kastrup :
>>Dan Eble writes:
>>
>>> On Dec 21, 2017, at 23:06, beauleetien...@gmail.com wrote:
>>>>
>>>> @@ -110,8 +110,7 @@ LY_DEFINE (ly_interpret_music_expression,
>>&
David Kastrup writes:
> Urs Liska writes:
>
>> Am 22. Dezember 2017 15:42:39 MEZ schrieb David Kastrup :
>>>Dan Eble writes:
>>>
>>>> On Dec 21, 2017, at 23:06, beauleetien...@gmail.com wrote:
>>>>>
>>>>> @@ -110,8 +1
this still works when running the files, giving no warnings. Would
> anyone know why this would happen?
Have you configured with
./configure --enable-checking
(can also be implied by using --disable-optimising ).
--
David Kastrup
___
lilypond-d
eldung/live>
for the Cfp.
And for the bus <https://freedom-tours.de/category/clt2018>
This is one conference that has been very worthwhile and is quite well
organized.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
; (Windows) or "/"
> (otherwise). But in your log "/" is used on Windows as well.
>
> I know that by now Windows can handle both forward and backward
> slashed.
That's news to me. Aren't you confusing this with the C library
commonly used on Windows? An
it to that stance (and it probably should be available
at least as an option) but it's less than great when one is actually
working with transposed notes/themes/parts.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
from (sign string-distance)
>
> Opinions?
We use enough properties of the LEFT/RIGHT kind ((2) and (3) are really
the same option apart from examples/docs) that I don't see a reason to
diverge here. A property 'handedness set to LEFT or RIGHT would be in
that ballp
lyPond uses your system language, part of the "locale".
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nto account) while
creating the output at voice level so that slurs and similar still work.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
up in the left border and
the tuplet numbers appear over the respective first notes. All of which
seems like a seriously messed up X offset rather than the Y offset that
should not even have been changed.
--
David Kastrup
___
lilypond-devel mailing list
901 - 1000 of 6220 matches
Mail list logo
