hello,
Francisco Vila wrote:
2010/5/27 William Bajzek :
My experience has been that getting the build system going on GNU/Linux
systems is, while not trivial, certainly much more reliable than on OS/X.
On OS/X, we're kind of on our own. And on Windows, it's even worse.
But I thought that th
Carl Sorensen writes:
> On 5/27/10 2:58 PM, "Benjamin Peterson" wrote:
>
>> Carl Sorensen byu.edu> writes:
>>> I saw the comment from David not as a suggestion to build an automated
>>> process for feeding the erroneous strings, but as a one-time testing
>>> suggestion. Hence my request for he
Hi James,
> my point is that it really isn't that hard to set up even for a complete
> beginner.
I've done Java programming in Eclipse with WebObjects Frameworks and WOLips --
the setup for that was "complicated" (i.e., tedious and time-consuming), but I
was able to accomplish it on three diff
On Fri, May 28, 2010 at 1:32 PM, Kieren MacMillan
wrote:
>
> I'm happy to continue with the VM install I've started... but Graham (the
> expert, AFAICT) is recommending that I wait.
To elaborate:
Given your background, attitude, and daily use of lilypond for your
composition job, you're an idea
Kieren,
Kieren MacMillan wrote:
I refuse to believe it's my incompetence alone that caused this problem. :-p
:-P
:)
I wasn't at all meaning to imply you were incompetent, but (and for the
benefit of others that may have been reading this thread) that some of
us had updated the documents
On 5/28/10 6:32 AM, "Kieren MacMillan"
wrote:
use a 1.5GB VM
>
> I wish someone had suggested a VM when I *first* started to set up the
> environment -- as Carl noted, by the time someone (Graham?) suggested a VM, I
> was already beyond frustrated with the huge number of hair-pulling hours I
Carl,
Carl Sorensen wrote:
"Simple" and "doc build" should not be used in the same sentence regarding
LilyPond, IMO. I think that the doc build is probably the most complicated
thing that a LilyPond setup will ever do.
From my own personal perspective (assuming I have the Lilybuntu installed)
On 5/28/10 6:32 AM, "Kieren MacMillan"
wrote:
> Hi James,
>
>> my point is that it really isn't that hard to set up even for a complete
>> beginner.
>
> I've done Java programming in Eclipse with WebObjects Frameworks and WOLips --
> the setup for that was "complicated" (i.e., tedious and ti
On Fri, May 28, 2010 at 2:46 PM, Carl Sorensen wrote:
>
> "Simple" and "doc build" should not be used in the same sentence regarding
> LilyPond, IMO. I think that the doc build is probably the most complicated
> thing that a LilyPond setup will ever do.
Agreed in a technical sense, but in a "com
On Fri, May 28, 2010 at 3:13 PM, James Lowe wrote:
> From my own personal perspective (assuming I have the Lilybuntu installed).
Heh, perfect example of the "well-intentioned but misleading" advice
that this mailing list is famous for! :)
> 1. Download lilygit.tcl - change permissions so I can
Hi all,
> My personal preference would be for you to be willing to risk some specified
> maximum time now (say, 2 hours), and agree to try once more when Graham can
> guarantee success if you can't get the install to work. I think that in less
> than 2 hours, you'd be up and running (although the
On 5/28/10 8:13 AM, "James Lowe" wrote:
> Carl,
>
> Carl Sorensen wrote:
>> "Simple" and "doc build" should not be used in the same sentence regarding
>> LilyPond, IMO. I think that the doc build is probably the most complicated
>> thing that a LilyPond setup will ever do.
>
> From my own
On Fri, May 28, 2010 at 09:18:36AM -0600, Carl Sorensen wrote:
>
> If your step 4:
>
> ./autogen.sh
>
> fails, then you may have a bunch of work to get the prerequisites installed.
>
> And if
>
> make doc
>
> fails, then you have a bunch of work to try to figure out what to do to make
> it w
2010/5/28 Kieren MacMillan :
> I've installed full LaTeX installations on several different machines and
> OSes; again, first time each time. In fact, I've done a number of fairly
> complex installations -- database servers, web servers, and so on -- and most
> have gone smoothly, where eventual
On Fri, May 28, 2010 at 06:45:56PM +0200, Francisco Vila wrote:
> Here, you are not comparing *installation* of well known, widespread
> things with *compiling* lilypond, are you?
oh, FFS...!
Look, our development environment sucks. Get over it.
Kieren has tried, twice, to get it working. He's
2010/5/15 Neil Puttock :
> Should be pretty simple to do, I'd imagine.
>
> I postponed pushing the fix for #305 since I wanted to incorporate
> some additional features (automatic breaking for \change Staff and
> manual directions), but I'd be happy to work on those features later
> to get this fi
Hi Francisco:
> Here, you are not comparing *installation* of well known,
> widespread things with *compiling* lilypond, are you?
To be clear:
1. I have installed many other build systems -- usually on my own (i.e.,
with only written/electronic documentation and web links, but no live
"ment
2010/5/28 Kieren MacMillan :
> I'm simply pointing out that the tools -- including my own computer, of
> course -- are more likely to blame than "user error"
I now understand.
Sorry again for my badly worded comment.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
2010/5/28 Graham Percival :
> Look, discussion is OVER.
Not before I apologize. God knows I was NOT trying to be insulting.
So, sorry if it sounded that way.
Du you really think I was laughing at him?
Furthermore, I lasted months before being able to make decent doc
patches, and several more mon
Hi Kieren,
I don't think we can remove the link between 'line-thickness and
underline offset, since it should scale based on staff-size. At small
staff-sizes, 'line-thickness gets progressively larger, which matches
the thicker underline with a slightly bigger gap.
What you could do instead is
On 5/28/10 2:29 PM, "n.putt...@gmail.com" wrote:
> Hi Kieren,
>
> I don't think we can remove the link between 'line-thickness and
> underline offset, since it should scale based on staff-size. At small
> staff-sizes, 'line-thickness gets progressively larger, which matches
> the thicker und
21 matches
Mail list logo
