Re: anybody know apache? (dir structure of docs)

2009-11-14 Thread Jan Nieuwenhuizen 
Op donderdag 12-11-2009 om 23:06 uur [tijdzone +0100], schreef Reinhold
Kainhofer:

> ###
> 
> ## Rewrite all non-existing files at toplevel to the /web/ dir, so
> our 
> ## internal structure for rsync doesn't have to be changed.
> RewriteEngine on
> RewriteBase /
> 
> # Don't rewrite already rewritten pathes!
> RewriteCond %{REQUEST_URI} !^/web/
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteRule ^(.*)$ /web/$1 [QSA,L]
> 
> ### 

Thanks!  It took me a while to get this to work for
the current/old site as well as for the new one, and
to get all details right.

I did not see much reason not to install it right away,
it can even make the switching easier, we possibly do
not need to rsync the new site to /web, even.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen  | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl| http://lilypond.org



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

2009-11-14 Thread Jan Nieuwenhuizen 
Op vrijdag 13-11-2009 om 17:45 uur [tijdzone +], schreef Graham
Percival:
> On Fri, Nov 13, 2009 at 04:59:20PM -, Trevor Daniels wrote:
> >
> > Chris Snyder wrote Friday, November 13, 2009 4:35 PM
> >> Graham Percival wrote:

> interesting.  is that really the GNU style?  maybe I should check.
> Or wait, maybe this is something changed in fixcc.py.  I'll check
> there.

GNU codyng style is what you get when you edit code in Emacs or
run C-x h M-x indent-region in Emacs.  That's what fix-cc.py does.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen  | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl| http://lilypond.org



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: My "make doc" is broken

2009-11-14 Thread Frédéric Bron 
> I have redone it again and the doc is now compiling since 1 hour so I
> assume it is working! Do not understand what happens.
> Will see tomorrow morning if anything good happened.

Well it stopped with an error before tomorrow:

cd ./out-www; texi2pdf -I ./out-www -I
/home/bronf/lilypond/Documentation/out -I
/home/bronf/lilypond/Documentation -I
/home/bronf/lilypond/Documentation --batch  general.texi
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 file:line:error style messages enabled.
 %&-line parsing enabled.
entering extended mode

