Err--- that would be a chortle yes?
--hsm
On Wed, Dec 2, 2009 at 11:07 PM, James Bailey
wrote:
>
> On 03.12.2009, at 02:33, Hugh Myers wrote:
>
>> Graham,
>> …
>> I do know that you've already discovered the value of enlisting your
>> user community, having said that, I think you might find them
Graham,
I wonder if it not so much a matter of prioritization as it is a
matter of intimidation. That is to say that most people seeing the
process from the out side find it a bit scary provoking a "oh I
couldn't do that kind of feeling." I know that in my own experience
with users turned loose o
On Wed, Dec 02, 2009 at 05:33:55AM -0700, Hugh Myers wrote:
> Hadn't realized that a policy of
> collateral damage was allowed. Given your approach to testing (and
> your experience) this should work as well as more conservative
> approaches.
As Alexander wrote, it's not so much that collateral da
Hugh Myers wrote:
Thanks for the tip on
2.odd versus 2.stable as well. Hadn't realized that a policy of
collateral damage was allowed.
It isn't allowed, AFAICS, but can you prognose if you do collateral
damage every time you write a patch?
The testing is not as thorough as for stable releases.
Clearly it is better that Graham continue as he has since the benefits
greatly out weight any negatives. And most beginners eventually form
their inquires to fit the forum in question. Thanks for the tip on
2.odd versus 2.stable as well. Hadn't realized that a policy of
collateral damage was allowe
Hugh Myers wrote:
Second point taken. I hope you realize that 2.13 has bug fixes for
2.12--- yes? Without those, there is no project...
Yes it has (as well as enhancements), but during developement - as is an
unstable release - they are allowed to break other things to a certain
degree. (Very
Also went away after an amendment in bar 22! Not sure what is going on
here, but it is at least fun to watch. My feeling is that once every
thing is correct, some of these things will go away.
--hsm
p.s. I'll save the \paper code for worst case, thanks Marc...
On Wed, Dec 2, 2009 at 12:58 AM, Mar
Hugh Myers schrieb:
Since the project can't be done in 2.12, what do you suggest?
I inserted a paper block after the \header:
\paper {
indent = 0
between-system-space = 2\cm
between-system-padding = #5
ragged-bottom=##f
ragged-last-bottom=##f
}
You can play with the numbers, but at lea
Ah! That should be easy enough to work with--- I'll see what I can come up with.
--hsm
On Wed, Dec 2, 2009 at 12:43 AM, Marc Hohl wrote:
> Hugh Myers schrieb:
>>
>> Here is the shortest template I use:
>>
>> \version "2.13.7"
>> upper = {
>> b c d
>> }
>>
>
> Use
>
> upper = {
> \repeat unfold
Since the project can't be done in 2.12, what do you suggest?
--hsm
On Wed, Dec 2, 2009 at 12:41 AM, Marc Hohl wrote:
> Hugh Myers schrieb:
>>
>> Second point taken. I hope you realize that 2.13 has bug fixes for
>> 2.12--- yes?
>
> Yes, but 2.13.x is work in progress. There is a new layout engi
Hugh Myers schrieb:
Here is the shortest template I use:
\version "2.13.7"
upper = {
b c d
}
Use
upper = {
\repeat unfold 100 {
b c d
}
}
lower = {
< gis, d e, >2.
}
and
lower = {
\repeat unfold 100 {
< gis, d e, >.
}
}
respectively.
Marc
{
\time 3/4
<<
\new St
Hugh Myers schrieb:
Second point taken. I hope you realize that 2.13 has bug fixes for
2.12--- yes?
Yes, but 2.13.x is work in progress. There is a new layout engine
which is still under improvement, as far as I know.
So the layout may change considerably between 2.13.x and 2.13.y.
2.12.x is s
Here is the shortest template I use:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar ""
\override Score.BarNumber #'break-visibility = #'#(#
Second point taken. I hope you realize that 2.13 has bug fixes for
2.12--- yes? Without those, there is no project... I don't suppose you
took a look? Did you notice that in included tablature? If you had,
then you would perhaps have sent me a different 'Most spacing bugs can
be reproduced...' Also
On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
> Pardon the length of the piece of code, but clearly demonstrates the
> problem where as other pieces don't (got to be a page long for
> instance...):
> \version "2.13.7"
I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
r
Pardon the length of the piece of code, but clearly demonstrates the
problem where as other pieces don't (got to be a page long for
instance...):
%
% malaguena.ly -- q&d testbed for mixed notation score and tab.
%
\version "2.13.7"
\header {
title = "Malaguena"
subtitle = "none"
composer = "
16 matches
Mail list logo