On 2014/07/16 10:02:52, Mark Polesky wrote:
Here's a new music function called \magnifyStaff (along the lines of
\magnifyMusic) that scales staff sizes, staff lines, bar lines,
beamlets, and
horizontal spacing at the Staff context level.
Just a nitpick: would a renaming to \scaleMusic and
On 2014/07/16 17:13:27, J_lowe wrote:
On 2014/07/16 09:20:45, dak wrote:
There is no doc string here or other documentation.
I wrote one now; didn't do it because I started with a copy of
make-pango-font-tree, and it does not have one as well (I know, not
the
best reason).
Is there some
Am 16.07.2014 21:18, schrieb Mark Polesky:
On Wed, Jul 16, 2014 at 12:01 PM, Paul Morris p...@paulwmorris.com wrote:
The best ideas I've come up with would be either resize or scale.
Since
scale could be confused with the musical meaning of scale, I think resize
is
the better option of these
perpeduumimmob...@gmail.com writes:
On 2014/07/16 17:13:27, J_lowe wrote:
On 2014/07/16 09:20:45, dak wrote:
There is no doc string here or other documentation.
I wrote one now; didn't do it because I started with a copy of
It is not built into the docs, right?
Hi all,
I'd also like to join the party, but I am quite busy in the next time. I
would like to join in for a session via skype or google-hang-out or
similar - I could talk about and discuss the edition-engraver.
Online-participation might be an option for users outside europe?
Cheers, Jan-Peter
On 2014/07/17 06:36:20, dak wrote:
mailto:perpeduumimmob...@gmail.com writes:
On 2014/07/16 17:13:27, J_lowe wrote:
On 2014/07/16 09:20:45, dak wrote:
There is no doc string here or other documentation.
I wrote one now; didn't do it because I started with a copy of
It is not built
perpeduumimmob...@gmail.com writes:
Two follow-up questions:
1.) Is there a way to list all Lily scheme functions and/or all their
docstrings? If you know what function or variable you are looking for,
the docstrings are obviously great. But if I look for something which
matches your
On 2014/07/17 08:28:36, dak wrote:
mailto:perpeduumimmob...@gmail.com writes:
Two follow-up questions:
1.) Is there a way to list all Lily scheme functions and/or all
their
docstrings? If you know what function or variable you are looking
for,
the docstrings are obviously great. But
perpeduumimmob...@gmail.com writes:
That leaves me with only one more question: Is there any reason to use
Texinfo markup in those docstrings, given that all more-or-less obvious
ways of accessing it do not seem to use it? Or should I rather give a
well-formatted uncluttered raw text
On 2014/07/17 09:13:54, dak wrote:
mailto:perpeduumimmob...@gmail.com writes:
That leaves me with only one more question: Is there any reason to
use
Texinfo markup in those docstrings, given that all more-or-less
obvious
ways of accessing it do not seem to use it? Or should I rather
I'm starting work on bringing the snippets in git up to date to match
those in the LSR. Stage one is to change the LSR address of dsi to di in
them all and to bring their version numbers up to 2.18.0. This isn't best
done with makelsr because it does not blindly update sll the snippets,
Looks well coded and well commented. I have some observations/questions
about the regtests, but otherwise LGTM.
https://codereview.appspot.com/117830043/diff/60001/input/regression/magnifyStaff-bar-lines.ly
File input/regression/magnifyStaff-bar-lines.ly (right):
- Original Message -
From: Phil Holmes m...@philholmes.net
To: lilypond-devel@gnu.org
Sent: Thursday, July 17, 2014 11:42 AM
Subject: LSR updates
I'm starting work on bringing the snippets in git up to date to match
those in the LSR. Stage one is to change the LSR address of dsi to
Am 17.07.2014 11:05, schrieb Urs Liska:
Hi,
to give you quick access and a first impression on what I've done on the
openlilylib documentation you can have a look at
http://openlilylib.org/demo-oll/git-commands.html
Updated, now with syntax highlighting! :-)
Thank you, Wilbert, for making
Phil Holmes m...@philholmes.net writes:
I'm starting work on bringing the snippets in git up to date to match
those in the LSR. Stage one is to change the LSR address of dsi to di in
them all and to bring their version numbers up to 2.18.0. This isn't best
done with makelsr because it
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Thursday, July 17, 2014 12:07 PM
Subject: Re: LSR updates
Phil Holmes m...@philholmes.net writes:
I'm starting work on bringing the snippets in git up to date
On 2014/07/17 12:44:20, david.nalesnik wrote:
https://codereview.appspot.com/117830043/diff/60001/input/regression/magnifyStaff-bar-lines.ly#newcode30
input/regression/magnifyStaff-bar-lines.ly:30:
Are so many examples necessary?
No. I've reduced from 5 examples to 3.
Hi Mark,
On Thu, Jul 17, 2014 at 2:34 PM, markpole...@gmail.com wrote:
While I have your attention, there was some discussion on the mailing
list about changing \magnifyMusic and \magnifyStaff to \resizeMusic and
\resizeStaff. Any opinion?
Hmm. To be honest, I rather like \magnifyMusic
On Jul 7, 2014, at 12:29 , Janek Warchoł janek.lilyp...@gmail.com wrote:
... try changing all instances of NullVoice to
Devnull and see what happens. It's a simple thing to do, and with
I tried this with 2.18.2 and 2.19.10. With both versions, the lyrics don’t
respect the tie, which makes it
19 matches
Mail list logo
