while my main
computer is being repaired; I must have hit the wrong button. Thanks
for noticing.
--
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
is
patch than match the legacy behavior in this case. If it can be improved at
all, it can be improved separately.
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
he part combiner involved at all before this mention?
Similar warnings could simply indicate a shared cause.
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nded vs. not expanded vs. church rests
* with and without measure counts
* etc.?
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
d as a known issue?
Wouldn’t it be more logical for an expanded R1*3\fermata to be engraved like R1
R1 R1\fermata?
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
gt;
It’s a bit long to quote, but his major premise is that \fermata on a
compressed multimeasure rest is ambiguous to the point of being useless.
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
cian but that's entirely the composer's choice and fault).
I agree, though I won’t suggest that the issue should block acceptance of this
patch, since \fermataMarkup had the same problem. Treating it as a known issue
would be nice.
—
Dan
___
li
On Jun 5, 2019, at 09:33, d...@gnu.org wrote:
>
> The resulting comment text is nonsensical. That might have been a clue
> that the resulting behavior is not up to par, either.
I took a new job last October and it doesn’t leave me with much energy to dig
into LilyPond issue
s you
> noted in long vs int, unicode vs str, StringIO vs io, iter.next vs
> iter.__next__, reload, xrange vs range.
Are these complications desirable? A clean and obvious implementation
requiring Python 3 will be easier to maintain.
—
Dan
___
r py changes are done, will the current makefiles
continue to work in environments with Python 2, but require updates to work in
environments with Python 3?
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ail when you
get there, e.g.
$(outdir)/%.pyo: $(outdir)/%.py
false # DO NOT COMMIT
$(PYTHON) -O -c 'import py_compile; py_compile.compile ("$<")'
If your tests are exercising those rules and nothing else seems to go wrong,
on3 targets) and that I think it would
> be something in if statements in python-module-vars.make to be in pseudo-code:
That’s what I needed to know. I’ll investigate.
Thanks,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
htt
start of its recipe.
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Issue 5564 is being neglected. I need some help understanding how to reproduce
the test failures.
https://sourceforge.net/p/testlilyissues/issues/5564/
<https://sourceforge.net/p/testlilyissues/issues/5564/>
—
Dan
> On Oct 8, 2019, at 07:05, James Lowe wrote:
>
> Hello,
&
ng
changes for review.
This is not intended to satisfy “normal” users, but it will be a part of my own
composing workflow until another solution is available.
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/li
y request that as you are working on this process, you try to avoid
making (1) more difficult.
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
he latest Xcode. Rather
>> than try to understand why, I switched to gcc9 and it seems to work fine.
>
> I do not have objection to that. :-)
And I’ve been building LilyPond with gcc 9 in a pre-release Ubuntu 19.10
container for about a week with no surprises yet.
—
Dan
___
encies and do exactly what needs to be
> done. The difference in behavior between these cases seems contrary to that:
>
> make && make check
> make check
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> On Oct 8, 2019, at 12:04, Dan Eble wrote:
>
> On Oct 8, 2019, at 11:09, Carl Sorensen wrote:
>> Federico Bruno says the latest LilyDev includes a Docker container.
>> http://lilypond.1069038.n5.nabble.com/LilyDev-0-3-released-td217945.html
>> <http://lilypond
can fix
the local-test warning at the same time. The collated-files.list warning is
possibly too involved to tackle now.
Regards,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lso be helpful.
Thanks in advance,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ntly, just in case I’m doing
something wrong.
Thanks,
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
le.in:357: recipe for target 'test-redo' failed
make: *** [test-redo] Error 2
$ cat /home/user/lilypond-build/input/regression/collated-files.texilog.log
*** Can't find merge-rests-engraver.texidoc, skipping (l. 25250)
Max error number exceeded
—
Dan
__
hope it works with other recent browsers.
My question for the developers is would you use this if it were available?
—
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nes created after this commit (a few back from the current tip of master)
will create out-test-baseline/share as a symlink.
0d7744aad0 Issue 5572/1: Compile modified C++ files automatically before
testing
—
Dan
___
lilypond-devel maili
On Oct 14, 2019, at 21:59, Dan Eble wrote:
>
> On Oct 14, 2019, at 18:27, Carl Sorensen wrote:
>>
>> What is the defect you are seeing? The last time I tried it, it worked as
>> described in the CG.
>
> I wiped my build directory and ran these commands with
ment with Python 2.4, GCC
3.4, and similarly aged versions of other tools, and run additional tests in
that environment.
Thanks,
—
Dan
u think
my time would be better spent preparing a patch that cleanly undoes the 'share'
change, I'm open to hearing it.
—
Dan
rd may well be a revert or a timely followup patch.
This is an answer to my question, though my recent perception (which is
possibly incorrect) was that receiving some public heat was included in the
cost. Anyway, I'm sorry that my recent contributions haven't worked for
everyone; it's not for lack of trying.
Regards,
—
Dan
from here. Maybe tomorrow I'll look for other logs or
start learning about the makefile.
—
Dan
s still not there, so the investigation will continue.
https://github.com/gperciva/gub/compare/master...DanEble:dev
—
Dan
ils for me, but I don't think it's related. There are
messages about shared library versions not being found.
—
Dan
for other than the commits in the pull
request.
A few minutes ago, I pushed revisions in response to your review, after
verifying that a clean build still got beyond lilypond-test stage. Note that I
did reorder and "fixup" some commits after testing.
Regards,
—
Dan
sf
> issue—resulting in a missing Rietveld link on
> www.philholmes.net/lilypond/allura/ Does anybody know why that is happening?
I'll investigate. Don't subscribe to this ticket unless you want to be
interrupted frequently. :)
https://sourceforge.net/p/testlilyissues/issues/5591/
—
Dan
On Nov 2, 2019, at 12:35, Dan Eble wrote:
>
>> when uploading a first patch set, git-cl asks for a sourceforge issue
>> number. If a new issue is created, everything is fine but when you choose an
>> existing issue, there is some 404 error and the Rietveld link is not adde
e is called guile-config1.8 instead of
guile-config-1.8 or guile-1.8-config.
—
Dan
Please review. This handles a couple of details I'd rather not have to
remember to do when submitting the patch or fix after the fact. I've exercised
these changes for the last few LilyPond patches I've uploaded.
https://github.com/gperciva/git-cl/pull/6
Thanks,
—
Dan
quot;
I guess we're not going to ask Savannah if they can change something on their
end to make this unnecessary?
—
Dan
time make -j3 CPU_COUNT=3 -C Documentation out=www out-www/changes.pdf
The last command yielded a readable file in Documentation/out-www/changes.pdf.
—
Dan
.
—
Dan
extra work and it is a usable workaround for Lilypond's restrictions.
>>
>> Sometimes even \unfoldRepeats doesn't do the trick.
I haven't used bar checks. Have you tried setting the ignoreBarChecks
property? If you don't know what that means, and if you are willing to post a
minimal example of the problem, I am willing to try setting it for you.
—
Dan
On Nov 27, 2019, at 11:35, Carl Sorensen wrote:
>
> It’s not bar checks causing the problem, it's bar number checks.
Oh, thanks for the correction.
It doesn't look difficult to add a context property to deactivate bar number
checks. Would that be the ideal solution?
—
Dan
'm looking at the existing regression tests, and I don't see why we need both
of these:
./input/regression/bar-number-check.ly
./input/regression/bar-number-check-warning.ly
Am I overlooking something?
—
Dan
On Nov 27, 2019, at 14:19, Dan Eble wrote:
>
> On Nov 27, 2019, at 12:06, Carl Sorensen wrote:
>>
>> From the user point of view, the ideal solution would be that if a score
>> that includes bar number checks was handled by a midi block , the bar
>>
, so maybe I can help you.
Please provide more detail. What are the inputs and outputs of your tests?
What steps are involved? Are expectations coded such that your script can
detect whether the tests passed or failed, or is human review required? etc.
—
Dan
> On Nov 28, 2019, at 18:57, James wrote:
>
> hello
>
> On 28/11/2019 21:00, Dan Eble wrote:
>> On Nov 28, 2019, at 15:07, lilyp...@de-wolff.org wrote:
>>
>>> Is het possible to do this kind of tests in the current lilypond regression
>>> tes
On Nov 28, 2019, at 19:22, Dan Eble wrote:
>
> Well, step one is to avoid intertwining the existing xml->ly test
> infrastructure with the new ly->xml test infrastructure. I would put ly->xml
> test input in a different directory. I would probably also plan to renam
placed all
your output files in $(outdir), the existing infrastructure should then remove
them automatically.
—
Dan
rious disputed
answers about autoconf on community Q&A sites.
—
Dan
complaining about index.html. What version of tidy do you have
(tidy --version)? My build environment has 5.6.0 and it isn't complaining.
—
Dan
0
I'll try to get it and fix the issue. I'm not sure if you can work around it
by some argument to configure.sh, but you should be able to work around it by
changing TIDY to "false" in config.make in the top-level build directory.
—
Dan
>>> $ tidy --version
>>> HTML Tidy for Linux version 5.2.0
>>
>> I'll try to get it and fix the issue.
https://codereview.appspot.com/551250043/
—
Dan
ndition
of your system.
It would be nice if patchy-staging used tidy, but it isn't a high priority.
It is wise for a contributor making changes to output-distance.py to install
tidy.
—
Dan
On Dec 7, 2019, at 04:36, Thomas Morley wrote:
>
> Btw, to get access to the "flip"-functionality I need to allow it in
> NoScript of my firefox. Intended?
Yes. It requires JavaScript, as do the filter links at the top.
—
Dan
tion. I'm willing to revert it and leave it for the
next person who notices it, if that bothers you less than piggybacking on this
issue.
—
Dan
support not picking improvements to the development workflow. A person
maintaining 2.20 will need to avoid referring to the 2.21 Contributor's Guide,
but hopefully that's understandable.
—
Dan
On Jan 4, 2020, at 06:09, Peter Toye wrote:
>
> Thanks for that. As everyone seems to be on all the mailing lists. I sort of
> assumed that cross-links wouldn't be necessary.
I am subscribed to lilypond-devel only.
—
Dan
scores that rely on
automatic context creation are engraved. Is a change justified either on the
grounds that the current behavior is a bug or that the NR gives fair warning
not to rely on this feature?
—
Dan
e itself into the same staff as the c' ?
You didn't specify a staff for the d', so I don't see grounds for
dissatisfaction if LilyPond were to do that. Having said that, my work in
progress produces the same output as master for this case, so it might not be
something we need to debate. I don't understand why yet, and I ought to, so
thanks for this case.
Regards,
—
Dan
Staff be a part of the
> StaffGroup.
The context schema makes these cases different.
In the new-Voice case, the Score does not accept the Voice directly. A Staff
is required between the Staff and the Voice, so the question "Which Staff?"
arises.
In the new-Staff case, the Score accepts the Staff. Placing it in a StaffGroup
is not considered.
(Thanks for the rest of your reply too; I haven't digested it all yet.)
—
Dan
On Jan 7, 2020, at 09:26, Dan Eble wrote:
>
> On Jan 6, 2020, at 17:01, David Kastrup wrote:
>>
>>>> If I write
>>>>
>>>> << \new Staff { c' } \new Voice { d' } >>
>>>>
>>>> should the d' in
On Jan 8, 2020, at 12:53, Zone Dremik wrote:
>
> I'm bound to ask; is this the end of for support of Mac OS?
I suggest checking the lilypond-devel archive, where people have been
discussing macOS this very day.
https://lists.gnu.org/archive/html/lilypond-devel/2020-01/msg00052.html
—
Dan
he calls
to isinf() in offset.cc either as ::isinf() or std::isinf(), and report which
of the two avoid the error. I expect that either one will work, but it would
help to see it happen.
Regards,
—
Dan
.
I've been building master with flex 2.6.4 and I have not had any problem.
—
Dan
On Jan 9, 2020, at 10:09, Dan Eble wrote:
>
> On Jan 9, 2020, at 07:32, Michael Käppler wrote:
>>
>> /home/dev/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/flower/offset.cc:132:23:
>> error: call of overloaded 'isinf(Real&)'
On Jan 10, 2020, at 15:52, Michael Käppler wrote:
>
> Hi Dan,
> GUB still fails to build lilypond in offset.cc. See attached log.
> Anyone out here using LilyDev1, who can build current master through GUB?
> Now testing, if I can build release/unstable.
>
> What I would
On Jan 10, 2020, at 16:21, Dan Eble wrote:
>
> It seems that this implementation of the standard library declares ::isinf
> when is included. The three solutions I can think of are (a)
> finish issue 4550, (b) require a version of the library that does not do
> this, or
-f/var/folders/3k/ftz328kw8xj94s0059bcsnx8gp/T//lilypond-zC36CX)' failed
(256)
I tried processing input/regression/bend-bound.ly in the GUI; the result was
similar:
Processing `/Users/dan/Music/LilyPond/bend-bound.ly'
Parsing…
Interpreting music…
Preprocessing
ftz328kw8xj94s0059bcsnx8gp/T//lilypond-gJjMWd)' failed
(256)
fatal error: failed files: "./simple.ly"
—
Dan
prependdir GS_LIB=$INSTALLER_PREFIX/share/ghostscript/9.50/Resource/Init
—
Dan
project's workflow.
My question here is, do I need to maintain extreme caution if I continue using
this tool? Would the git server actually delete origin/staging if I hit the
wrong button by mistake?
Thanks,
—
Dan
t's wise to avoid disturbing `make website` for now. My point is
that, if revising `make website` might eliminate the need for the kludge, then
it is premature to require me to change my build environment. I'm not asking
you to understand it all now, but to understand it before asking me to cope
with it. I'm glad to hear that you are willing to live with the kluge for now.
—
Dan
ld only touch the build directory.
Well, plan to commit the ugly little hack; however, I will experiment with this
if I have time.
—
Dan
quot; but
I am not now prepared to elaborate.
—
Dan
On Jan 20, 2020, at 11:40, Carl Sorensen wrote:
> I agree. And while comments during countdown are annoying and frustrating,
> it's even more annoying and frustrating to have a commit reverted. So I
> prefer countdown to reversion.
+1
—
Dan
comments could have a bad impact if, say, it inserts an accidental stray
character and is not tested sufficiently.
James' report demonstrates that even if multiple devs agree that a change is
trivial, it should still be tested before being pushed.
—
Dan
ing me to publish some of the private changes I've been testing, rather
than trying what's in Federico's repo. I tend to slack off in that regard
because no one is asking.
—
Dan
% CSS
\context [@id=choir]/[@id=soprano] { … } % XPATH
%% find the context where the rehearsalMark property is defined
\context [rehearsalMark] { … } % CSS
\context [@rehearsalMark] { … }% XPATH
—
Dan
as creating \new Voice = soprano { … } within an existing-or-new
context of unspecified type and ID "choir".
If we decide what we want from \context first, it will probably be pretty
obvious how \new should work.
—
Dan
uld be interpreted as shorthand for this:
\context %{ unspecified %} = foo {
\context %{ unspecified %} = bar {
\context %{ unspecified %} = baz { … }
}
}
—
Dan
LilyPond even though the
> concept may be considered fitting.
I'm glad you agree.
—
Dan
and regards,
—
Dan
about the implementation of those to answer, I've
forgotten it.
—
Dan
nd machine time to test
this patch in GUB, it would be very helpful. The first attempts at this change
(some years ago) were plagued by issues that didn't show up until after the
changes were pushed. I expect that they have been fixed, but it would be nice
to be sure before pushing.
https://codereview.appspot.com/579240043/
—
Dan
;s repo?
Federico has merged a couple changes already. This is the last one I have
planned:
https://github.com/fedelibre/LilyDev/pull/19
—
Dan
On Jan 24, 2020, at 03:49, Han-Wen Nienhuys wrote:
>
> (I think Dan is nine.fierce.ballads?)
sort(Dan.full_name) == sort('ninE Fierce ballaDs')
—
Dan
x27;ve been trickling in changes of this nature for a few months, and I'm content
to keep it up if we can agree that it's the right thing to do.
—
Dan
On Jan 24, 2020, at 11:11, d...@gnu.org wrote:
>> Don't assume the hash function is perfect: create the table with more
> buckets,
>> say 2*size.
>
> I'd not do that. It's second-guessing the implementation. The size
> should be good as a hint. In particular if there are actual
> duplicates...
g--lilypond.git-master/flower/include/interval.tcc:142:14:
>> error: 'std::to_string' has not been declared
...
>> Probably:
>>
>> commit 9cf6b20aefd79be13c7678d4cc834434b7ca000d
>> Author: Dan Eble
>> Date: Sat Jan 11 08:55:36 2020 -0500
>>
>&g
mpiles.
In stepmake/stepmake/c++-vars.make, EXTRA_CXXFLAGS is defined with "-std=c++11"
in it, so I don't understand why Harm is having trouble.
Could something in GUB be overriding that option?
—
Dan
[1] https://lists.gnu.org/archive/html/lilypond-devel/2019-12/msg00072.html
[2] https://godbolt.org
the variable.
> Please don't do stuff like that, if necessary using
>
> git reset --hard
I don't understand from this description exactly problem you experienced and
where in my development process you would have wanted me to use that command.
—
Dan
ort I16;
* flower-proto.hh:typedef unsigned short U16;
* flower-proto.hh:typedef unsigned U32;
* flower-proto.hh:typedef int I32;
* flower-proto.hh:typedef unsigned long long U64;
—
Dan
;
3. a makefile target that automatically restyles all source so that "make
check" will pass. Only the files that need to be modified are touched. This
runs only when requested, never as a prerequisite of any other target.
—
Dan
. See some examples at
https://en.cppreference.com/w/cpp/language/types .
—
Dan
On Jan 27, 2020, at 10:13, David Kastrup wrote:
>
> None relevant to GCC and Clang as far as I can see. Can you clarify for
> which platforms you expect a practical concern?
No. That would require a level of effort that is a reason I never mentioned
these things before.
—
Dan
s test their code and it will happen during the review countdown.
If you also build a style check into the final tests before merging staging to
master, the goal will be achieved.
—
Dan
"\n fldcw (%ebp)"
+"\n pop %eax"
+"\n pop %ebp"
+ );
+ fprintf(stderr, "done.\r \r");
What does this do? Is it something that could be handled portably with these
C++11 functions?
https://en.cppreference.com/w/cpp/numeric/fenv
—
Dan
stand out like a sore thumb.
We must be miscommunicating, because I see a lot more than 2. For some
examples,
git grep 'vector<[^>]\+> &'
Please clarify.
Thanks,
—
Dan
On Jan 30, 2020, at 05:17, truer...@gmail.com wrote:
>
> How about this patch?
> Sorry, not tested.
Bringing the _FPU_SETCW() branch and the asm() branch closer together is an
improvement.
(I don't have the resources to test this patch.)
_COUNT=9 make -j9 doc ends with
I did a bunch of build-related stuff in Oct-Nov, but this doesn't trigger any
specific memories. After I eat lunch, I'll try to reproduce the problem and
see if I can spot anything helpful.
—
Dan
1 - 100 of 835 matches
Mail list logo
