Issue 2347 in lilypond: Patch: Improving \harmonicBy... functions
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2347 by m...@hohlart.de: Patch: Improving \harmonicBy... functions http://code.google.com/p/lilypond/issues/detail?id=2347 Improving \harmonicBy... functions These functions work now as expected for guitar music. We have dotted harmonics and mixed harmonic note heads. http://codereview.appspot.com/5695059 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #5 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I am pointing out that OSX has now been responsible for about a month of stable release delay. The people spending most of the time for fixing the problem have no way of testing it. Any useful feedback even for total blunders takes weeks to arrive, and arrives more by accident rather than release-related coordinated testing, testing that does not require more skills than actually using the respective platform. And that right before a major release. I think we owe the OSX users the following information in the release announcement for 2.16: a) since we don't have any actual users of MacOSX available for systematic testing and feedback, support for MacOSX is only provisional. If any component of it works, you are in luck. b) without anybody willing to engage in regular, timely and systematic testing, we have no option but considering MacOSX an unsupported platform. While we will package MacOSX versions for the near future, there is no way for us to know whether any part of them will actually work, and on what OSX versions. For that reason, it does not make sense to have our release schedule set back in case somebody actually happens to report a problem short before a release. Without anybody willing to do systematic testing and thus provide the most basic criterion for calling a system supported, any problem occuring only in relation with OSX will not be considered release-critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2348 by m...@hohlart.de: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348 Handling of open strings in tablature This patch creates a switch called ignoreOpenStrings. When set to #f (default), LilyPond handles open strings as usual. Setting ignoreOpenStrings to #t excludes open strings and forces the fret calculation routine to find a fretted position even for pitches equal to an open string. http://codereview.appspot.com/5695058 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Comment #18 on issue 2271 by colingh...@gmail.com: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 I've posted to the user list to solicit help with this. http://article.gmane.org/gmane.comp.gnu.lilypond.general/70160 I have an power-pc architecture iMac running 10.3.9 that my family use it on a daily basis. Email and word processing is fine but it is hopeless for web browsing because the browsers that can run on it do not support modern web page content. I stopped using it for Lilypond work three years ago. I'd be amazed if there are many technically savvy users are out there using Lilypond on Mac 10.4. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: Bug squad needs help to verify a critical bug on Mac OS X 10.4
- Original Message - From: Graham Percival gra...@percival-music.ca To: Colin Hall colingh...@gmail.com Cc: Phil Holmes em...@philholmes.net; Lilypond Bugs bug-lilypond@gnu.org Sent: Friday, February 24, 2012 12:01 AM Subject: Re: Fwd: Bug squad needs help to verify a critical bug on Mac OS X 10.4 On Thu, Feb 23, 2012 at 11:55:31PM +, Colin Hall wrote: I wondered if it was closed down pending resolution of the spam problem? Yes, I heard from the mailing list admins that it was down. No estimates on when it will be up again. I'll let Phil handle the actual bug issue -- and thanks for trying to get some action on it! - Graham Going by the lack of activity on .devel it looks like that's down, too. Looks like the approach you're taking on the OSX bug is exactly right - thanks for starting to progress this - hopefully it'll bring results when the mailing list is back up. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Comment #19 on issue 2271 by d...@gnu.org: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 It would be at least _one_ data point if LilyPond (and LilypondTool) worked on 10.3.9. If you consider upgrading to 10.4, be aware that it is common for newer versions to have larger resource requirements. If the system is in active use, that could become a nuisance if the 10.3.9 installation is not kept in parallel. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Updates: Labels: -Bounty Comment #20 on issue 2271 by d...@gnu.org: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 As I no longer have a Graham hour available, I cannot continue the offering of a continued support attempt in exchange for a bounty. Since the circumstances under which the $US25 offer for a bounty have been made don't seem to match the current situation either, I am removing the respective tag. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Updates: Status: Verified Comment #21 on issue 2271 by colingh...@gmail.com: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 James Worton reports that this issue is verified to work: http://article.gmane.org/gmane.comp.gnu.lilypond.general/70163 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Updates: Status: Fixed Blockedon: 2338 Comment #22 on issue 2271 by d...@gnu.org: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 I don't see that it makes sense to verify this as long as Issue 2338 is around, meaning that we will get yet another replacement of the OSX version anyway. I am re-marking this as Fixed as well as blocked on 2338. We will have to verify _if_ and _when_ the next OSX version gets produced. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Issue 2338: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 This issue is now blocking issue 2271. See http://code.google.com/p/lilypond/issues/detail?id=2271 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC
Updates: Status: Verified Labels: -Cant_verify Comment #23 on issue 2271 by gra...@percival-music.ca: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 I disagree. Issue 2338 refers the (now poorly-named) osx-universal version which is only for x86, while this refers specifically to the PPC version. I would consider them to be two different code bases, so bugs for each should be treated separately. We have confirmation that the PPC version works, so let this be Verified. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2349 by mts...@gmail.com: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349 Removes transparents in TabVoice and replaces with false stencil http://codereview.appspot.com/5694066 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_31 Comment #6 on issue 2336 by d...@gnu.org: Patch: Add layout changing command \layout-from for getting context defs from music http://code.google.com/p/lilypond/issues/detail?id=2336 Pushed a version changed along the suggested lines as dd7a75b0862bf05adec8033a1c4a15f225255101 to staging. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2322 in lilypond: Add layout-from function to documentation
Updates: Blockedon: -2336 Comment #3 on issue 2322 by d...@gnu.org: Add layout-from function to documentation http://code.google.com/p/lilypond/issues/detail?id=2322 The code is now submitted as issue 2336 together with a regtest. This would be a useful starting point for adding this into the user level documentation. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Issue 2336: Patch: Add layout changing command \layout-from for getting context defs from music http://code.google.com/p/lilypond/issues/detail?id=2336 This issue is no longer blocking issue 2322. See http://code.google.com/p/lilypond/issues/detail?id=2322 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Comment #1 on issue 2349 by mts...@gmail.com: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349#c1 Removes transparents in TabVoice and replaces with false stencil http://codereview.appspot.com/5694066 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Updates: Labels: Patch-needs_work Comment #2 on issue 2349 by d...@gnu.org: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349#c2 Patchy the autobot says: Full tablature is missing out on measure counter and dynamics. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2349 in lilypond: Patch: Removes transparents in TabVoice and replaces with false stencil
Comment #3 on issue 2349 by d...@gnu.org: Patch: Removes transparents in TabVoice and replaces with false stencil http://code.google.com/p/lilypond/issues/detail?id=2349 Oh, and a flag is missing as well. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Updates: Labels: Patch-needs_work Comment #1 on issue 2348 by d...@gnu.org: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348#c1 Patchy the autobot says: /usr/local/tmp/lilypond/issue5695058_2001.diff:15: trailing whitespace. /usr/local/tmp/lilypond/issue5695058_2001.diff:16: trailing whitespace. } /usr/local/tmp/lilypond/issue5695058_2001.diff:21: trailing whitespace. g, d 1 /usr/local/tmp/lilypond/issue5695058_2001.diff:23: trailing whitespace. g, d 1 warning: 4 lines add whitespace errors. Problem with issue 2348 Failed runner: nice make check -j3 See the log file log-2348-nice-make-check--j3.txt Log file no longer available, but my guess is the \version of 2.15.32 which does not correspond to the next release. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2347 in lilypond: Patch: Improving \harmonicBy... functions
Updates: Labels: Patch-review Comment #1 on issue 2347 by d...@gnu.org: Patch: Improving \harmonicBy... functions http://code.google.com/p/lilypond/issues/detail?id=2347#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2148 in lilypond: vertical skylines should use stencil integrals
Updates: Labels: Patch-review Comment #74 on issue 2148 by d...@gnu.org: vertical skylines should use stencil integrals http://code.google.com/p/lilypond/issues/detail?id=2148#c74 Patchy the autobot says: LGTM. stem-length-estimation now produces an overfull-page warning. Should be checked for accuracy. And of course the rotated stencil thingy again. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests.
Comment #9 on issue 1833 by n.putt...@gmail.com: Deprecate \fermataMarkup for full-bar rests. http://code.google.com/p/lilypond/issues/detail?id=1833 Hi Reinhold, I'll try to resurrect this next week. There's nothing wrong with it, just needs rebasing probably. I'll close this issue once I've sorted out git-cl and posted a new patch. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Comment #8 on issue 2336 by d...@gnu.org: Patch: Add layout changing
command \layout-from for getting context defs from music
http://code.google.com/p/lilypond/issues/detail?id=2336
Ok, I am not altogether happy. The regexp example with its
\midi { \layout-from { \tempo 4 = 80 } }
makes quite obvious that this is rather \context-defs-from or \output-from
even though it will most often be used as \layout { \layout-from ...
Its purpose is to adjust context-defs while in an output-def. Does anybody
have a better suggestion for its name? It's pushed to staging already, but
it would still be pretty painless to change its name. The name should
contain a hyphen (to prevent accidental use inside of music). It serves a
somewhat similar purpose as \settingsFrom (which is used inside of a single
context-def and actually could also make use of a hyphen: it is
less dangerous since it does not actively change variables in the current
module but just returns a context-def).
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Comment #9 on issue 2336 by d...@gnu.org: Patch: Add layout changing
command \layout-from for getting context defs from music
http://code.google.com/p/lilypond/issues/detail?id=2336
Ok, what do people say to the following:
a) rename settingsFrom to \context-like
b) rename \layout-from to \output-like
Then we may do things like
\midi {
\Score { \context-like { \tempo 4 = 80 } }
}
\layout {
\output-like { \accidentalStyle modern }
}
Is that better than xxx-from ?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Ok, what do people say to the following:
a) rename settingsFrom to \context-like
b) rename \layout-from to \output-like
Then we may do things like
\midi {
\Score { \context-like { \tempo 4 = 80 } }
}
\layout {
\output-like { \accidentalStyle modern }
}
Is that better than xxx-from ?
I totally agree.
It is an evidence that \context-like deals with contexts and,
from a non English native user point of view, I know that layout deals
with printable; therefore I would get confused to be allowed to mention
\layout-from in a midi block...
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #7 on issue 2338 by carl.d.s...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I would agree with this description if it applied to OSX 10.4. We have users regularly using OSX 10.5 through 10.7. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2347 in lilypond: Patch: Improving \harmonicBy... functions
Comment #2 on issue 2347 by m...@hohlart.de: Patch: Improving \harmonicBy... functions http://code.google.com/p/lilypond/issues/detail?id=2347#c2 Improving \harmonicBy... functions These functions work now as expected for guitar music. We have dotted harmonics and mixed harmonic note heads. http://codereview.appspot.com/5695059 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Comment #10 on issue 2336 by carl.d.s...@gmail.com: Patch: Add layout
changing command \layout-from for getting context defs from music
http://code.google.com/p/lilypond/issues/detail?id=2336
I think I would prefer
\layout-properties-from
\context-properties-from
It's more typing, but I think it's clearer.
\midi {
\Score {
\context-properties-from { \tempo 4 = 80}
}
}
\layout {
\layout-properties-from { \accidentalStyle modern }
}
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Comment #12 on issue 2336 by d...@gnu.org: Patch: Add layout changing
command \layout-from for getting context defs from music
http://code.google.com/p/lilypond/issues/detail?id=2336
I am actually starting to lean towards not bothering about the naming at
all. Instead, when music is encountered in a context def or output def,
just call a Scheme function for harvesting it, period.
That would make \midi { \tempo 4 = 80 } work again as expected. The only
disadvantage is that you can't specify what to do with layout properties
for Bottom then, but in that case one could still use
\layout { \with-Bottom #'TabVoice \FullTabulature } or so.
Sure, it is not really all that conceptually clean, but one can throw a
warning for any kind of music not belonging in there.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Labels: Patch-new Comment #1 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346#c1 CG: Use latest convert-ly for LSR updates (fix 2346) Suggested by Thomas Morley: Use convert-ly from latest development release for LSR updates http://codereview.appspot.com/5696069 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc addition
On Fri, Feb 24, 2012 at 1:23 AM, Colin Hall colingh...@gmail.com wrote: On Thu, Feb 23, 2012 at 11:18:43PM +0100, Thomas Morley wrote: Make sure you use convert-ly from the latest available release to gain all advantages from the latest converting-rules-updates. Thanks very much for the documentation suggestion, Thomas. I have created a new issue tracker for it, see Issue 2346 Rietveld issue added http://codereview.appspot.com/5696069/ thanks, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2350 in lilypond: Patch: Simplify font building.
Comment #2 on issue 2350 by lemzw...@gmail.com: Patch: Simplify font building. http://code.google.com/p/lilypond/issues/detail?id=2350 .enc files are indeed not used anywhere. You would need them for TeX if you were going to access the Type1 fonts directly. We don't support this, so everything's OK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
