On Mon, Mar 14, 2005 at 10:49:51AM -0800, Thomas Bushnell BSG wrote:
> Martin Michlmayr <[EMAIL PROTECTED]> writes:
>
> > * Thomas Bushnell BSG <[EMAIL PROTECTED]> [2005-03-14 02:14]:
> > > I know how to take care of the package. But Anthony Fok is currently
> > > the maintainer, so he needs to e
Matthias Kilian writes:
> Solved. I used to run MAKEINFO=/usr/local/bin/makeinfo sh autogen.sh,
> since OpenBSD's own texinfo is too old and I'd to install a newer
> one in /usr/local.
>
> This, however, breaks the check for SPLITTING_MAKEINFO in aclocal.m4
> (see patch below), which in turn disab
Werner LEMBERG writes:
> To provide fixcc.py is a nice idea!
Thanks. I like consistent formatting, which fixcc is good at ;-)
> Here some comments on parts where its formatting is not optimal.
I agree with your suggestions, but most seem non-trivial. I would be
delighted if you could fix some
Thomas Bushnell writes:
> Ok, adoption in progress. Would the lilypond people please point me
> to the official web pages
http://lilypond.org
> and subscription information for the relevant mailing lists I should
> be on?
I do not think we can require anything, but info-lilypond and
lilypo
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> * Thomas Bushnell BSG <[EMAIL PROTECTED]> [2005-03-14 02:14]:
> > I know how to take care of the package. But Anthony Fok is currently
> > the maintainer, so he needs to either orphan it or offer it for
> > adoption. I can't speak about the question
* Thomas Bushnell BSG <[EMAIL PROTECTED]> [2005-03-14 02:14]:
> I know how to take care of the package. But Anthony Fok is currently
> the maintainer, so he needs to either orphan it or offer it for
> adoption. I can't speak about the question of making that happen; I'm
> just saying that if it s
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Thanks for the offer! I'm not sure however how adopting a package
> works, I guess you'll have to sort with Anthony and Pedro.
I know how to take care of the package. But Anthony Fok is currently
the maintainer, so he needs to either orphan it or
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> > We are a bit concerned with old LilyPond packages, and a potential
> > new maintainer (Pedro Kroger) with his sponsor going mia.
>
> Who was going to sponsor him?
I use lilypond all the time, so I'm happy to adopt it if necessary.
I'm a bad mentor
Cool...
>Some proof of concept is ready.
>I think there could be also a configuration wizard (to set PDF viewer
>and bash's path), if something is not found in the path.
I think (step-by-step) configuration wizard is a good idea too!
Maybe the user can click on a link on the tutorial mode to st
Hi,
We do not have a lilytool tutorial yet, do we? I think a lilytool tutorial
will make a easier LilyPond tutorial (I'm thinking of Wiki) ;)
>
>
> Original Message
>Subject: easier LilyPond tutorial?
>Date: Sat, 5 Mar 2005 17:46:09 +0100
>From: Han-Wen Nienhuys <[EMAI
On Mon, 14 Mar 2005, Laura Conrad wrote:
"JR" == Juergen Reuter <[EMAIL PROTECTED]> writes:
JR> may I suggest to add a 'packed' option to lilypond-book? This could
JR> help enhancing some of the ancient notation examples in the
JR> documentation.
Is this intended to fix some of the proble
> "JR" == Juergen Reuter <[EMAIL PROTECTED]> writes:
JR> may I suggest to add a 'packed' option to lilypond-book? This could
JR> help enhancing some of the ancient notation examples in the
JR> documentation.
Is this intended to fix some of the problems with parts that use
larger
[EMAIL PROTECTED] writes:
> CVSROOT: /cvsroot/lilypond
> Module name: lilypond
> Branch:
> Changes by: Werner LEMBERG <[EMAIL PROTECTED]> 05/03/14 17:19:56
>
> Modified files:
> . : ChangeLog
> mf : feta-klef.mf feta-macros.mf
>
> Log mes
[CVS 2005-03-13 00:00]
To provide fixcc.py is a nice idea! Here some comments on parts where
its formatting is not optimal.
o After the word `operator' I suggest that a space remains. Example:
Interval_t &operator *= (T r)
^
Currently, fixcc.py removes
Hi Mats, and all,
Wow, thank you for the link, I haven't heard about this one. But I see now
that it was mentioned in lilypond mailing lists before, shame on me.
It doesn't have a link at lilypond.org, does it? If not, shouldn't it?
It seems to work for the problem in mind it was designed: to sh
Ciao Giancarlo,
The php solution you are speaking about is the very same idea I was speaking
about. It can be used to process not just short snippets (transmitted as
form-data), but whole bunch of ly files (maybe even zipped), and this is
where the HTTP upload method comes in the picture.
It's ma
I'm trying to collect here the main requirements which should be addressed
by a future LilyPond Server:
- It should use a recent version of LilyPond, with optional or automatic
applying of convert-ly
- fast response (online all the time, enough computing power). Providing
output files as required
[EMAIL PROTECTED] writes:
> Salvete,
>
> WikiTeX has been stuck in 2.2.6 upon the grounds twain
> here documented:
>
> http://wikitex.org/lilypond
>
> 2.5.14, namely, (1) cuts short the .png on multipage output;
> and (2) systematically ignores `printpagenumber = ##f'.
>
> Is t
On Sun, 27 Feb 2005, Benkõ Pál wrote:
2005-02-27 Pal Benko <[EMAIL PROTECTED]>
* lily/mensural-ligature.cc (brew_flexa):
make flexa parts of ligatures look more similar to square parts
Hi, Pál!
Currently, the thickness property of the flexa shape aplies to all
segments of the out
Since this is a usage question for the stable version of LilyPond,
I recommend to keep the discussion on the lilypond-user mailing
list.
I don't know any details about the drum support in LilyPond, but
as far as I know, the only way to get a different note head on
one note out of several in the sam
In addition to what I said below, please take a look at the example
called apply-output.ly in the "Regression Test" document in the
on-line documentation. In the example called note-head-style.ly,
you will find the documentation of different note head styles that
you requested in an earlier email.
Regarding the new ideas for a lilypond server, have you seen the
already existing one at http://wikitex.org/? See also the recent
discussions on the mailing lists related to the LilyPond Snippet
Repository (LSR).
/Mats
___
lilypond-devel mailing list
l
Thomas Bushnell writes:
[fixed lilypond list address: not snipping]
>> > We are a bit concerned with old LilyPond packages, and a potential
>> > new maintainer (Pedro Kroger) with his sponsor going mia.
>>
>> Who was going to sponsor him?
>
> I use lilypond all the time, so I'm happy to adopt it
23 matches
Mail list logo
