On 11/13/21 2:53 AM, Federico Bruni wrote:
Paul, do you have a backup of lilypondblog.org?
I might try converting it to a static site generator and host it on
some free platform.
Hi Federico, Thanks for your message. I'd like to help with this.
Unfortunately, I don't have an up-to-date backup
Congrats and thanks Federico! Glad to know there's a Debian container now.
-Paul
On 11/03/2017 01:13 PM, Federico Bruni wrote:
Hi all
Few days ago I made a new release (version 0.2):
https://github.com/fedelibre/LilyDevOS/releases/tag/v0.2
I chose to keep calling the final images LilyDev, e
Hi Urs,
On 05/13/2018 02:02 PM, Urs Liska wrote:
1) for SVG output the objects would get the class assigned (along with
an id). I don't have any idea yet how that is implemented, though.
This will make it possible to work with CSS in a display environment.
You'll be glad to know this is alre
On 05/17/2018 09:00 AM, David Kastrup wrote:
Man, I must have slept through this. "this is already supported in
2.19" is misleading if it's actually only supported _outside_ of 2.19,
namely by chancing upon people in the know in the mailing lists.
The problem with that kind of support is that
Huh, looks like I already created a changes entry and regtests for this
output-attributes feature.
https://codereview.appspot.com/308430043
https://sourceforge.net/p/testlilyissues/issues/4974/
I think I didn't do user documentation because the previous ID-only
functionality didn't have any.
5355]
<https://sourceforge.net/p/testlilyissues/issues/5355/> Doc: document
grob metadata in SVG output in Notation Reference*
*Status:* Started
*Created:* Thu Jun 21, 2018 06:35 PM UTC by Paul Morris
*Last Updated:* Mon Jun 25, 2018 09:41 AM UTC
*Owner:* Paul Morris
Doc: document grob metada
On 07/01/2018 02:43 AM, David Kastrup wrote:
Edit your .git/config file and change the repository address according
to the Git repository clone command given for developers on LilyPond's
Savannah page.
Thanks. It turned out I had a new SSH key that I hadn't added to
Savannah yet. So I got i
James,
On 07/04/2018 09:41 AM, James Lowe wrote:
On Sun, 1 Jul 2018 17:52:02 -0400, Paul Morris wrote:
Thanks. It turned out I had a new SSH key that I hadn't added to
Savannah yet. So I got it to work by following CG 3.4.9
http://lilypond.org/doc/v2.19/Documentation/contributor/c
For Google Summer of Code 2015 David Garfinkle worked on MusicXML export.
(See mailing list archives:
https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Garfinkle&submit=Search%21&idxname=lilypond-devel&max=20&result=normal&sort=score
)
I don't know if the code he wrote was ever checked i
On 10/16/2018 10:48 AM, Paul Morris wrote:
I don't know if the code he wrote was ever checked in somewhere, on a
branch or something. (It's not mentioned in the issue for this feature.)
I've now added the GSOC 2015 code to the issue and put a link to
Jan-Peter's work t
On 10/17/18 2:55 AM, Jan-Peter Voigt wrote:
2. the MusicXML is created "manually" with simple string-concatenation.
[...]
It would be very helpful to have an XML-lib at hand for the export.
Hi all, I've done some work on this. See this PR:
https://github.com/jpvoigt/lilypond-export/pull/9
Hi Carl and everyone,
On 12/2/18 8:02 PM, Carl Sorensen wrote:
We used to have black be the color of the glyphs. We made a very specific and
intentional move from black to currentColor. And it was an improvement, IMO.
That is why I feel strongly about moving away from currentColor.
curre
On 12/3/18 10:07 AM, Richard Shann wrote:
what seems strange is that there seems to be no concept of "backgound
color" in SVG (logical in a way as SVG is about things you can draw)
allowing for the possibility of drawing white on white.
Easily setting a background color would be a nice option
Hi Andrew,
On 12/13/18 6:17 PM, Andrew Bernard wrote:
[I don't know anything about containers, but I am willing to learn. But it
would be goodo to get the VM machine going alos.]
I also recommend the container approach. I hadn't used them before
Federico brought them to LilyDev.
Basically
On 12/13/18 8:47 PM, Paul Morris wrote:
I also recommend the container approach.
Here are the steps for the container setup:
https://github.com/fedelibre/LilyDevOS/tree/v0.3/mkosi#container
-Paul
___
lilypond-devel mailing list
lilypond-devel
On 1/24/19 3:08 PM, Thomas Morley wrote:
From my point of view (and limited knowledge) other newly implemented
guilev2-procedures are not _that_ important.
One area where guile2 (and upcoming guile3) would be useful is for
MusicXML export. David Garfinkle's summer of code project (mentored
On 1/25/19 10:43 AM, David Kastrup wrote:
Paul Morris writes:
One area where guile2 (and upcoming guile3) would be useful is for
MusicXML export. David Garfinkle's summer of code project (mentored
by David Kastrup) made a start on using guile2's sxml and pattern
matching procedu
Hi Harm,
On 1/25/19 3:17 PM, Thomas Morley wrote:
If you do a regtest-comparison between builds with guile-1 and
guile-2, nothing serious is visible in the images. So far one could
say "well enough".
Though, looking through the other results, some other flaws are noticeble.
One I remember immed
Hi Jan-Peter,
On 1/26/19 1:36 PM, Jan-Peter Voigt wrote:
sorry for missing to mention your contribs! And thank you for the XML
port.
Oh, no problem, and you're welcome!
I didn't look into the gsoc code lately, but perhaps the two projects
dont need to compete?
Yeah, it would be nice to co
On 1/29/19 4:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.linux-64.sh
Installed on Ubuntu 18.04.1 LTS and tested with a couple of pieces.
Everything appears to be working fine.
Thanks to all for the work on GUB and the next stable LilyPond release!
-Paul
On 1/29/19 1:24 PM, David Kastrup wrote:
Paul Morris writes:
On 1/29/19 4:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.linux-64.sh
Installed on Ubuntu 18.04.1 LTS and tested with a couple of
pieces. Everything appears to be working fine.
Thanks to all for the work on GUB and the next
Hi Carl,
On 4/2/19 12:14 AM, carl.d.soren...@gmail.com wrote:
https://codereview.appspot.com/337870043/diff/40001/input/regression/chord-name-exceptions.ly#newcode29
input/regression/chord-name-exceptions.ly:29: chExceptions = #(append
(chordmode->exception-entry chordVar markupVar) chExcepti
Urs Liska wrote
> There's another thing I can throw into the discussion:
> blog.openlilylib.org.
> www.openlilylib.org is a domain that I recently registered for a
> 'community' kind side-project to LilyPond. The current content of the
> web site is still a stub, but you can get a good impression
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?
Hmmm... I think it would help to have a clearer decision on the
relationship of the blog with the main LilyPond site. Once there's an
answer to "what" is w
Urs Liska wrote
>> Something like that. Possibly we want a lilypond.org-site navigation
>> menu somewhere at the top, served from either site.
> As we'd want such a thing also when the blog is viewed 'standalone' it
> would probably better to include this in the blog theme and have the
> iframe
Urs Liska wrote
> So it looks as we're having two options if we want to provide a more
> lilypond-like address for the blog:
>
> a)
> blog.lilypond.org
> Involving remapping the subdomain from lilypond.orgs server to another
> one (possibly mine)
> b)
> blog.openlilylib.org
>
> But I would say
Janek Warchoł-2 wrote
> I already have a dozen sketches for posts, so i can promise at least
> one post per week till the end of summer. I hope that more people
> will join by then; we have a dozen active contibutors so if people
> write one post each month (or two) it should amount to a fairly ac
Janek Warchoł-2 wrote
> Thanks :) However, it actually would be unbearable for me to slow
> down so much. It was already hard (for me and Urs) to restrict
> ourselves to post no more than 1 time per day.
> Frankly, 1 post per week is the _slowest_ pace at which i expect to be
> able to blog conti
This is good news Janek. One project that might be appropriate is working on
integrating the improvements to musicxml2ly that the Philomelos team have
made on their own fork, but haven't had time to contribute back upstream.
That seems like low-hanging fruit that should be picked.
As David K men
I'll throw in a couple of my thoughts:
A. The user-friendly web interface for contributing snippets to the LSR is
really key for it to work for novice users like myself (at least when I
started). I find it quite convenient and easy to use. If I had had to
learn git in order to contribute a snipp
Urs Liska wrote
> Am 12.12.2013 04:19, schrieb Graham Percival:
>> On Wed, Dec 11, 2013 at 02:21:28PM +0100, Urs Liska wrote:
>>> - I changed "Easier editing" to "Editing".
>> ok. I also like the "applicances" tab, although I agree with you
>> that the name might be ideal (but I also can't thi
Urs Liska wrote
> Am 12.12.2013 14:10, schrieb Mike Solomon:
>> On Dec 12, 2013, at 3:06 PM, Urs Liska <
> ul@
> > wrote:
>>
>>> The page "GSoC 2012" is obviously outdated.
>>>
>>> What should be done with it?
What about just changing it to "GSoC" (dropping the "2012") and make it a
general GSoC
David Kastrup wrote
> I suggest to let the topic of the _last_ GSoC rest until there are more
> tangible results. That concerns the "Janek's GSoC work can legitimately
> be presented in a positive light" angle.
>
> That does neither mean leaving the page as it is currently, nor removing
> it comp
Urs Liska wrote
> But clicking on "Web (split HTML)" brings you to a copy of the whole
> website, just several directories below the original.
> This is irritating, to say the least.
I agree that this does not make sense for someone browsing the website, and
the text does not really explain what'
Paul Morris wrote
> Usually this works by putting
> http://www.example.com/etc/etc.html";>
> in the
>
> of any non-canonical page, pointing to the canonical page.
Forgot to say: under the scenario of using 301 redirects you wouldn't need
to do any http://li
Graham Percival-3 wrote
>> >Maybe another whole page about "sample
>> >usage", or something like that?
>>
>> Maybe this should even be split: One dedicated page explaining the
>> concept of IDEs, similar to the Text Input page but less elaborate,
>> and another page that more or less lists availab
David Kastrup wrote
> Paul Morris <
> paul@
> > writes:
>
>> Here's how I would reword the warning to make it as concrete and simple
>> as
>> possible:
>>
>> Note: With LilyPond you write and edit music by typing text with your
>> key
Carl Peterson wrote
> I use MuseScore,
> Scorio, and Finale Notepad (depending on where I am and how I feel)
> for compositional work because they provide ease of note entry in the
> composing process and the ability to have instant aural feedback on
> what I've written (particularly if I'm not at
Carl Peterson wrote
> Retyping by far. I pretty much write exclusively a cappella SATB, and I
> have developed a very specific template/workflow for the part combining
> and
> layout. I've tried a few different ways of getting the music from these
> formats into LP, and in each case, I found myself
Carl Sorensen-3 wrote
> I can't speak for Carl P's work. For me, effective LP input files require
> structure (variables, contexts) that MusicXML knows nothing of. And it's
> generally easier to create them than to fix them on import.
I see what you mean. Unfortunately it makes it harder to use
Urs Liska wrote
> a) in what form should I provide such an image that it can be translated
> and modified in the future?
Since your image is simply boxes with text and arrows connecting them, one
possibility might be to do it with html and css rather than making it an
image. The styling and layo
Another possibility would be to do it as a LilyPond snippet using markup
commands. That would keep it as close as possible to the usual LilyPond
docs/website process.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Pre-review-questions-about-image-s-and-translatio
Carl Peterson wrote
> Maybe not texidoc-wise, but it's something I thought about on its own
> merits. I'm personally not crazy about is as it would basically result in
> us creating a very specialized set of CSS parameters for a very specific
> thing that could be changed and completely removed or
The message below appeared fine on Rietveld but hasn't come through on the dev
list after about 45 minutes, probably because the email address for my google
account was not subscribed to the list. So here it is.
Thanks, -Paul
Reviewers: ,
Message:
This patch introduces a make-path-stencil funct
paulwmorris wrote
> On 2014/01/18 04:52:51, lemzwerg wrote:
>> A minor thing: We use two spaces after a full stop in documentation
>> strings.
>> (At least it should be like that in general.)
>
> Done.
>
> https://codereview.appspot.com/54050043/
This second patch set appeared successfully on Ri
Trevor Daniels wrote
> It seems you're not authorised to change the labels, so I've done it for
> you.
Ok, thanks!
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Lilypond-auto-Issue-3818-in-lilypond-Patch-stencil-scm-addmake-path-stencil-function-tp158369p158
I have uploaded the patches to the issue tracker. Would someone please push?
(I don't have push access.) Thanks in advance. -Paul
https://code.google.com/p/lilypond/issues/detail?id=3818
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/stencil-scm-add-make-path-stenci
Here's a late-arriving thought about potential GSOC projects...
What about working on the code for the LSR, Mutopia, or similar "LilyPond
ecosystem" type projects? Seems like they would offer simpler code bases
and lower hanging fruit that a student could achieve in a summer.
I think GUILEv2
Greetings dev list,
I submitted a patch and I am sorry to say that somehow it was added to the
wrong issue:
https://codereview.appspot.com/54050043
And a new issue (with the wrong title and content) was created in the google
code tracker:
https://code.google.com/p/lilypond/issues/detail?id=3883
Hi Benko,
benko.pal wrote
>> It seems that my local git branch was still associated with that previous
>> issue, the one I had submitted a patch for before. I was using git-cl.
>
> yes, git-cl associates the rietveld issue permanently to a branch
> (in your ~/lilypond-git/.git/config); it seems
pkx166h wrote
> 3883 Enhancement Paul Morris review Patch: stencil.scm: add
> make-path-stencil function
This issue 3883 should just be deleted. It was generated in error, see:
http://lists.gnu.org/archive/html/lilypond-devel/2014-03/msg00034.html
I would do it but I don&
Here is a crazy and implausible idea that I thought I'd share for curiosity's
sake, just thinking out loud for kicks and not as a serious suggestion:
compiling LilyPond to Javascript so it can run in a web browser.
Mozilla has introduced tools[1] that make it possible to compile large C/C++
code b
By chance I came across the following blog post about Guile 2.2, apparently
it's due out later this year.
http://wingolog.org/archives/2013/11/26/a-register-vm-for-guile
Most of it is technical and above my head but the summary is that it should
be significantly faster: "A simple count-up-to-a-
David Kastrup wrote
> GUILE2.2 from master takes eternities to compile, like more than half an
> hour or so. LilyPond does a lot of on-the-fly evaluation, and Guile2.0
> is already a big step backwards in that department compared to Guile
> 1.8.
>
> If they don't get compilation and partly interp
Hi David and Werner,
David Nalesnik-2 wrote
> \version "2.19.3"
>
> offsetPositions =
>
> #(define-music-function (parser location) ()
>
> #{
>
> \override Slur.positions =
>
> #(lambda (grob)
>
> (cons
>
> (cdar (ly:slur::calc-control-points grob))
>
> (c
Hi all,
On the question about possibilities for some kind of partial compilation,
I'd be curious to hear from Jan about his experience with Schikker's
List[1]. Do I remember correctly that it uses LilyPond to re-engrave only
part of the music, just the part that changed?
Cheers,
-Paul
[1] htt
Jan Nieuwenhuizen wrote
> Yes, that's correct. It's an ugly optimization that's needed because
> lilypond would otherwise be too slow for interactive use. It will
> probably only work (or seem to work) if the changes made are small
> enough. Currently, partial engraving is line-based but we coul
Jan-Peter Voigt wrote
> I think Guile V2 is the most important issue regarding lilypond in general
> and especially with these thoughts. This would speed up the scheme-part of
> lilypond and ensure its inclusion in linux-distros.
+1
And I suppose that any potential future work on optimizing and
Federico Bruni wrote
>> Does anyone know if we got any applicants for this summer of code
>> project?
>> I remember seeing at least one inquiry about it.
>
> https://www.google-melange.com/gsoc/homepage/google/gsoc2014
>
> 2 days and few hours left and I couldn't find any lilypond project
> searc
David Kastrup wrote
> You mean with regard to patches? Let's first figure out what we want to
> arrive at. Personally, I'm not really enthused about any proposal
> including my own ones yet. But maybe we can manage to find something
> making most people happier yet.
I like the idea of something
David Kastrup wrote
>> As a first step (just working with \override X.X.stencil =) could there
>> be
>> an easier way to just override a stencil with a markup (that gets
>> converted
>> into a stencil)?
>
> That would end up a very invasive mess. A stencil is really a stencil
> and referenced as
David Kastrup wrote
> There is not one "code that handles overriding stencils". Overrides are
> a general mechanism. So we are talking about the code _interpreting_
> stencils. This code will tend to be some get_property ("stencil") call.
> There are a lot of those from a lot of different engrav
David Kastrup wrote
> Overrides are type-checked early, so you'd get the error early.
> Callbacks are considered valid when type-checking however, so a callback
> returning something unfitting will lead to a late error message
> (hopefully).
Ok, makes sense. Thanks again for the explanations.
-P
Thought of another idea for a name:
\substitute \markup {...} Score.TimeSignature
But maybe it's no better than \replace, which is shorter and basically
conveys the same thing.
Cheers,
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Issue-3918-Add-alternating
David Kastrup wrote
> "replace" is a bit too generic in my opinion. I rather like the flair
> of \behold. \substitute does not seem all that bad either, however.
\behold does have flair, but I think it wouldn't really convey what we'd
want. (i.e. pointing out what's already there or revealing s
David Kastrup wrote
>> How about "\adorn"?
>
> Less cute: \retouch.
I like \retouch better than \adorn. So far my favorites (for what it's
worth) are \redraw, \substitute, and \replace, since I think they convey
well what the user is doing, from the user's perspective. I think you're
right that
David Kastrup wrote
> "\redraw" implies overdrawing, and the others don't carry a "visual"
> connotation. True, neither does \omit.
>
> Apart from "replace" being more likely to collide with other uses, the
> order of arguments would favor substitute as its grammar can be
>
> substitute xxx
Thomas Morley-2 wrote
> Maybe a step in this direction:
>
> \version "2.19.6"
>
> appear =
> #(define-music-function (parser location mrkp item)
>(markup? symbol-list-or-music?)
>(let ((stil (lambda (item)
> (grob-interpret-markup item mrkp
> #{ \tweak stencil #s
David Kastrup wrote
>>
>> Assuming we would want to support stencils as well as markups, we'd need
>> a
>> new type predicate:
>>
>> markup-or-stencil?
>>
>> And if it is to be as flexible as a \tweak, then it should also support
>> procedures (i.e. that return a stencil).
>
> I don't think it ma
David Kastrup wrote
>> So we'd need:
>>
>> markup-or-stencil-or-procedure?
>
> markup-or-stencil-or-procedure-or-false? ...
>
> We don't do this elsewhere.
This particular case raises a general question. Instead of having to define
an "x-or-y?" type predicate for each combination that might be
Paul Morris wrote
> #(define-music-function (parser location arg)
> (or (boolean?) (number?) (procedure?))
> ...)
I suppose it would need to be something like this to work for multiple
arguments:
#(define-music-function (parser location argA argB)
((or boolean? number?
dak wrote
> So my proposal would be to try making a fast feature cut _except_ for
> Guile 2 migration and focus on getting that done with.
+1 Makes sense to me.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/LilyPond-2-20-planning-tp162960p162974.html
Sent from
Thomas Morley-2 wrote
> Hi Paul,
> in general I disagree.
> Nearly every time I thought I'd need a predicate for multiple
> argument-types, I found a way to code it better/simpler.
Hi Harm,
Maybe you're right that better/simpler code uses single-type arguments. I'm
not convinced but I'll defer to
Thomas Morley-2 wrote
> No.
> It abuses the syntax for an _optional_ argument, with the default ""
Ah, I see. Thanks for the explanation and example. I see that if you don't
use the (predicate? default) form for supplying an optional/default argument
then you get an error: Unbound variable "x"
markpolesky wrote
> magnifyMusic =
> #(define-music-function (parser location mag mus) (number? ly:music?)
>(_i "Magnify the notation of @var{mus} without changing the
> staff-size, using @var{mag} as a size factor. Stems, beams, and
> horizontal spacing are adjusted automatically.")
>#{
>
markpolesky wrote
>> Can be simplified: (lambda (x) x) is the same as x
>
> Not in this case; guile would complain about unbound variable x. I
> could have used the guile function `identity', but I opted not to since
> it's not documented in the guile manual. I'll rewrite it though, so
> that th
Thomas Morley-2 wrote
>> But *do* we need two different variables which then are used with
> exactly the
>> same value?
>> Do we need the option to change the distance of the segno double bar
> line?
>
> I'd say yes.
> I'm always against loosing functionality, and deleting 'thin-kern would
> limit
markpolesky wrote
> Here's a new music function called \magnifyStaff (along the lines of
> \magnifyMusic) that scales staff sizes, staff lines, bar lines,
> beamlets, and horizontal spacing at the Staff context level. Staff
> lines are prevented from being scaled smaller than the default (and
> co
markpolesky wrote
> Regarding the naming, looks like it's a tie between `resize' and
> `magnify', with `magnify' slightly ahead if you count Paul's vote as
> split:
>
> scale: Paul
> resize: Paul, Marc
> magnify: James, David N.
>
> Unless there's more opposition, I'll probably push it as `magni
markpolesky wrote
> But before I start recoding the thing, I would like to know if
> there's any good reason to retain the current \magnifyMusic
> interface.
Hi Mark, I can't think of any. It seems like all benefits and no drawbacks
to me. Good idea to make these more consistent!
Cheers,
-Paul
From: https://code.google.com/p/lilypond/issues/detail?id=4040
Mark Polesky wrote
> I don't have a solution, but my interest is piqued because apparently
> someone here understands how ledger-positions works? The documentation
> for ledger-positions ( Issue 1935 ) is utterly, utterly incomprehen
Richard Shann-2 wrote
> To do this I think I need to have an additional property to be used via
> something like this
>
> (if (ly:context-property-where-defined context 'compact)
> ...
>
> to decide whether to format the chord symbol in a compact fashion or to
> use the default formatting.
> If t
David Kastrup wrote
> So I think we should likely reorder the English notename language such
> that the default output is the abbreviated form. Thoughts?
+1 That makes good sense to me.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Another-English-notename-iss
Urs Liska wrote
> I just stumbled over
> http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and
> http://lilypond.org/website/gsoc-2012.html
I still think it would be best to convert it into a generic GSOC page and
start the process of updating it for the next round which will
Greetings LilyPond developers,
Over the last few weeks I had some time and found myself experimenting with
the appearance of the LilyPond website, especially the main navigation
bars/menus at the top of each page. You can see a "sketch" of what I've
come up with at the following URL:
(Take out th
Thanks for your thoughts Phil. More below...
Phil Holmes-2 wrote
> I would say that some of the changes are a matter of personal aesthetics,
> and so it's not possible to say which is better: it's just taste. And if
> you say that much of this is tidying and improving, then I wouldn't
> objec
Thanks Urs and Trevor for chiming in. I've made another version that can be
seen here:
http://clairnote.org / lilypond-web-demo2/
(just remove the spaces as before...)
The background image is restored and I managed to get the Lily icon with
"LilyPond" appearing next to it in the main nav bar.
Hi Urs, my responses are below...
Urs Liska wrote
> I think there is no official entity who makes such decisions. It's
> rather like someone uploading a patch and others objecting against it or
> not. As I experienced changes to the website are expected to raise more
> objections than obscure
Thanks for the feedback Abraham, Joram, and Urs.
I've changed the search box color to make it lighter and less yellow-ish.
Basically I realized that it just needs to be close to white without being
exactly white (to avoid looking like it has been "cut out" and you're
looking through a hole in t
Heikki Tauriainen wrote
> Apparently the problem was that access to the Google account was not
> enabled for "less secure apps" in the account's security settings;
> git-cl worked after changing this option. Sorry about the noise.
I'm glad I found this post. I was caught by the same thing and wa
pkx166h wrote
> Fails to apply to current master.
Hmmm, I'm not sure what went wrong. It succeeded previously and then I just
added the images without changing any code. I rebased on origin/master
before submitting the patch set (#3) and everything seemed to be in place
(using gitk to check). B
Thanks James for committing this patch. I see that the revised CSS file is
now in effect on the LilyPond website.
The html remains to be updated, which will require running the website build
scripts. (This will change "Main" to "LilyPond" in the main nav bar.)
Also I've submitted a pull request
Phil Holmes-2 wrote
>> The html remains to be updated, which will require running the website
>> build
>> scripts. (This will change "Main" to "LilyPond" in the main nav bar.)
>
> The website build happens automatically. Any changes in git master that
> are
> part of the website get implemente
Phil Holmes-2 wrote
>> Yes, please. According to the CG the images need to be in this repo to
>> be
>> accessible to the website.
>
> Done.
Thanks Phil.
I don't know when the cron job runs, but just for kicks I checked the
current html that's up on the site. It seems the changes from this ea
> On Jan 24, 2015, at 5:06 PM, Phil Holmes wrote:
>
> I believe I've kicked a website rebuild off. Could you confirm thr results
> are as expected, please?
Hmmm... I'm not seeing any difference. (at least not yet...?) After the
changes take effect the main navigation bar should be:
LilyPon
> On Jan 25, 2015, at 6:37 AM, Phil Holmes wrote:
>
> I definitely see a _different_ website. In IE9 the shaded search box and
> plainer nav bar are there, and the small LilyPond image is no longer on the
> nav bar.
I'm seeing this too. These changes are the result of the revised CSS file, a
I looked in the website section of the contributor's guide[1] and found some
things that might be relevant:
Under "Overall Idea" at the top:
"All scripts and makefiles used for the website build are run from a “trusted”
copy. Any modification to those files in git needs a human to review the
c
> On Jan 25, 2015, at 9:53 AM, Phil Holmes wrote:
>
> That's fixed it. Hadn't realised thingy.init counted as a trusted script.
Great, looks good here!
Thanks again,
-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/
Urs Liska wrote
> Guile 2.0 transition.
Here's the description of the GUILE 2.0 project from last year:
https://www.gnu.org/software/soc-projects/ideas-2014.html
I don't think any of the ideas listed on the lilypond.org GSoC page have
already been completed/exhausted, so they are not out of date
Just uploaded a revised patch to rietveld 203050043
"Also add new classes to IE fixes CSS"
Got the message below, so I'm emailing lilypond-devel with the google
tracker issue number: 4288
Cheers,
-Paul
--
We were not able to associate this patch with a google tracker issue.
Please enter a
1 - 100 of 234 matches
Mail list logo
