[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Time signature position broken
From: |
David Kastrup |
Subject: |
Re: Time signature position broken |
Date: |
Mon, 24 Nov 2014 10:40:01 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
David Kastrup <address@hidden> writes:
> Urs Liska <address@hidden> writes:
>
>> With a build from current master (151120c3240601fd29bbb20a315decbde681fcdb)
>>
>> compiling
>>
>> \version "2.19.16"
>>
>> {
>> c'1
>> }
>>
>> results in the attached output. This is not related to the concrete
>> example but a general issue: The time signature is printed completely
>> at the left edge of the staff. I suspect it has something to do with
>> recent time signature code changes?
>
> I should think that nobody will complain if I figure out the responsible
> commit and revert it. Could be time signature code changes or spacing
> changes, but I think we don't want to wait for a "proper fix/rewrite" to
> go through the complete pipeline for getting this back to normal.
>
> It is strange that such a problem should have made it through regtests
> unnoticed.
I don't see this effect either with current master
commit 2f6c938f9897f6106e0673a6bf16d4e570395a3e
Author: Keith OHara <address@hidden>
Date: Sun Nov 23 22:25:30 2014 -0800
issue 2724
nor do I see it with 151120c3240601fd29bbb20a315decbde681fcdb which is
rather old (68 commits behind current master, admittedly including
several commits from the translation branch).
Now even assuming that you confused origin/master with your local master
branch, I cannot corroborate your finding. Admittedly, the last commits
in current master contain a revert, but it is a revert of a rather old
commit (complete with merge conflict) so this does not look like a
hotfix on the reported problem.
So can you come up with some actually reproducible recipe and/or a
commit id that would be affected?
Thanks
--
David Kastrup