Am 16. Oktober 2018 20:13:29 MESZ schrieb Alex Roitman :
>Thank you Jan-Peter! This looks really promising, and I’d love to
>contribute.
>
>I’m only vaguely familiar with Scheme so I’ll probably take a bit of
>time to get my hands dirty with that. Would it be OK to bug you with
>questions every
Am 17.10.2018 um 08:55 schrieb Jan-Peter Voigt:
Hi Kieren,
Am 16.10.18 um 16:54 schrieb Kieren MacMillan:
Hi Jan-Peter,
2. I wrote a rudimentary engraver-based solution last year which is
waiting for clean-up and completion to support MEI, MusicXML
The code in the project is able to export
Am 20.11.18 um 18:05 schrieb Werner LEMBERG:
It seems that
http://github.com/janneke/gub
is no longer available. Jan, is this intentional?
Werner
https://github.com/janneke/ suggests that "janneke" joined Github on Oct
12 2018 and doesn't have any repositories.
_
Am 22.11.18 um 00:21 schrieb Werner LEMBERG:
Please give her a warm welcome!
Warm welcome :-)
I suggest to start with setting up a build environment (on GNU/Linux
box or in a virtual GNU/Linux machine) so that changes to C++ code,
Scheme code, and documentation can be easily done.
Janek ha
Hello Basia (and Janek),
Am 21.11.18 um 23:20 schrieb Janek Warchoł:
Hi everyone,
I'd like to introduce Basia Mroczek, who's joining our team for several
months. Basia is a graduate (is that the correct english term?) of
Mathematics at the University of Warsaw (so, cream of the crop!) who'd lik
code, and documentation can be easily done.
Yeah, we're working on that. :)
czw., 22 lis 2018 o 00:29 Urs Liska <mailto:li...@openlilylib.org>> napisał(a):
Janek has created a set of very useful scripts.
Whoah, I almost forgot them :p
So, you're still using them?
Unfortuna
Am 23.11.18 um 19:29 schrieb Benkő Pál:
Ubuntu 16.04 should be OK, I use that too. Though it's a lng time
I tried a make check.
Ubuntu 16.04 still has guile-1.8 in its repositories, so on that system
it should be smooth to get things to run.
What I did back then was go through all the
Hello Étienne,
I too think this would be a very promising proposal, and if it would get
closer to an actual application I will surely have some more thoughts on
it too.
Right now it is of course premature to discuss because not even the
*organization* application period has started. So as ev
Am 04.12.18 um 11:56 schrieb Andrew Bernard:
Hi Étienne ,
The default is PDF, not PNG.
I applaud your desire to improve the SVG output, but do get the premise
right. Thanks!
Étienne has already clarified this. I assume it's that with "this
application" he was not refering to LilyPond as a
significantly smaller.
Let's say if I want to do something at GSoC this year with LilyPond, who
should I get in touch with?
Urs Liska seems the most involved in Google Summer of Code efforts.
Perhaps this email address:
With the lilypond-devel mailing list you have in fact found the best
pl
Hi Knut,
thank you for working on this, and - like Karlin - I wouldn't have
tested without your straightforward recipe. But before going to bed I
logged off, then logged in again in a terminal-only session and started
the process.
Am 28.01.19 um 13:53 schrieb Knut Petersen:
Hi everybody!
I
Am 29.01.19 um 07:41 schrieb Urs Liska:
The overall end doesn't report a failure, but the last "rule" shows
some problems,
I should have mentioned this was the "nsis rule"
___
lilypond-devel mailing list
lil
Am 29.01.19 um 08:14 schrieb Werner LEMBERG:
The overall end doesn't report a failure, but the last "rule" shows
some problems,
I should have mentioned this was the "nsis rule"
If you reach this point you can be rather sure that everything was
fine – at least for your build system, since it wa
Am 29.01.19 um 08:32 schrieb Werner LEMBERG:
If we get more success reports, the resulting packages should be
uploaded so that other people not running gub can test them.
Developers can then have a look how to add support for 64bit
binaries on MacOS and Windows. Especially the former is rather
Hi Knut,
Am 29.01.19 um 10:02 schrieb Knut Petersen:
Hi Urs!
So what can I do to check whether make lilypond succeeded or failed?
The last lines of the terminal output will look like:
make -f lilypond.make update-versions
To upload, run:
make lilypond-upload LILYPOND_BRA
Hi Knut,
as said I ran the GUB build on my Debian server as well.
Am 29.01.19 um 08:11 schrieb Knut Petersen:
On 29.01.19 00:53, Karlin High wrote:
*** Failed target: darwin-ppc::odcctools
gub.make:63: recipe for target 'packages' failed
make[1]: *** [packages] Error 1
make[1]: Leaving directo
Am 29.01.19 um 14:28 schrieb Knut Petersen:
On 29.01.19 11:56, Thomas Morley wrote:
Am Di., 29. Jan. 2019 um 00:53 Uhr schrieb Karlin High:
On 1/28/2019 6:53 AM, Knut Petersen wrote:
Please report success / fails with os / version / cpu info.
I really like the simple instructions you posted
Am 29. Januar 2019 19:47:07 MEZ schrieb Michael Hendry
:
>> On 29 Jan 2019, at 09:19, Knut Petersen
>wrote:
>>
>> Hi everybody
>>
>> Urs Liska provides installers for branch master of lilypond,
>generated by an updated version of our build system
Am 29.01.19 um 14:58 schrieb Knut Petersen:
On 29.01.19 14:30, Urs Liska wrote:
Looks like 64-bit Ubuntu, like my main machine. With an earlier
gub-version I had similiar problem, because of missing 32-bit
libraries.
I got further after installing:
lib32ncurses5
lib32z1
I suspect that
Am 30.01.19 um 12:14 schrieb Knut Petersen:
Hi everybody!
Thanks for testing.
Here is a summary of the current status:
openSuSE Tumbleweed: Gub succeeds, but it is necessary to install
gcc-7.
openSuSE Leaf 42.3: Gub succeeds.
Ubuntu 18.04[.1]: Gub succeeds. But. libc6-dev-i386
ls::guile to build with Fedora 29 plus GCC
>7?
>> On my system with a similar setup (Fedora 29 + GCC 7.4.0 installed
>> locally and configured with Ccache), I get the same error as with
>> system's GCC (8.2.1), error you've already reported.
>>
>> Best
&g
Hi Daniel,
Am 27.02.19 um 15:00 schrieb Daniel Benjamin Miller:
Hi all:
I'm an undergraduate student at McGill University. As I've personally
wanted to tweak LilyPond to improve the stylistic output of my scores,
I was hoping to do some work on LilyPond this summer, perhaps through
GNU's inv
Am 16. März 2019 20:20:15 MEZ schrieb Valentin Villenave
:
>On 3/16/19, Valentin Petzel wrote:
>> Currently the anchor points are set both over or both under the
>starting /
>> ending note, depending on the slur’s direction. For the S-shape we
>would
>> need
>> the control points to differ in d
Hi Tsz Kiu Pang (which of these names would you like to be called, or
should I use all of them like I did?)
Am 21.03.19 um 06:58 schrieb Tsz Kiu Pang:
Hi all,
I am writing to express my interest in working on LilyPond as part of GNU
in the Google Summer of Code.
I was just looking at the proj
Hi Tzk Kiu,
Am 21.03.19 um 13:06 schrieb Tsz Kiu Pang:
Hi Urs,
Thank you for your reply, and thank you so much for asking about my name.
On Thu, 21 Mar 2019 at 17:58, Urs Liska <mailto:li...@openlilylib.org>> wrote:
Hi Tsz Kiu Pang (which of these names would you like to be c
This is directed at the other devs, to (please) join the conversation
Am 01.04.19 um 08:30 schrieb Tsz Kiu Pang:
I just have some concerns.
Sorry I might have overestimated myself in the past week, but I
realised I might not be able to commit for 30+ hours per week
during May s
Hi Tsz Kiu,
Am 03.04.19 um 13:48 schrieb Tsz Kiu Pang:
Hi Urs,
Whether or not I'll be suitable to participate in GSoC, I am keen to
dive into openlilylib.
That would be great!
On Thu, 21 Mar 2019 at 17:58, Urs Liska <mailto:li...@openlilylib.org>> wrote:
What you
Am 06.04.19 um 01:49 schrieb Kieren MacMillan:
Hi Werner,
Would this be of interest for LilyPond?
https://developers.google.com/season-of-docs/docs/project-ideas
It would be *very* valuable for OpenLilyLib… =)
Indeed, but I don't think this program is suitable for that ...
If I've underst
Am 18.05.19 um 05:53 schrieb Carl Sorensen:
1.8
It's actually 1.8.8 IIRC
Urs
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 04.06.19 um 00:13 schrieb thomasmorle...@gmail.com:
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm
File scm/color.scm (right):
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm#newcode678
scm/color.scm:678: (define css-color-list
Is there anythin
Am 04.06.19 um 10:53 schrieb Urs Liska:
Am 04.06.19 um 00:13 schrieb thomasmorle...@gmail.com:
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm
File scm/color.scm (right):
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm#newcode678
scm/color.scm
Thank you for doing so.
The thing is (as buried in a comment somewhere), these regular reminders served
as an incentive for me not to forget that I wanted to push this only after
documenting the new feature...
___
lilypond-devel mailing list
lilypond-
I'm not sure if this is actually a *development* request or if it could also be
solved at the "user" level.
As Werner showed in https://github.com/jperon/lyluatex/issues/268
(https://github.com/jperon/lyluatex/issues/268) there is an issue with the
output of scores compiled with `lilypond-book-
30. Juli 2019 11:16, "David Kastrup" schrieb:
> "Urs Liska" writes:
>
>> I'm not sure if this is actually a *development* request or if it
>> could also be solved at the "user" level.
>>
>> As Werner showed in https://gi
Hi Kim,
thank you for the suggestion.
4. August 2019 16:14, "hs kim" schrieb:
> Hi.
> I was making "la campanella". There was many subdivide beams but it was so
> confused that I can't make it anymore. That's why I decided to change the
> way subdivide beams are written.
>
> In the stable bran
Hi Werner,
thank you for that!
I can't comment on it because I don't know much about Schenker graphs. But I
could right away use it ;-)
https://github.com/frescobaldi/frescobaldi/pull/1173#issuecomment-531884243
(actually this was something I had been hoping for).
Best
Urs
16. September 2019
Am 20. September 2019 02:23:58 MESZ schrieb Carl Sorensen :
>We are stuck for release because GUB is not working properly. Until we
>get GUB to work properly, we cannot make a release.
>
>As far as I know now, the answer is in fact indefinite.
But is that the actual roadblock for the *2.20* rel
Am 21. September 2019 04:09:36 MESZ schrieb Andrew Bernard
:
>So let me get this straight.
>
>It's not the case that GUB is completely broken. We can still build
>releases.
>
>DK is working steadily to cherry pick items for 2.20.
>
>Python 2 to Python 3 is a major issue.
>
>So, I offered to do
Am 21. September 2019 19:09:55 MESZ schrieb David Kastrup :
>Werner LEMBERG writes:
>
>> Here's an updated version of the Stockhausen example, with a lot of
>> added comments to the source code.
>>
>> I've also attached an image of rendering the old code (as present in
>> the git) with a lilypon
Hi Martin,
23. September 2019 11:17, "Martin Tarenskeen" schrieb:
> Hi,
>
> This has been discussed here before but https://pythonclock.org made me
> wonder in which direction LilyPond and Frescobaldi are currently going.
Well, if you're wondering about the direction then you might just read
Hi Werner,
thanks for working on this.
I have the impression it would be nice to add at least one example with an
alternative notation font to the example page. Here is the list of freely
available fonts:
https://github.com/openlilylib-resources/lilypond-notation-fonts/tree/master/fonts
(note
27. September 2019 08:55, "Urs Liska" schrieb:
> Hi Werner,
>
> thanks for working on this.
>
> I have the impression it would be nice to add at least one example with an
> alternative notation
> font to the example page. Here is the list of freely availa
Am 12. November 2019 10:50:45 MEZ schrieb David Kastrup :
>Werner LEMBERG writes:
>
>>>> This package is written by Urs Liska , who is
>>>> quite busy these days. In case you have experience with Python 2
>>>> to 3 conversion, please help produce
Hi David,
I feel responsible for this because I know where this is coming from ;-)
You can send me the patch. However, it's a long time since I uploaded
anything, so I'm not sure my set-up still works. But I'll try.
Best
Urs
Am 15.11.19 um 04:10 schrieb David Nalesnik:
Hi all,
I have a pa
Am 15. November 2019 14:35:26 MEZ schrieb David Nalesnik
:
>On Fri, Nov 15, 2019 at 12:33 AM Urs Liska
>wrote:
>>
>> Hi David,
>>
>> I feel responsible for this because I know where this is coming from
>;-)
>
>Hah! :) (Seriously, though, this is som
Hi Jan-Peter,
that sounds like a very nice idea.
However, I'm so involved in the conference already (along with my other
duties which are quite overwhelming right now) that I can't commit to
that beyond maybe occasional commenting or helping out with some
lyluatex syntax/options.
From what
Any LilyPond dev who does have a Facebook account might have a look at
this interesting, although somewhat sad, discussion. I think it gives a
clear picture of how our current state of development is perceived by users:
https://www.facebook.com/groups/gnulilypond/permalink/10157762793383529/
U
Am 16.12.19 um 10:18 schrieb Urs Liska:
* For integration in LilyPond the functionality should be wrapped into
a single file that can be included. Including the file should
automatically activate the functionality.
Maybe there should be a second includable file that does *not
4. Januar 2020 12:34, "Malte Meyn" schrieb:
> Am 04.01.20 um 12:29 schrieb Malte Meyn:
>
>> But that brings me to another question: Shouldn’t we add the \dynamic >
>> command from openlilylib to
>> vanilla LilyPond? This would allow users to > have “p dolce”, “più f” and
>> ‘exotic’ dynamics l
Am 7. Januar 2020 23:53:42 MEZ schrieb Andrew Bernard
:
>Hi Malte,
>
>\shapeII is a function I use heavily - heavily - in all my work. It's
>indispensable for me at least. I'm very familiar with OpenLilyLib, and
>contribute a bit to it, so it's not an issue for me, but that's a
>function that r
Hi Kieren,
Am Samstag, den 11.01.2020, 11:03 -0500 schrieb Kieren MacMillan:
> Hello colleagues!
>
> I just had a wonderful video-chat with Jan-Peter, as part of the
> preparations for my session “The Edition-Engraver: The benefits and
> limitations of tweaking LilyPond scores” at next week’s
> [
Am Montag, den 13.01.2020, 15:42 -0500 schrieb Kieren MacMillan:
> Hello future Salzburg-ers!
>
> Knowing the way my life works, and the fact that I’ll be in Salzburg
> for four days without the normal distractions (family, etc.), and at
> hand will be a rather wonderful collection of brains and f
Am Sonntag, den 19.01.2020, 07:20 +0100 schrieb Werner LEMBERG:
> > While that may be true, there are already GNU projects using GitHub
> > as their host, for example gnucash and gnuradio.
>
> Gnucash uses github as a mirror only, see
>
> https://wiki.gnucash.org/wiki/Git#code.gnucash.org
>
>
Am Sonntag, den 19.01.2020, 20:31 + schrieb Erlend Aasland:
> True. But, there are GitHub alternatives that are free, for example
> Gitea.
Yes, but self-hosting a Git repository software (well, I have a Gitea
instance on my server) is an involved thing, and I don't think it's
reasonable to exp
.
>
>contributions in GitHub are usually stored on a branch + fork owned by
>the contributor, e.g.
>
> https://github.com/mikesol/lilypond/
>
>branch code_of_conduct.
I think that needs clarification.
Forks are "usually" used by people without push access to a repository. People
*with* push a
Hi all,
how/where is the file searchign with LilyPond's search path is
implemented?
If I write
\include "a/relative/path"
the given path is searched for relative to all search paths known to
LilyPond.
Is there a way to do the same in Scheme, say
(file-visible-to-lilypond "a/relative/path")
Hi,
one of the results of yesterday's developer meeting in Salzburg
[someone™ should provide a more concise summary than the notes in the
GoogleDoc] was that I should go forward "integrating openLilyLib" as
LilyPond's official extension mechanism.
I spent my travel back home reading through the c
I'll have a look ASAP:
Urs
>
> On Mon, Jan 20, 2020 at 9:22 AM Urs Liska
> wrote:
> > Hi all,
> >
> > how/where is the file searchign with LilyPond's search path is
> > implemented?
> >
> > If I write
> > \include "a/relati
Am Montag, den 20.01.2020, 10:27 +0100 schrieb Urs Liska:
> * A core extension library shipping with LilyPond will be initiated.
> Extensions that are considered core functionality (prime
> candidates:
> edition-engraver, stylesheets) will eventually be moved here from
>
Am Montag, den 20.01.2020, 16:53 +0100 schrieb David Kastrup:
> David Kastrup writes:
>
> > Werner LEMBERG writes:
> >
> > > > > Han-Wen has recently pushed a bunch of changes directly to
> > > > > Rietveld, most of them quite uncontroversial. I assume that
> > > > > this
> > > > > is as good
Am Montag, den 20.01.2020, 14:14 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Montag, den 20.01.2020, 10:27 +0100 schrieb Urs Liska:
> > > * A core extension library shipping with LilyPond will be
> > > initiated.
> > > Extensions that a
Am Montag, den 20.01.2020, 23:45 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > OK. The *current* behaviour of oll-core is:
> >
> > * loaded packages and modules (let's for now keep the existing
> > names)
> > are accounted for in an alist.
Am Dienstag, den 21.01.2020, 03:56 -0800 schrieb lemzwerg--- via
Discussions on LilyPond development:
> Very nice, thanks!
>
> https://codereview.appspot.com/571380043/
>
I've only looked at it cursorily, but I think this is really a step in
the right direction (even if it may feel like the drop
We have discussed options already on a conceptual level as "package
options", but technically it should be dealt with separately.
Options are not functionally required for the package loading to work,
but they are an integral part of the functionality, and I have found
that their availability has
Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > Ok. One thing to think about is that we want package files to be
> > contributed by "ordinary" users. But something like
> >
> > \exportSymbols transposeSequence,instrumentGroup,scratchMyBack
&g
Am Mittwoch, den 22.01.2020, 11:06 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > > > Ok. One thing to think about is that we want package files to
> > > > be
> > > > cont
Am Mittwoch, den 22.01.2020, 20:28 + schrieb Carl Sorensen:
>
> On 1/22/20, 1:21 PM, "lilypond-devel on behalf of David Kastrup" <
> lilypond-devel-bounces+c_sorensen=byu@gnu.org on behalf of
> d...@gnu.org> wrote:
>
> Han-Wen Nienhuys writes:
>
> > On Wed, Jan 22, 2020 at
Am Mittwoch, den 22.01.2020, 11:43 +0100 schrieb Urs Liska:
> Am Mittwoch, den 22.01.2020, 11:06 +0100 schrieb David Kastrup:
> > Urs Liska writes:
> >
> > > Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > > > > Ok. One thing to th
Am Freitag, den 24.01.2020, 11:41 +0100 schrieb Han-Wen Nienhuys:
> On Fri, Jan 24, 2020 at 11:28 AM David Kastrup wrote:
>
> > Han-Wen Nienhuys writes:
> >
> > > Thanks for keeping track of this.
> > >
> > > Can you confirm my countdown patches will get pushed without any
> > > of my
> > > in
Am 25. Januar 2020 08:36:08 MEZ schrieb Han-Wen Nienhuys :
>Looks like a bug.
What is "french beaming" supposed to do/be?
>
>On Sat, Jan 25, 2020 at 8:12 AM Werner LEMBERG wrote:
>>
>>
>> Before adding it to the bug tracker I want to check this group's
>> knowledge whether there is a reason t
Am 25. Januar 2020 08:56:44 MEZ schrieb Werner LEMBERG :
>
>> What is "french beaming" supposed to do/be?
>
>No stems within the beam.
Ah, yes. Sorry for forgetting that...
>
>
>Werner
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
I didn't have time to really think about much (about LilyPond) the past
week, just enjoyed seeing so much constructive discussion.
I think the first thing I'd like to go for with the package/extension
mechanism is storing and handling (package) options.
There are three use cases which are differe
Am Dienstag, den 28.01.2020, 00:34 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > I didn't have time to really think about much (about LilyPond) the
> > past
> > week, just enjoyed seeing so much constructive discussion.
> >
> > I think th
Am Dienstag, den 28.01.2020, 09:26 +0100 schrieb Han-Wen Nienhuys:
> On Mon, Jan 27, 2020 at 11:39 PM Urs Liska
> wrote:
> > I didn't have time to really think about much (about LilyPond) the
> > past
> > week, just enjoyed seeing so much constructive discussion.
>
Am 28. Januar 2020 14:48:54 MEZ schrieb David Kastrup :
>Han-Wen Nienhuys writes:
>
>> On Mon, Jan 27, 2020 at 11:39 PM Urs Liska
>wrote:
>>>
>>> I didn't have time to really think about much (about LilyPond) the
>past
>>> week, j
One final question before I start working on some package code
proposal:
All the basic Scheme files are loaded in lily.scm with
(for-each ly:load init-scheme-files)
What does this do internally? I.e. how is the visibility handled of
definitions/bindings from names in files loaded with ly:load
Am Mittwoch, den 29.01.2020, 07:01 -0800 schrieb d...@gnu.org:
> On 2020/01/29 12:20:10, mail5 wrote:
> > Unfortunately I haven't set up a build system on my new computer
> > yet,
> so this
> > patch is not tested locally at all, so I'm humbly waiting for the
> automated
> > tests to succeed or fai
Am Donnerstag, den 30.01.2020, 09:50 +0100 schrieb Han-Wen Nienhuys:
> On Tue, Jan 28, 2020 at 2:48 PM David Kastrup wrote:
>
> > > I think we should aim to avoid textual inclusion as a mechanism
> > > that
> > > powers packaging.
> >
> > At the implementation side, "textual inclusion" will be w
Am Freitag, den 31.01.2020, 18:38 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Mittwoch, den 29.01.2020, 07:01 -0800 schrieb d...@gnu.org:
> > > On 2020/01/29 12:20:10, mail5 wrote:
> > > > Unfortunately I haven't set up a build system
Hi all,
I wanted to get a better understanding from my impression of the
significant increase in traffic on lilypond-devel.
For this I did some statistics on James' "PATCHES - Countdown"
messages. Since patches are counted multiple times while flowing
through the process I think the only relevant
Am 5. Februar 2020 20:08:28 MEZ schrieb nine.fierce.ball...@gmail.com:
>On 2020/02/05 18:17:25, c_sorensen wrote:
>> I recognize that Mike Solomon has a different opinion. I mean no
>disrespect to
>> Mike, Janek, Han-Wen, or any other member of the LilyPond team. I
>highly value
>> the team sp
Am Mittwoch, den 05.02.2020, 21:21 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am 5. Februar 2020 20:08:28 MEZ schrieb
> > nine.fierce.ball...@gmail.com:
> > > On 2020/02/05 18:17:25, c_sorensen wrote:
> > > > I recognize that Mike Solomon has
Am Mittwoch, den 05.02.2020, 22:26 -0500 schrieb Kieren MacMillan:
> Hi Graham,
>
> > Oh, that would definitely be a good idea!
>
> Okay, then! I’ll start with your suggestion to [paraphrasing:]
> "summarize the jobs described in the CG", and prepare a skeleton
> document where each entry is like
> I'm not top posting.
In the mentioned chapter 4.5.3 of the LM the music example (LilyPond 2.13.27)
there is an ugly problem that shouldn't be there - especially not on this page.
I'm talking about the right hand phrasingSlur spanning from the first c'' to the
last g'. Which crosses the notes of
On Tue, 19 Mar 2013 19:38:10 -0400
Kieren MacMillan wrote:
> Hi Shane,
>
> > one would think that might cause more difficult
> > programming necessitating the keeping tracking of various R values
> > through out the piece as defined by a time signature as opposed to us
> > setting the value, whi
Am Mittwoch, den 15.05.2013, 06:03 -0400 schrieb Kieren MacMillan:
> Hi Urs,
>
> > I don't know if it's the _best_ and _most flexible_ structure, but it
> > definitely looks like a _good_ and _flexible_ structure.
>
> I probably can't ask for any more at this stage. ;)
Exactly.
You should take
Am Sonntag, den 12.05.2013, 21:51 -0400 schrieb Kieren MacMillan:
> Hello all,
>
> I'm working on putting together some "house style" stylesheets, and wanted to
> see if I had the best structure…
>
> As one example, I'm tweaking up a Henle piano score stylesheet (e.g.
> Beethoven Piano Sonatas
Am 06.06.2013 00:09, schrieb Janek Warchoł:
Hi,
from the previous discussion it seems that hosting our blog (currently
lilypondblog.wordpress.com) on the same server as our website would be
a bad idea and could lead to problems. I stand corrected.
However, there seems to be another way of givi
Am 06.06.2013 16:21, schrieb Phil Holmes:
- Original Message - From: "Janek Warchoł"
To: "Jan Nieuwenhuizen" ; "Graham Percival"
; "LilyPond Developmet Team"
; "Urs Liska"
Sent: Wednesday, June 05, 2013 11:09 PM
Subject: maybe we
Am 06.06.2013 18:46, schrieb Jan Nieuwenhuizen:
Can't we just use lilypond.org/blog and/or use iframes to include it into our
home page?
Greetings, Jan
Would that mean that www.lilypond.org/blog.html would be a static HTML
page containing nothing than a full-page frame that points to wherever
Am 06.06.2013 19:00, schrieb Urs Liska:
Am 06.06.2013 18:46, schrieb Jan Nieuwenhuizen:
Can't we just use lilypond.org/blog and/or use iframes to include it
into our home page?
Greetings, Jan
Would that mean that www.lilypond.org/blog.html would be a static HTML
page containing nothing
Am 06.06.2013 22:44, schrieb Jan Nieuwenhuizen:
Urs Liska writes:
Would that mean thatwww.lilypond.org/blog.html would be a static HTML
page containing nothing than a full-page frame that points to wherever the
blog is hosted?
Something like that. Possibly we want a
Am 06.06.2013 22:57, schrieb Jan Nieuwenhuizen:
Urs Liska writes:
(- a minor issue is that I don't know how to define the iframe yet. I had to
manually set a height in pixels, which obviously isn't good.)
Oh, I have been using something like this. Problem is possibly
CORS, no prob
Am 06.06.2013 23:01, schrieb Michel Villeneuve:
- Whoever is the admin of lilypond.org would have to:
- register/set up the subdomain blog.lilypond.org
- edit the nameserver (A-Record) for that subdomain to point to my
provider's IP
- Then my server would transparently serve the blog as blo
Am 07.06.2013 08:22, schrieb Janek Warchoł:
Hi,
2013/6/6 Urs Liska :
Am 06.06.2013 19:00, schrieb Urs Liska:
I can try that with an arbitrary iframe page on my server.
You can have a look at http://test.ursliska.de/test.html
It works partially:
- One can see everything and navigate the blog
Am 07.06.2013 09:00, schrieb Janek Warchoł:
2013/6/7 Urs Liska :
But I have yet another idea that could be elegant if the technical
requirements are met.
If the server hosting lilypond.org is capable of running WordPress, i.e. has
- PHP >= 5.2.4
- MySQL >= 5.0
available, we could:
- Cr
One thing I'd definitely support about this is making LSR somewhat version
independent to allow one to have snippets requiring new lily versions.
Maybe providing several lily versions (not necessarily _all_ of course) and use
an appropriate one to compile the snippets. This would also allow us to
One thing I'd definitely support about this is making LSR somewhat version
independent to allow one to have snippets requiring new lily versions.
Maybe providing several lily versions (not necessarily _all_ of course) and use
an appropriate one to compile the snippets. This would also allow us to
"Janek Warchoł" schrieb:
>Hi,
>
>2013/8/20 Frédéric Bron :
>>> For the programmers, i'd like to ask you to look at the branch
>>> dev/tie-crusade/comments
>>> and read the comments we've added to the code together with Franek.
>>
>> Just in case some would need, we can read all the added comm
I'm very sorry, but I currently can't afford neither the time nor the money for
the trip.
Best
Urs
"Janek Warchoł" schrieb:
>Hi,
>
>2013/9/14 David Kastrup :
>> This is a reminder that next weekend, Sept 20th to 24th, there will
>be a
>> LilyPond developer and user meeting in Waltrop, Germany
101 - 200 of 754 matches
Mail list logo
