[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
From:       Łukasz_Czerwiński <milimetr88 () gmail ! com>
Date:       2012-04-28 22:22:00
Message-ID: CAMELQsAr94GcqvPtdGaskAP22mpjQa3j_8UW1q4_QoMdtYn9Ow () mail ! gmail ! com
[Download RAW message or body]

Could you please change the mails' subject? :) I've started a thread: Lilyp=
ond
patchy and other Lilypond problems for this discussion. Could you move
there?

=C5=81ukasz


On 27 April 2012 19:43, Phil Holmes <mail@philholmes.net> wrote:

> ----- Original Message ----- From: "James" <pkx166h@gmail.com>
> To: "Phil Holmes" <mail@philholmes.net>
> Cc: <mike@apollinemike.com>; <k-ohara5a5a@oco.net>; <dak@gnu.org>; <
> lilypond-devel@gnu.org>
> Sent: Friday, April 27, 2012 5:58 PM
>
> Subject: Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue
> 6109046)
>
>
>  You then need to tick a box more or two to enable that stuff in VBox
>> or KVM. Remember though that LilyDev is 32bit so if you use KVM you
>> must not go over 4096 for your RAM (even if you have more) else, I
>> found, it will just default to 128mb! Vbox is a bit more smart, but
>> you still cannot address more than 4GB of RAM in a 64bit VBox install
>> using LilyDev.
>>
>>
> That said, I've never seen Lily builds take much RAM, so 4 GByte is
> normally plenty.
>
> --
> Phil Holmes
>
> ______________________________**_________________
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/**listinfo/lilypond-devel<https://lists.gnu=
.org/mailman/listinfo/lilypond-devel>
>

[Attachment #3 (text/html)]

Could you please change the mails&#39; subject? :) I&#39;ve started a thread:  <h1 \
class="ha" style><span id=":2ma" class="hP" style="padding-right:10px">Lilypond \
patchy and other Lilypond problems</span></h1>  for this discussion. Could you move \
there?<div>

<br></div><div>Ɓukasz</div><div><br><br><div class="gmail_quote">On 27 April 2012 \
19:43, Phil Holmes <span dir="ltr">&lt;<a href="mailto:mail@philholmes.net" \
target="_blank">mail@philholmes.net</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">----- Original Message ----- From: &quot;James&quot; &lt;<a \
href="mailto:pkx166h@gmail.com" target="_blank">pkx166h@gmail.com</a>&gt;<br>



To: &quot;Phil Holmes&quot; &lt;<a href="mailto:mail@philholmes.net" \
                target="_blank">mail@philholmes.net</a>&gt;<br>
Cc: &lt;<a href="mailto:mike@apollinemike.com" \
target="_blank">mike@apollinemike.com</a>&gt;; &lt;<a \
href="mailto:k-ohara5a5a@oco.net" target="_blank">k-ohara5a5a@oco.net</a>&gt;; &lt;<a \
href="mailto:dak@gnu.org" target="_blank">dak@gnu.org</a>&gt;; &lt;<a \
href="mailto:lilypond-devel@gnu.org" \
target="_blank">lilypond-devel@gnu.org</a>&gt;<br>



Sent: Friday, April 27, 2012 5:58 PM<div><br>
Subject: Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)<br>
<br>
<br>
</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> You then need to tick a box more or two to enable that \
stuff in VBox<br> or KVM. Remember though that LilyDev is 32bit so if you use KVM \
you<br> must not go over 4096 for your RAM (even if you have more) else, I<br>
found, it will just default to 128mb! Vbox is a bit more smart, but<br>
you still cannot address more than 4GB of RAM in a 64bit VBox install<br>
using LilyDev.<br>
<br>
</blockquote>
<br></div>
That said, I&#39;ve never seen Lily builds take much RAM, so 4 GByte is normally \
plenty.<br> <br>
--<br>
Phil Holmes <br><div><div>
<br>
______________________________<u></u>_________________<br>
lilypond-devel mailing list<br>
<a href="mailto:lilypond-devel@gnu.org" \
target="_blank">lilypond-devel@gnu.org</a><br> <a \
href="https://lists.gnu.org/mailman/listinfo/lilypond-devel" \
target="_blank">https://lists.gnu.org/mailman/<u></u>listinfo/lilypond-devel</a><br> \
</div></div></blockquote></div><br> </div>



[prev in list] [next in list] [prev in thread] [next in thread]