Marc Hohl hohlart.de> writes:
> I am about to upload a patch for these four glyphs within the next
> days, but I wanted to ask whether a new (or enhanced existing)
> regtest is necessary for this type of enhancement?
They could conceivably be broken accidentally, by a mistaken change
to our .mf
Dear developers,
[tl;dr: how about ISO language codes for input language selection?]
some time ago, I suggested to add French ("français") to the list of
note-name languages as an alias to "italiano". This is the current
state, "español" was also added.
The discussion back then was about some in
Another discussion point:
3. \bookpartTitleMarkup (analogous to \bookTitleMarkup and \scoreTitleMarkup).
Cheers,
Kieren.
On Jan 2, 2014, at 1:40 PM, Kieren MacMillan
wrote:
> Hello all,
>
> Riffing on some recent threads/discussions… I’d love to have a discussion
> about what can (and canno
Hello all,
Riffing on some recent threads/discussions… I’d love to have a discussion about
what can (and cannot) be done to take the current \book & \bookpart
mechanism(s) to the goal line, and then come up with a list of specific feature
requests (and possible bounties) to get us there.
Here
Hi all,
Does anyone have a function to automatically lay out a list of markups in two
columns?
Bonus points for margin/width/gutter parameter control, and auto page-breaking.
=)
I’m doing it all manually right now, and it’s a bit frustrating…
Thanks,
Kieren.
___
Here's my (very simple) Vagrant setup. Am I perhaps missing some
dependencies?
https://gist.github.com/svenax/8222686
--
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
Sven Axelsson:
> It appears as if texi2html needs word-writeable folders to work. Thus I
> took the simple route of running make doc (and make test) under sudo. Is
> that how others does it too?
Nope, git clone, pull, ./autogen.sh, make all, make doc all as the same
user, no problems like the one
On 2 January 2014 17:10, James wrote:
> On 02/01/14 15:51, David Kastrup wrote:
>
>> Sven Axelsson writes:
>>
>> It appears as if texi2html needs word-writeable folders to work.
>>>
>> No, it just needs writeable folders to work.
>>
>> Thus I took the simple route of running make doc (and make
On Wed, Jan 1, 2014 at 10:12 AM, James wrote:
> On 07/12/13 18:33, Carl Sorensen wrote:
>> I've thought of some possible fixes:
>>
>> 1) Add an "expert mode" button that then would open up a listbox that
>> would allow you to choose your branch.
>>
>> 2) Create a special, branch-unaware version of
On 02/01/14 15:51, David Kastrup wrote:
Sven Axelsson writes:
It appears as if texi2html needs word-writeable folders to work.
No, it just needs writeable folders to work.
Thus I took the simple route of running make doc (and make test) under
sudo. Is that how others does it too?
No, never
Sven Axelsson writes:
> It appears as if texi2html needs word-writeable folders to work.
No, it just needs writeable folders to work.
> Thus I took the simple route of running make doc (and make test) under
> sudo. Is that how others does it too?
No, never. I think that if you do
make
sudo m
- Original Message -
From: "Trevor Daniels"
To: "David Kastrup" ;
Sent: Thursday, January 02, 2014 3:37 PM
Subject: Re: Announcing 2.18.0 widely?
BTW, are the number of downloads recorded anywhere? It would
be interesting to track this for stable releases.
Google analytics should
It appears as if texi2html needs word-writeable folders to work. Thus I
took the simple route of running make doc (and make test) under sudo. Is
that how others does it too?
--
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
David Kastrup wrote Thursday, January 02, 2014 2:54 PM
> Apart from a note about the convert-ly accident, does anybody see a
> reason not to announce 2.18.0 presently to a wide audience? Or should
> we wait until 2.19.0 is out? I _think_ that the web site should be fine
> currently.
I think it
Hello list,
happy new year to you all!
I have drawn some new glyphs for LilyPond, namely
1) the double G clef, mentioned in
http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00029.html
2) the varpercussion clef, mentiaoned in the same message
3) the tenor G clef, mentioned in
http:/
James writes:
> On 02/01/14 14:54, David Kastrup wrote:
>> Apart from a note about the convert-ly accident, does anybody see a
>> reason not to announce 2.18.0 presently to a wide audience? Or should
>> we wait until 2.19.0 is out? I _think_ that the web site should be fine
>> currently.
>>
> A
On 02/01/14 14:54, David Kastrup wrote:
Apart from a note about the convert-ly accident, does anybody see a
reason not to announce 2.18.0 presently to a wide audience? Or should
we wait until 2.19.0 is out? I _think_ that the web site should be fine
currently.
Are there any considerations fro
Apart from a note about the convert-ly accident, does anybody see a
reason not to announce 2.18.0 presently to a wide audience? Or should
we wait until 2.19.0 is out? I _think_ that the web site should be fine
currently.
--
David Kastrup
___
lilypon
On 2 January 2014 12:50, Phil Holmes wrote:
> AFAICS it will be complaining about the directory below where the
> logfile is found.
>
Thanks. Making that folder (./build/input/regression/lilypond-book/out-www)
world writeable did the trick.
Continuing the build now. We'll see if this is needed
AFAICS it will be complaining about the directory below where the logfile is
found.
--
Phil Holmes
- Original Message -
From: Sven Axelsson
To: lilypond-devel@gnu.org
Sent: Thursday, January 02, 2014 11:29 AM
Subject: Building Lilypond documentation
I've decided to get
On 01/01/14 21:35, David Kastrup wrote:
Benkő Pál writes:
2014/1/1 :
Janek, when people start with `git clone` do they also get a staging
branch that tracks the one on savannah?
I think we still want at least one mention of how to set up a 'staging'
branch to track origin/staging,
git che
On 02/01/14 11:29, Sven Axelsson wrote:
I've decided to get at least a little active in Lilypond development,
and thought I should start with getting my development environment up
and running. I get some weird errors when building the different doc
targets,
What does 'building the different d
On Jan 2, 2014, at 1:29 PM, Sven Axelsson wrote:
> I've decided to get at least a little active in Lilypond development, and
> thought I should start with getting my development environment up and
> running. I get some weird errors when building the different doc targets,
> such as:
>
> Plea
I've decided to get at least a little active in Lilypond development, and
thought I should start with getting my development environment up and
running. I get some weird errors when building the different doc targets,
such as:
make[4]: Entering directory `/lilydev/build/input/regression/lilypond-b
LGTM.
https://codereview.appspot.com/40040046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM, from mere inspection.
https://codereview.appspot.com/45420044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
26 matches
Mail list logo
