On 2017/10/06 22:00:07, dak wrote:
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py
File python/convertrules.py (right):
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py#newcode3963
python/convertrules.py:3963: str = re.sub
(r'(\\(?:justify
On 2017/10/06 22:00:07, dak wrote:
> What
> about wordwrap-string, eps-file, with-url, lookup, verbatim-file,
> wordwrap-string-internal, and the accordion commands discant,
freeBass,
stdBass,
> stdBassIV, stdBassV, and stdBassVI?
Some of them certainly are good candidates, as long as their
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py
File python/convertrules.py (right):
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py#newcode3963
python/convertrules.py:3963: str = re.sub
(r'(\\(?:justify-string|musicglyph|harp-pedal|simple|po
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py
File python/convertrules.py (right):
https://codereview.appspot.com/331820043/diff/20001/python/convertrules.py#newcode3963
python/convertrules.py:3963: str = re.sub
(r'(\\(?:justify-string|musicglyph|harp-pedal|simple|po
On 2017/10/06 09:39:11, dak wrote:
I mean exactly what I say: set direction to CENTER (if this would
otherwise
cause problems, temporarily) and call the original callback in order
to
determine staff-position.
I didn’t manage to use these callbacks correctly but maybe my solution
without the
On Thu, Oct 5, 2017 at 7:01 AM, Federico Bruni wrote:
> Anyway, if we decide that the setup script in LilyDev should include your
> proposal, I'll be happy to see a pull request
https://github.com/fedelibre/LilyDev/pull/8
If you decide against including this, I will be OK with that. Perhaps
5 or
Am 06.10.2017 um 17:20 schrieb Federico Bruni:
Il giorno ven 6 ott 2017 alle 16:27, Malte Meyn
ha scritto:
What’s this? I found the same message in the list archive
(https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00084.html)
but I couldn’t find any other hints what to do now. I
Le 06/10/2017 à 16:27, Malte Meyn a écrit :
Hi list,
I tried to compile the regression tests (make test) but this failed with
the following message in input/regression/collated-files.texilog.log:
Undefined subroutine &main::get_index called at
/home/malte/lilypond/Documentation/lilypond-texi
Il giorno ven 6 ott 2017 alle 16:27, Malte Meyn
ha scritto:
What’s this? I found the same message in the list archive
(https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00084.html)
but I couldn’t find any other hints what to do now. If that helps,
my texi2html version is 5.0.
That
Hi list,
I tried to compile the regression tests (make test) but this failed with
the following message in input/regression/collated-files.texilog.log:
Undefined subroutine &main::get_index called at
/home/malte/lilypond/Documentation/lilypond-texi2html.init line 2408.
What’s this? I found
On 2017/10/06 08:42:55, Malte Meyn wrote:
On 2017/10/06 08:19:46, dak wrote:
> Stupid question: is there no way to (re-)use the default callbacks
which know
> about all those little details? Set `direction` to neutral and call
them for
> advice?
I’m not sure what you mean: Don’t do anythi
On 2017/10/06 08:42:55, Malte Meyn wrote:
But there’s this little inconsistency:
{
\override Rest.staff-position = 0
\override MultiMeasureRest.staff-position = 0
r1
R1
}
Hm … I don’t know what I thought when I wrote this. This inconsistency
hasn’t to do anything with a situation
On 2017/10/06 08:19:46, dak wrote:
Stupid question: is there no way to (re-)use the default callbacks
which know
about all those little details? Set `direction` to neutral and call
them for
advice?
I’m not sure what you mean: Don’t do anything to Y-offset or
staff-position but set directio
On 2017/10/06 08:12:23, Malte Meyn wrote:
Thanks for the suggestions, I’ll apply these fixes, test them, and add
a
regression test.
There’s another issue (already present in the “old”
Merge_rests_engraver):
Single-bar or non-compressed MMRs in 4/2 time are positioned
incorrectly because
Thanks for the suggestions, I’ll apply these fixes, test them, and add a
regression test.
There’s another issue (already present in the “old”
Merge_rests_engraver): Single-bar or non-compressed MMRs in 4/2 time are
positioned incorrectly because the engraver assumes they are semibrevis
rests. I w
15 matches
Mail list logo