(./general.texi (/home/bronf/lilypond/tex/texinfo.tex
Loading texinfo [version 2009-08-14.15]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texmf-texlive/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.3 <23 July 2005>
) localization, formatting, and turning on texinfo input format.)
(./general.aux) (/home/bronf/lilypond/tex/txi-en.tex)
(/home/bronf/lilypond/Documentation/macros.itexi (./version.itexi)
(/home/bronf/lilypond/Documentation/common-macros.itexi)) [1{/var/lib/texmf/fon
ts/map/pdftex/updmap/pdftex.map}] <./pictures/double-lily-modified3.png>
(/home/bronf/lilypond/Documentation/general/news-front.itexi)
l.111: Undefined cross reference `old news-snt'.
l.111: Undefined cross reference `old news-snt'.
l.111: Undefined cross reference `old news-pg'.
l.124: Undefined cross reference `download-snt'.
l.124: Undefined cross reference `download-snt'.
l.124: Undefined cross reference `download-pg'.
l.126: Undefined cross reference `manuals-snt'.
l.126: Undefined cross reference `manuals-snt'.
l.126: Undefined cross reference `manuals-pg'.
l.130: Undefined cross reference `development-snt'.
l.130: Undefined cross reference `development-snt'.
l.130: Undefined cross reference `development-pg'.
l.132: Undefined cross reference `development-snt'.
l.132: Undefined cross reference `development-snt'.
l.132: Undefined cross reference `development-pg'. [1] (./general.toc) [-1]
(./general.toc) (./general.toc)
(/home/bronf/lilypond/Documentation/general/introduction.itexi (Introduction) <
./pictures/flat-design.png (PNG copy)>
l.41: Undefined cross reference `freedom-snt'.
l.41: Undefined cross reference `freedom-snt'.
l.41: Undefined cross reference `freedom-pg'.
l.44: Undefined cross reference `background-snt'.
l.44: Undefined cross reference `background-snt'.
l.44: Undefined cross reference `background-pg'.
l.55: Undefined cross reference `productions-snt'.
l.55: Undefined cross reference `productions-snt'.
l.55: Undefined cross reference `productions-pg'.
l.58: Undefined cross reference `testimonials-snt'.
l.58: Undefined cross reference `testimonials-snt'.
l.58: Undefined cross reference `testimonials-pg'.
l.69: Undefined cross reference `text input-snt'.
l.69: Undefined cross reference `text input-snt'.
l.69: Undefined cross reference `text input-pg'.
l.72: Undefined cross reference `alternate input-snt'.
l.72: Undefined cross reference `alternate input-snt'.
l.72: Undefined cross reference `alternate input-pg'.
Underfull \hbox (badness 1) in paragraph at lines 100--104
[...@textrm Maybe draw in-spi-ra-tion from [...@texttt 
http://lilypond.org/web/ab
out/features[][][] @textrm and

Overfull \hbox (4.16455pt too wide) in paragraph at lines 100--104
[...@texttt http://lilypond.org/web/switch/tour[][][] @textrm and [...@texttt h
ttp://lilypond.org/web/switch/advantages[][][]
 <./pictures/flat-design.png (PNG copy)>
l.121: Undefined cross reference `essay-snt'.
l.121: Undefined cross reference `essay-snt'.
l.121: Undefined cross reference `essay-pg'. [2] <./pictures/lilypond-book.png>
[3] l.198: Undefined cross reference `text input-snt'.
l.198: Undefined cross reference `text input-snt'.
l.198: Undefined cross reference `text input-pg'. <./examples/bach-bwv610-small
.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
 <./examples/granados-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
[4] <./examples/ancient-headword-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
 <./examples/cary-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
 <./examples/sesto-full-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
[5] <./examples/sesto-piano-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
 <./examples/sesto-violin-small.png (PNG copy)>
Overfull \hbox (147.00592pt too wide) in paragraph at lines 12--12
[]
/home/bronf/lilypond/Documentation/general/introduction.itexi:0: Could not find
 image file examples/tab-example-small for pdf.
@dopdfimage ...uld not find image file #1 for pdf}
  @else @gdef @pdfimgext {PD...

@imagexxx ...ndent @ifpdf @dopdfimage {#1}{#2}{#3}

Re: [PATCH] serious doubts about waf

2009-11-14 Thread Graham Percival 
Ok, it seems the the key was to call
   bld.rescan(node)
after adding it.

I'm off to a short conference tomorrow.  I expected to have internet
access, but when I mentioned it to one of the professors today, he
just laughed at me.  :(so if I'm not around for a few days, that's
why.

I'm going to work on
  1)  the waf build
  2)  merging the two init-pl files.
in the dev/gperciva branch.

I don't know how much time I'll have, but it's traditional for me to
do build system stuff at conferences.  I have no plans on touching
anything else, so if you're waiting for me to do anything, either do
it yourself or keep on waiting.

Cheers,
- Graham


On Thu, Nov 12, 2009 at 5:54 PM, Graham Percival
 wrote:
> On Thu, Nov 12, 2009 at 10:21:16AM +0100, John Mandereau wrote:
>> Le jeudi 12 novembre 2009 à 00:21 +0100, John Mandereau a écrit :
>> > Does the attached patch convince you to go on on Waf?
>>
>> Actually, please ignore my patch and checkout a SVN copy of Waf instead
>>
>> svn checkout http://waf.googlecode.com/svn/trunk/ && mv trunk waf
>>
>> then invoke waf-light from this checkout.
>
> I'm already working from waf.  I did an svn update.  It still
> fails the first time I run it, while working perfectly the second
> time.
>
> In case there's any misunderstanding, I'm talking about the
> dev/gperciva branch.  The minimal example that Thomas Nagy sent
> works just fine.
>
>
> 1)  if you can't duplicate the problem after checking out
> dev/gperciva, then I'll check a third time to see if there's any
> old version of waf floating around on this machine.
>
> 2)  if you can duplicate it in dev/gperciva, then please either
> fix the problem in my wscripts, or follow up with the waf people
> (if you can extract another small example).
>
> Cheers,
> - Graham
>


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: My "make doc" is broken

2009-11-14 Thread Frédéric Bron 
> I hope that you did a "make clean; make" first.  There was a
> commit recently that did something about strings and markups, so
> perhaps that's the problem.

I did make dist-clean and rerun autogen.sh
I have redone it again and the doc is now compiling since 1 hour so I
assume it is working! Do not understand what happens.
Will see tomorrow morning if anything good happened.

> Note that if you're using the EXTERNAL_BINARY trick, then git head
> will no longer work for you.  And if you _are_ using that trick,
> please mention it in the report.

Do not know that trick. I cloned the entire git repository.

Frédéric


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: My "make doc" is broken

2009-11-14 Thread Graham Percival 
On Sat, Nov 14, 2009 at 07:57:05PM +0100, Frédéric Bron wrote:
> Since I upgraded ubuntu to 9.10, make doc does not work anymore but
> why? Is it because of the ubuntu upgrade or because of git pull?
> Here is the output:
> ...
> Renaming input to: `music-function-string-markup.ly'
> music-function-string-markup.ly:15:24: error: syntax error, unexpected
> STRING, expecting \markup or MARKUP_IDENTIFIER
>   \testFunc "test string
> "

