On Thu, Jul 30, 2009 at 10:19:42AM +0200, Francisco Vila wrote:
> 2009/7/30 Graham Percival :
> > I think it's possibly to detect keypresses in javascript.
>
> Javascript not needed.
>
> Links can have
>
> Next
Neat!
Ok, I think we have enough positive, and no negative, responses.
Valentin, co
On Tue, Aug 04, 2009 at 06:44:12PM -0300, Han-Wen Nienhuys wrote:
> On Tue, Aug 4, 2009 at 5:19 AM, Graham Percival
> wrote:
> > However, I started wondering about all the old history that would
> > be lost when we delete web/ and (to a much lesser extent)
> > web-gop/.
>
> I don't understand thi
Neil Puttock wrote:
> Sorry to throw a spanner in the works, but have you considered what
> will happen if an innocent user adds the Span_arpeggio_engraver to the
> Staff context in order to span voices on one stave?
Can you give an example that fails? (You may want to read my reply to
Joe first
On 8/4/09 8:02 PM, "Joe Neeman" wrote:
> On Tue, 2009-08-04 at 19:02 -0600, Carl Sorensen wrote:
>>
>>
>> On 8/4/09 5:49 AM, "Graham Percival" wrote:
>>
>>> On Tue, Aug 04, 2009 at 09:13:40PM +1000, Cameron Horsburgh wrote:
I'm having trouble with a brand new clone of the git repo. Ru
On Tue, 2009-08-04 at 19:02 -0600, Carl Sorensen wrote:
>
>
> On 8/4/09 5:49 AM, "Graham Percival" wrote:
>
> > On Tue, Aug 04, 2009 at 09:13:40PM +1000, Cameron Horsburgh wrote:
> >> I'm having trouble with a brand new clone of the git repo. Running
> >> lilypond on even the simplest of files
On 8/4/09 5:49 AM, "Graham Percival" wrote:
> On Tue, Aug 04, 2009 at 09:13:40PM +1000, Cameron Horsburgh wrote:
>> I'm having trouble with a brand new clone of the git repo. Running
>> lilypond on even the simplest of files generates this error:
>
>> | programming error: no VerticalAlignment
On Tue, 2009-08-04 at 14:01 -0700, Mark Polesky wrote:
> Mark Polesky wrote:
>
> > Otherwise, does this look good?
>
> I'm sorry to keep doing this, but I keep finding ways of
> improving this. Now I think users should find this very
> intuitive, although the internal workings are more complex.
>
2009/8/4 Graham Percival :
> On Tue, Aug 04, 2009 at 02:53:51PM +0200, John Mandereau wrote:
>> I was thinking on annotated SVG examples, which should be created for
>> the essay BTW -- I believed Till had taken this over a while ago, but I
>> never got news about this.
>
> Do you mean the annotate
2009/8/2 John Mandereau :
> You have surely noticed that this is fixed in Git. Sorry for the little
> delay for fixfing this and for having ignored your patch Neil, I only
> remembered you had complained with this but didn't go back to the email
> thread to look at your patch, though discussions
On Tue, Aug 4, 2009 at 5:19 AM, Graham Percival wrote:
> GUB won't be moved into lilypond git, and web stuff will live in
> master and stable. So currently we're only looking at creating
> one extra repo:
> ...@sv/lilypond/lilypad.git
> description: Lightweight editor for lilypond files
>
>
2009/8/4 Mark Polesky :
> Anyone have any comments/suggestions?
Sorry to throw a spanner in the works, but have you considered what
will happen if an innocent user adds the Span_arpeggio_engraver to the
Staff context in order to span voices on one stave?
A few nitpicks:
(not (null? parent))
(n
On Fri, Jul 31, 2009 at 3:10 PM, Mark Polesky wrote:
>
> Han-Wen Nienhuys wrote:
>> No. In the specific case, I'd recommend making another music
>> function that takes an argument, so you can pass the 15/16
>> explicitly, without mucking with variables.
>
> So it sounds like you believe that one w
Mark Polesky writes:
> Mark Polesky wrote:
>
>> Otherwise, does this look good?
>
> I'm sorry to keep doing this, but I keep finding ways of
> improving this. Now I think users should find this very
> intuitive, although the internal workings are more complex.
>
> I've attached the most recent ve
Mark Polesky wrote:
> Otherwise, does this look good?
I'm sorry to keep doing this, but I keep finding ways of
improving this. Now I think users should find this very
intuitive, although the internal workings are more complex.
I've attached the most recent version, which includes an
annotated ex
>> > IIUC, one interesting advantage of this is that scheme symbols
>> > have less restrictions than parser identifiers:
>> >
>> > \anchor #'m.32
>> > \anchor #'flute2-entrance
>>
>> Mhmm, this is not something we should advertize loudly...
>
> Why not?
I believe it confuses users that Scheme code
Mark Polesky wrote:
> Hopefully there are no more snafus, but I need you guys to test this.
> Let me know if you find any problems. I'd like to apply this if the
> developers approve.
In the file attached to the previous post
http://lists.gnu.org/archive/html/lilypond-devel/2009-08/txtDIrSYMGg1c
Werner LEMBERG wrote:
> > IIUC, one interesting advantage of this is that scheme symbols
> > have less restrictions than parser identifiers:
> >
> > \anchor #'m.32
> > \anchor #'flute2-entrance
>
> Mhmm, this is not something we should advertize loudly...
Why not?
- Mark
__
> IIUC, one interesting advantage of this is that scheme symbols
> have less restrictions than parser identifiers:
>
> \anchor #'m.32
> \anchor #'flute2-entrance
Mhmm, this is not something we should advertize loudly...
Werner
___
lilypond-deve
Trevor Daniels wrote:
Mark Polesky wrote Thursday, July 30, 2009 7:06 PM
It would be nice to have some central place that explains some
"internals" concepts. Here are examples of things that a new developer
might have to ask about, or perhaps spend a long time disentangling:
grob
prob
smob
ou
Trevor Daniels wrote:
Mark Polesky wrote Thursday, July 30, 2009 7:06 PM
It would be nice to have some central place that explains some
"internals" concepts. Here are examples of things that a new developer
might have to ask about, or perhaps spend a long time disentangling:
grob
prob
smob
ou
Mark Polesky wrote:
Han-Wen Nienhuys wrote:
No. In the specific case, I'd recommend making another music
function that takes an argument, so you can pass the 15/16
explicitly, without mucking with variables.
So it sounds like you believe that one way or another, the burden
should be on the
Le mardi 04 août 2009 à 05:06 -0700, Graham Percival a écrit :
> Look, I was sole maintainer of the docs for 4 years. A few times,
> I took a look at the build process because I wanted something or
> other changed. Each time, I abandoned the idea after a few hours,
> because I was getting nowhere
2009/8/4 John Mandereau :
> Le mardi 28 juillet 2009 à 16:39 +0200, Translation Project Robot a
> écrit :
>> A new POT file for textual domain 'lilypond' has been made available
>> to the language teams for translation. It is archived as:
>>
>> http://translationproject.org/POT-files/lilypond-
Jay Anderson wrote:
> global =
> {
> \time 4/4 s4*4*10
> \time 3/4 s4*3*5
> \time 7/4 s4*7
> \time 4/4 \anchor #'coda s4*4*10
> \bar "|."
> }
>
> \addAt #'coda \global {\tempo \markup "Extremely slow"}
IIUC, one interesting advantage of this is that scheme symbols
have less restrictions tha
Le mardi 04 août 2009 à 07:30 -0600, Carl Sorensen a écrit :
> So, I have heartburn about regressions on the stable branch as indicated by
> failure to pass the regtest. But I have no heartburn about "regressions"
> that mean a complicated example that uses tweaks doesn't look right any
> more.
I
Hi,
I use Lilypond to make diagrams of all the available notes on an
accordion. For that I use a single system and switch from bass clef to
violin clef (and it would also be feasible to use 8va and 8ve
modifiers).
Now the problem is that the ambitus is engraved using the first clef of
the syste
Le mardi 04 août 2009 à 06:58 -0700, Graham Percival a écrit :
> Hmm, I suppose this would screw up the cross-references.
Not at all, cross-references are defined in macros.itexi.
> I guess we'll just expect users
> looking at a pdf tarball to open up "general.pdf" first.
We don't care so much
Trevor Daniels wrote:
> Something must have happened between the last
> time git worked and the first time it failed.
> Anything you did during that time is a suspect.
The only other things I can imagine:
1) my anti-virus software might have done something
2) my security might have been compromi
On Tue, Aug 04, 2009 at 12:00:40PM +0200, John Mandereau wrote:
> Le mardi 04 août 2009 à 01:12 -0700, Graham Percival a écrit :
> > Fair enough -- but could you add a post-build rule to rename
> > general.info/pdf/html to lilypond.info/pdf/html ?
>
> Not worth the effort. DIY if you like.
Hmm, I
On Tue, Aug 04, 2009 at 02:53:51PM +0200, John Mandereau wrote:
> Le mardi 04 août 2009 à 05:20 -0700, Graham Percival a écrit :
> > But we don't require them for building the website on
> > lilypond.org.
>
> Inkscape *is* required for building current web site from web branch
> sources.
But it's
Greetings everyone,
as the -devel list tends to get crowded these days, John and I have
opened a separate mailing list for documentation translators.
You can subscribe and read the archives on http://lists.lilynet.net/translations
To whomever is in charge of the translationproject.org LilyPond
c
On 8/4/09 4:00 AM, "John Mandereau" wrote:
> Le mardi 04 août 2009 à 01:12 -0700, Graham Percival a écrit :
>
>
> Yes, even power users could run lilypond and output-distance on entire
> input file directories and detect changes in formatting. This is a goal
> for 2.14, or more reasonnably
Le mardi 28 juillet 2009 à 16:39 +0200, Translation Project Robot a
écrit :
> A new POT file for textual domain 'lilypond' has been made available
> to the language teams for translation. It is archived as:
>
> http://translationproject.org/POT-files/lilypond-2.13.3.pot
>
> http://downl
Le mardi 04 août 2009 à 14:36 +0200, Reinhold Kainhofer a écrit :
> > I see this too, but not on my build. It looks like @translationof
> > commands are ignored on kainhofer.com, as I saw French page names.
>
> Hmm, this should work. I haven't updated texi2html for some days/weeks,
> though...
Le mardi 04 août 2009 à 05:20 -0700, Graham Percival a écrit :
> ... at the very minimum, we could omit the news on the home page
> (that would require one macro/conditional thingie in
> general.texi),
I want to restore and fix the RSS feed, so I merge news-* into a single
source file for import i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 2. August 2009 20:00:56 schrieb John Mandereau:
> Le dimanche 02 août 2009 à 19:00 +0200, Jean-Charles Malahieude a
>
> écrit :
> > For the first point: you'll notice it when you choose a language other
> > than English on the root page and
On Tue, Aug 04, 2009 at 12:55:05PM +0200, John Mandereau wrote:
> Le lundi 03 août 2009 à 05:51 -0700, Graham Percival a écrit :
> > I thought the website was going to be built from the stable
> > branch? If we're doing that, then let's delete the web branches.
>
> This just made me come to mind
On Tue, Aug 04, 2009 at 12:22:02PM +0200, John Mandereau wrote:
> Le lundi 03 août 2009 à 05:57 -0700, Graham Percival a écrit :
> > They complicate the build process
> > even more.
>
> I'm not sure what this means, but it's hard to scare me with the build
> process.
That's the biggest thing th
On Tue, Aug 04, 2009 at 12:58:02PM +0200, Valentin Villenave wrote:
> A lot of users have been using a user-defined Dynamics context for
> years. How about making convert-ly print a warning whenever it finds a
> Dynamics context in a score?
No. Put a warning in changes.itely (the new NEWS), and t
2009/7/31 Joe Neeman :
> It should be sufficient to simply remove the definition of the Dynamics
> context from these files (and the \accepts Dynamics part from
> PianoStaff). The default Dynamics context is very similar (and drew
> heavily from) the piano dynamics template, so it should be a drop-
Le lundi 03 août 2009 à 05:51 -0700, Graham Percival a écrit :
> I thought the website was going to be built from the stable
> branch? If we're doing that, then let's delete the web branches.
This just made me come to mind that I'm for not including News in
generated offline docball: if we did, i
2009/8/4 Han-Wen Nienhuys :
> I can imagine how this would be implemented, but it would be a lot of
> work. If anyone is up for a challenge, I can give some pointers. :)
OK, now there's no way I'm gonna let you get away with such a promise :-)
http://code.google.com/p/lilypond/issues/detail?id=82
Le lundi 03 août 2009 à 05:57 -0700, Graham Percival a écrit :
> ok, I'm willing to go as far as adding a single "View sources"
> link at the bottom of the page, which takes people to a
> Snippets->Examples page. Of course, that would require adding the
> Examples to LSR (or at least new/), requir
Le mardi 04 août 2009 à 01:12 -0700, Graham Percival a écrit :
> Yes, but what if somebody reads the LM, looks at the source, then
> accuses us of lying when we claimed "no tweaks were used"? I
> wouldn't blame that person at all!
Of course, I rather meant lilyond-book trickery, which we probably
Mark Polesky wrote Tuesday, August 04, 2009 9:23 AM
Does anyone know -- is there any harm in just generating a new
SSH key pair?
No harm at all.
I think my modem gives me a different IP address
from time to time.
It (well, your ISP) will - that's normal.
I could be making that up, and I
On Tue, Aug 04, 2009 at 01:23:11AM -0700, Mark Polesky wrote:
> Does anyone know -- is there any harm in just generating a new
> SSH key pair?
Absolutely no problems. Go ahead.
> I think my modem gives me a different IP address
> from time to time. I could be making that up, and I don't know
> i
Does anyone know -- is there any harm in just generating a new
SSH key pair? I think my modem gives me a different IP address
from time to time. I could be making that up, and I don't know
if that would even affect the SSH stuff. But I'm willing to try
anything at this point. Would generating a ne
GUB won't be moved into lilypond git, and web stuff will live in
master and stable. So currently we're only looking at creating
one extra repo:
g...@sv/lilypond/lilypad.git
description: Lightweight editor for lilypond files
However, I started wondering about all the old history that would
On Mon, Aug 03, 2009 at 08:51:55PM +0200, John Mandereau wrote:
> Le lundi 03 août 2009 à 05:51 -0700, Graham Percival a écrit :
> > Well, it depends how you define "tweak". In the LM, we lean
> > pretty heavily on "tweak = \override and \set" (plus others).
> > Some of those examples definitely *
On Mon, Aug 03, 2009 at 03:19:54PM -0600, Andrew Hawryluk wrote:
> 2009/8/3 John Mandereau :
> > No, there isn't. Having pictures in respective manual directories would
> > create more Git history noise and more ad-hoc include path
> > specifications for images shared between several manuals. Put
On Mon, 2009-08-03 at 13:28 +0200, Werner LEMBERG wrote:
> The documentation of the new `after-title-spacing' property and its
> siblings is missing. Additionally, there are no regression tests
> showing those parameters in action.
Thanks, I'll add this to my todo list.
Joe
_
51 matches
Mail list logo
