This should be trivial to fix. I would do it but I can't
figure out from the sources how `robots.txt' is generated.
IIUC (correct me if I'm wrong), only the following rules
need to be followed:
1) The only valid locations for blank lines are *above* a
User-agent line and below the last
Graham Percival wrote:
Huh, I didn't reliaze we kept the old unstable directories
around; they're not listed on
http://lilypond.org/documentation
anybody mind if I delete the unstable doc dirs?
I might mind, but I don't think I'd be able to give any good
reason why. I think it's kinda neat
On Wed, Dec 16, 2009 at 01:12:16AM -0800, Mark Polesky wrote:
Graham Percival wrote:
Huh, I didn't reliaze we kept the old unstable directories
around; they're not listed on
http://lilypond.org/documentation
anybody mind if I delete the unstable doc dirs?
I might mind, but I don't
Updates:
Status: Started
Comment #2 on issue 852 by percival.music.ca: stop google from indexing old
docs
http://code.google.com/p/lilypond/issues/detail?id=852
Mark started this. I've updated the robots.txt and submitted lilypond to
google's
site crawler, but I have no clue if
Updates:
Labels: -Type-Defect Type-Other
Comment #3 on issue 842 by percival.music.ca: bibliography not built
http://code.google.com/p/lilypond/issues/detail?id=842
I guess we're kind-of using Type-Other for build-related stuff.
--
You received this message because you are listed in
Updates:
Labels: -Type-Documentation Type-Other
Comment #2 on issue 815 by percival.music.ca: Enhancement: AJAX-powered
search auto-completion for the online documentation
http://code.google.com/p/lilypond/issues/detail?id=815
Lining this up with the other webpage-related stuff.
--
Updates:
Labels: -Type-Other Type-Documentation
Comment #2 on issue 846 by percival.music.ca: copyright years for manuals
http://code.google.com/p/lilypond/issues/detail?id=846
Mark started this.
I'm (re)defining Type-Documentation as anything that can be done by editing
texi/tely
Updates:
Status: Fixed
Comment #3 on issue 845 by percival.music.ca: AUTHORS / THANKS should be
integrated into new website
http://code.google.com/p/lilypond/issues/detail?id=845
... and now finished it. I've changed the topdocs AUTHORS to use the new
file.
--
You received this
On Wed, Dec 16, 2009 at 1:24 PM, Mats Bengtsson
mats.bengts...@ee.kth.se wrote:
Graham Percival wrote:
Note that if anybody wants to do serious archeological work, they
can just grab git
Yes!
Is this a vote in favor of removing the v1.9 docs from the website,
and leaving v1.8 and v2.0
Comment #7 on issue 854 by percival.music.ca: lilycontrib.tcl
http://code.google.com/p/lilypond/issues/detail?id=854
BTW, does anybody other than Carl feel like taking it over? Mark,
maybe? :)
I think version 0.5 is actually a step back from the previous one (where it
just had
a
It's part of the lilypond binary (or scheme functions) itself, not
lilypond-book.
OK.
The best solution is probably to add a new command line option
`--default-left-padding' to lilypond-book (which is then used in
the Makefile with value 0mm to override the default setting of
3mm), and
Please read again in the Learning Manual on how to specify durations. In
your example, you ask LilyPond to let each chord have a duration that
equals 4/3 of a crotchet (since 1 means whole note = 4/1 crotchets, 2
means halft note = 4/2 crotchets, 8 means minim = 4/8 crotchets, and so
on. Just
On Wed, Dec 16, 2009 at 2:02 PM, Werner LEMBERG w...@gnu.org wrote:
The best solution is probably to add a new command line option
`--default-left-padding' to lilypond-book (which is then used in
the Makefile with value 0mm to override the default setting of
3mm), and adding a snippet option
Graham Percival gra...@percival-music.ca writes:
On Wed, Dec 16, 2009 at 2:02 PM, Werner LEMBERG w...@gnu.org wrote:
The best solution is probably to add a new command line option
`--default-left-padding' to lilypond-book (which is then used in
the Makefile with value 0mm to override the
On Wed, Dec 16, 2009 at 6:59 AM, Graham Percival
gra...@percival-music.ca wrote:
Disallow: /doc/v1.9/
Huh, I didn't reliaze we kept the old unstable directories around;
they're not listed on
http://lilypond.org/documentation
anybody mind if I delete the unstable doc dirs?
IIRC it is a
If the makefile sets it to 0mm, then what happens for longer
examples with bar numbers? Presumably somebody needs to go through
all the docs to find multi-line examples, then add
[left-padding=3mm]
to those examples.
Exactly. However, in most multi-line examples of the lilypond
Graham Percival wrote:
True, although it would be simple to have
doc/stable/
doc/devel/
doc/archive/
That's better.
Oh, we'll keep the stable docs. I just don't think the
old *unstable* docs are worth having online.
Is it really such a burden to keep the old docs on the
lilypond.org
Han-Wen Nienhuys wrote:
On Wed, Dec 16, 2009 at 6:59 AM, Graham Percival
gra...@percival-music.ca wrote:
Disallow: /doc/v1.9/
Huh, I didn't reliaze we kept the old unstable directories around;
they're not listed on
http://lilypond.org/documentation
anybody mind if I delete the
2009/12/16 isaac theh...@gmail.com:
i think this is not in the list of known bugs because i looked through it and
didnt find it. and im not top posting (i dont know what top posting means)
the problem is the length of the full bar notes. in theory, 3/4 time can have
a
semibreve as a full
Updates:
Labels: -Priority-Low Priority-Medium
Comment #2 on issue 712 by lemzwerg: alignment of multiple \tempo marks
over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712
(No comment was entered for this change.)
--
You received this message because you are
Status: Accepted
Owner: lemzwerg
New issue 936 by lemzwerg: \tempo makes TextSpanner too long
http://code.google.com/p/lilypond/issues/detail?id=936
\version 2.13.10
\header { texidoc =
A @code{\tempo} mark must not influence a @code{TextSpanner} object
within another context.
Below is a
Updates:
Labels: Type-Defect Priority-Medium
Comment #1 on issue 936 by lemzwerg: \tempo makes TextSpanner too long
http://code.google.com/p/lilypond/issues/detail?id=936
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC
On Wed, Dec 16, 2009 at 8:06 PM, Werner LEMBERG w...@gnu.org wrote:
Do you actually expect the vertical formatting of the snippet below as
shown in the attached PDF?
Wow. CCing to bug- just in case.
Cheers,
Valentin
___
bug-lilypond mailing list
Updates:
Labels: Fixed_2.12.2
Comment #4 on issue 697 by Carl.D.Sorensen: Path problem on Windows
http://code.google.com/p/lilypond/issues/detail?id=697
Everything works properly on WinXP under parallels. Double-clicking
results in a correctly-produced .pdf
--
You received this
Comment #1 on issue 883 by Carl.D.Sorensen: stems may collide with
noteheads in tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883
It appears that the note heads are being spaced only to avoid the other
note-heads, i.e. that the stems are not
considered at all.
Comment #2 on issue 883 by Carl.D.Sorensen: stems may collide with
noteheads in tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883
Further investigation causes me to believe that this behavior is caused by
the addition of skylines (see lily/note-
spacing.cc, lines
Should I add an item to the Major release checklist about
this? See the attached patch. I'll apply it if you guys
think it's a good idea. The alternative is to write some
script that generates robots.txt, but that's beyond me.
Let me know.
- Mark
From
27 matches
Mail list logo