I hope that you did a "make clean; make" first.  There was a
commit recently that did something about strings and markups, so
perhaps that's the problem.

Note that if you're using the EXTERNAL_BINARY trick, then git head
will no longer work for you.  And if you _are_ using that trick,
please mention it in the report.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

My "make doc" is broken

2009-11-14 Thread Frédéric Bron 
Since I upgraded ubuntu to 9.10, make doc does not work anymore but
why? Is it because of the ubuntu upgrade or because of git pull?
Here is the output:
...
Renaming input to: `music-function-string-markup.ly'
music-function-string-markup.ly:15:24: error: syntax error, unexpected
STRING, expecting \markup or MARKUP_IDENTIFIER
  \testFunc "test string
"
music-function-string-markup.ly:16:30: error: syntax error, unexpected
STRING, expecting \markup or MARKUP_IDENTIFIER
  c2 
]
music-function-string-markup.ly:14:0: error: errors found, ignoring
music expression

\relative c' {
]
error: failed files: "ed/lily-05317feb.ly"
command failed: /home/bronf/lilypond/out/bin/lilypond -I ./ -I
./out-www -I ../../input -I /home/bronf/lilypond/Documentation -I
/home/bronf/lilypond/Documentation/snippets -I ../../input/regression/
-I /home/bronf/lilypond/Documentation/included/ -I
/home/bronf/lilypond/mf/out/ -I /home/bronf/lilypond/mf/out/ -I
/home/bronf/lilypond/Documentation/pictures -I
/home/bronf/lilypond/Documentation/pictures/./out-www -dbackend=eps
--formats=ps,png,pdf  -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitlefr --header=doctitlees
--header=doctitlede --header=doctitlenl --header=doctitleja
--header=doctitlehu --header=texidoc --header=texidocfr
--header=texidoces --header=texidocde --header=texidocnl
--header=texidocja --header=texidochu -dcheck-internal-types
-ddump-signatures -danti-alias-factor=2 -I
"/home/bronf/lilypond/out/lybook-db"  -I
"/home/bronf/lilypond/input/regression"  -I
"/home/bronf/lilypond/input/regression"  -I
"/home/bronf/lilypond/input/regression/out-www"  -I
"/home/bronf/lilypond/input"  -I  "/home/bronf/lilypond/Documentation"
 -I  "/home/bronf/lilypond/Documentation/snippets"  -I
"/home/bronf/lilypond/input/regression"  -I
"/home/bronf/lilypond/Documentation/included"  -I
"/home/bronf/lilypond/mf/out"  -I  "/home/bronf/lilypond/mf/out"  -I
"/home/bronf/lilypond/Documentation/pictures"  -I
"/home/bronf/lilypond/Documentation/pictures/out-www" --formats=eps
--verbose  -deps-box-padding=3.00  -dread-file-list
-dno-strip-output-dir
"/home/bronf/lilypond/out/lybook-db/snippet-names--163355416.ly"
Child returned 1


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

2009-11-14 Thread demery 

>> 2) many programmers view code style in a highly personal,
>> quasi-religious manner.
> ...
>> ...Han-Wen and Jan have different views...

Foe me its a matter of blocking the whitespace to to present the code in a
way that makes it easier to understand.  This is not easy to do with any
automated tool.

A project done by a one-man team sees a limited set of tools and has a
limited amount of schizophrenia in esthetic decisions.

When the product is ported to as many platforms as ly is you see all the
toolsets and more.  Fonts make a difference.  Screen size and eyestrain
influence choice of font and font size.  Vendor coding style influences
things too.  Apple used to be rather cavalier about code namespace, they
would use short common words for class, structure, and field symbols. 
With cocoa things are somewhat improved, NS prefixes everything new, and
method names are verbose and attempt to be meaningful.  The verbosity has
a downside tho, many invocations are multi-line, especially when localized
text is involved.

> If the standard isn't even completely defined then how could the job of
> code janitor be given to an inexperienced Frog?

Actually, its a pretty good learning experience.

> until an official LilyPond coding standard is
> fully set in stone.

IMHO that would be a mistake, for example, switch statements have a number
of ways of being presented that are effective, no one way serves all code.

>> Any automatic tool will

have faults, including being unavailable on some platform now in use.

I recall a movement sometime ago to mix code and prose commentary, making
real tab stops available for the code, and also allowing illustrations. 
Guess it died a hard death.

--
Dana Emery



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: new abc2ly files not distributed

2009-11-14 Thread Graham Percival 
On Fri, Nov 13, 2009 at 06:17:58PM +0100, Reinhold Kainhofer wrote:
> Am Freitag, 13. November 2009 15:30:21 schrieb Graham Percival:
> > Trying to build GUB:
> > 
> > file from VC not distributed: lilypond-2.13.8/make/abc-vars.make
> 
> Hmm, I'm adding the *.abc files to the EXTRA_DIST_FILES in abc-vars.make:
> 
> ABC_FILES = $(call src-wildcard,*.abc)
> OUT_LY_FILES = $(sort ${ABC_FILES:%.abc=$(outdir)/%.ly})
> OUT_FILES = $(OUT_LY_FILES)
> EXTRA_DIST_FILES += $(ABC_FILES)
> 
> Shouldn't that suffice? And I have no idea why the files from the make 
> directory 
> are not added... Sorry, but I don't understand how GUB collects all the files 
> that are distributed.
> I simply copied the make files (make/*.make and GNUmakefile) from the 
> musicxml 
> regression tests and adjusted them for abc2ly.

Sorry, I don't know how GUB does this.  My first instinct was to
check if "make dist" worked, but that failed in a completely
different way (linking css files!)


I really don't know what to suggest.  It would be nice if "make
dist" worked, but fixing this would require delving into the
current build system.  It would be nice if the new waf build
system was working, but currently even the initial stages of
building the docs are failing because of the "directory in build
tree doesn't exist in the source tree" issue.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread nicolas . sceaux 

On 2009/11/12 21:40:37, Carl wrote:


http://codereview.appspot.com/154056/diff/1/10#newcode1
ly/chord-repetition-init.ly:1: \version "2.13.8"
Just a question.  Why do this in a .ly file instead of in a .scm file?


This initializes the parser object, and thus shall be placed in a .ly
file, where this object is accessible.
It is similar to language files, defining note names: this file in
particular defines the shortcut name.

I'm correcting the documentation as you suggest. Thanks for your review.


http://codereview.appspot.com/154056


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread Carl Sorensen 



On 11/14/09 3:30 AM, "nicolas.sce...@gmail.com" 
wrote:

> On 2009/11/12 21:40:37, Carl wrote:
>> Nicolas,
> 
>> It looks great!  Thanks.
> 
>> I have just a couple of suggestions for changes to the documentation
> 
> I've addressed your remarks concerning documentation in a new patch
> 
>
> 
> 
> http://codereview.appspot.com/154056


Looks great to me!

Thanks,

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread nicolas . sceaux 

On 2009/11/12 21:40:37, Carl wrote:

Nicolas,



It looks great!  Thanks.



I have just a couple of suggestions for changes to the documentation


I've addressed your remarks concerning documentation in a new patch

  


http://codereview.appspot.com/154056


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel