Some background PNGs are 0-length

> The following PNG files (only) {snip} are empty (i.e., their length is 0 bytes): > lily-home-32x32.png > nav1-active.png > nav1-bg.png > nav1-hover.png > nav2-active.png > nav2-bg.png > nav2-hover.png > All are in Documentation/pictures/. Another set of these picture files, including their act

Some background PNGs are 0-length

RELEVANT COMMIT The latest commit relevant to the below problem seems to be "Web: Revise navigation bars with CSS gradients": http://git.savannah.gnu.org/cgit/lilypond.git/diff/?id=0a89d9ec5ab4b03a6396c0970aa0a227f8950c31 which regards issue "#4258 Patch: Web: revise navigation bars with CSS gra

Re: *.eps and *.svg .gitignore patterns match files in repo

Here's how to generate the complete list of files in the working tree (and thus, files in the current repository branch) which match patterns anywhere in Git's multiple gitignore sources: $ cd $LILYPOND_GIT $ find . -path ./.git -prune -o -print | git check-ignore --stdin --no-index --verb

*.eps and *.svg .gitignore patterns match files in repo

On Aug 25, 2015; 5:05pm James Lowe wrote: > On 25/08/15 18:48, markdblackwell wrote: >> Per >> https://www.kernel.org/pub/software/scm/git/docs/gitignore.html >> "A gitignore file specifies intentionally untracked files that Git >> should ignore. Files already

*.eps and *.svg .gitignore patterns match files in repo

Per https://www.kernel.org/pub/software/scm/git/docs/gitignore.html "A gitignore file specifies intentionally untracked files that Git should ignore. Files already tracked by Git are not affected" Aug 23, 2015; 6:21am, James Lowe wrote: > I had similar problems when trying to add snippets in the

build/ .gitignore pattern matches files in repo

> Any chance to see an uncensored version of this on the actual mailing list? > --David Kastrup Thanks for that. :) Now, I've added the archive to my toolbar for future checking. The full text follows (without HTML tags; I had used {raw}). Currently, the top level .gitignore (of LilyPond's rep

*.eps and *.svg .gitignore patterns match files in repo

> Any chance to see an uncensored version of this on the > actual mailing list? Not everybody uses Nabble, and you > can see what got actually sent out on the list by looking at > http://lists.gnu.org/archive/html/bug-lilypond/2015-08/msg00065.html > --David Kastrup Thanks for that. :) Now, I've

build/ .gitignore pattern matches files in repo

Currently, the top level .gitignore (of LilyPond's repository) contains this pattern: I found no pattern negating this, in any .gitignore file (at any directory level). Currently, the repository on the server contains files (see below) which match this pattern. Because of this, Git will ignore c

Re: *.eps and *.svg .gitignore patterns match files in repo

> Actually, the following files match patterns in the .gitignore's Currently, the repository on the server contains those *.eps and *.svg files. (I neglected to state this, clearly.) Because of patterns in the .gitignore's, Git will ignore changes to those files. -- View this message in contex

*.eps and *.svg .gitignore patterns match files in repo

Currently, the top level .gitignore (of LilyPond's repository) contains these patterns: I found no pattern negating them, in any .gitignore file (at any directory level). If any files match patterns in the .gitignore's, then: * Should those .gitignore patterns be deleted? * Should those matchin

`Help Us' section duplicated

> Interesting. With me, it does: The link in > leads me to > Not for you? You are right; that link does—for me, too! However, I neglected to be specific enough in my very short summary: >> The *first (front matter) page* of the Contributor's Guide manual >> (version 2.19.23, in the second parag

Re: `Help Us' section duplicated

>> the Contributor's Guide includes a link to `Help us'. >> Should that link go to section `Help us' of: >> 1. The Contributor's Guide manual?; or of >> 2. The Web/General Information manual? > Of course, this only links the subsection within the CG, > as with all other links of the kind. Actuall

`Help Us' section duplicated

The first (front matter) page of the Contributor's Guide manual (version 2.19.23, in the second paragraph) refers people to a very important section, 'Help Us' located in another manual: the Web/General Information manual. In the PDF version: `For more information about different jobs, see Section

`Help Us' section

The first (front matter) page of the Contributor's Guide manual (version 2.19.23, in the second paragraph) refers people to a very important section, 'Help Us' located in another manual: the Web/General Information manual. In the PDF version: `For more information about different jobs, see Section

barNumberCheck broken in LilyPond 2.19.22

If a user passes a wrong bar number to \barNumberCheck, LilyPond 2.19.22 produces a Scheme error: >lilypond tiny-example.ly GNU LilyPond 2.19.22 Processing `tiny-example.ly' Parsing... Interpreting music...C:/progra/lilypond/current/usr/share/lilypond/current/ly/music-functions-init.ly:220:24: In