Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

[David Kastrup]

David Kastrup  writes:

> Urs Liska  writes:
>
>> I've only read the documentation, and I agree with Trevor that this is a
>> real improvement.
>>
>> One question/suggestion: Would it be possible to have \voicify accept a
>> single symbol with a "pattern", which should allow two entries like
>> #'top-bottom and #'bottom-top? This could count the number of following
>> expressions and calculate the list (like 1,3,5,6,4,2 in the docs example).
>
> No.  A symbol already has meaning.
>
> You could try separate commands \voicifyUp and \voicifyDown .  I am not
> sure whether or not \voicify should not be \voices or \voicing or
> \voicings instead, possibly making for nicer compounds like that.
>
> I mean, something like
>
> \voices 1,3,4 ...
>
> possibly stresses the connection with \voiceOne, \voiceThree, \voiceFour
> better.  And then \voicesUp and \voicesDown ?  Somehow a bit too close
> to \stemUp / \stemDown meaning something entirely different.
> Upwards/Downwards ?  Rising/Falling ?

And frankly, I don't think it a good idea.  What should

\voicesUp << a \\ b \\ c >>

be equivalent to?  \voicify 2,3,1 or \voicify 2,4,1 ?  And \voicesDown ?

\voicify 1,3,2 or \voicify 1,4,2 ?

There are obvious use cases for either and people will be confused when
the pattern does not fit their use after all, and people will always
forget which is which.

Those numbered lists are brief and painless to enter, clear in the
semantics, and they never force you to warp your input to match the
scheme when it would be nicer in another manner.

That's a strong point of the command, and a \voicesUp/\voicesDown does
not save enough typing to make up for this.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

[David Kastrup]

Urs Liska  writes:

> I've only read the documentation, and I agree with Trevor that this is a
> real improvement.
>
> One question/suggestion: Would it be possible to have \voicify accept a
> single symbol with a "pattern", which should allow two entries like
> #'top-bottom and #'bottom-top? This could count the number of following
> expressions and calculate the list (like 1,3,5,6,4,2 in the docs example).

No.  A symbol already has meaning.

You could try separate commands \voicifyUp and \voicifyDown .  I am not
sure whether or not \voicify should not be \voices or \voicing or
\voicings instead, possibly making for nicer compounds like that.

I mean, something like

\voices 1,3,4 ...

possibly stresses the connection with \voiceOne, \voiceThree, \voiceFour
better.  And then \voicesUp and \voicesDown ?  Somehow a bit too close
to \stemUp / \stemDown meaning something entirely different.
Upwards/Downwards ?  Rising/Falling ?

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES - Countdown for April 6th

[James]

Hello,

Here is the current patch countdown list. The next countdown will be on
April 9th.

A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/





Push:


5111 Implement spacing-pair for MeasureCounter - David Nalesnik
https://sourceforge.net/p/testlilyissues/issues/5111
http://codereview.appspot.com/319610043


5109 Allow 'staff-padding to work with MeasureCounter - David Nalesnik
https://sourceforge.net/p/testlilyissues/issues/5109
http://codereview.appspot.com/312580043


Countdown:


5115 Add guile-config-1.8 etc. searching - Masamichi Hosoda
https://sourceforge.net/p/testlilyissues/issues/5115
http://codereview.appspot.com/320830043


5114 Add a \voicify command - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/5114
http://codereview.appspot.com/320820043


5113 Parser: discriminate quoted and non-quoted strings - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/5113
http://codereview.appspot.com/316430043


5112 web: move Google Summer of Code information in included/ -
Federico Bruni https://sourceforge.net/p/testlilyissues/issues/5112
http://codereview.appspot.com/321830043


4276 Allow changes of scripts by type (e.g. changing the padding and
font-size > of "tenuto" throughout a file) - David Nalesnik
https://sourceforge.net/p/testlilyissues/issues/4276
http://codereview.appspot.com/324740043


Review: No patches in review at this time.


New:


5117 Web: Addition to 'What we wrote' section - James Lowe
https://sourceforge.net/p/testlilyissues/issues/5117
http://codereview.appspot.com/316440043


5116 Allow \change to same context type - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/5116
http://codereview.appspot.com/322820043



Regards

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [patch] Add a work to "we wrote" list

[James]

Hello,

On Thu, 6 Apr 2017 10:24:42 +0200
Francisco Vila  wrote:

> Hello,
> 
> this adds my PhD thesis to the list in the web. Sorry for not
> uploading the patch in a more formal way; I can not recall if I've
> done it anytime. I'm willing to, however.
> 
> I'll be relatively unreachable for a week. See you on 04/13
> 


https://sourceforge.net/rest/p/testlilyissues/issues/5117/


Have a good holiday

James


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

[Urs Liska]

I've only read the documentation, and I agree with Trevor that this is a
real improvement.

One question/suggestion: Would it be possible to have \voicify accept a
single symbol with a "pattern", which should allow two entries like
#'top-bottom and #'bottom-top? This could count the number of following
expressions and calculate the list (like 1,3,5,6,4,2 in the docs example).

Urs

Am 06.04.2017 um 16:29 schrieb tdanielsmu...@googlemail.com:
> LGTM
>
> David, you've found an excellent way of squaring the circle!
>
> Trevor
>
>
> https://codereview.appspot.com/320820043/
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

[tdanielsmusic]

LGTM

David, you've found an excellent way of squaring the circle!

Trevor


https://codereview.appspot.com/320820043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

[patch] Add a work to "we wrote" list

[Francisco Vila]

Hello,

this adds my PhD thesis to the list in the web. Sorry for not
uploading the patch in a more formal way; I can not recall if I've
done it anytime. I'm willing to, however.

I'll be relatively unreachable for a week. See you on 04/13

Best,
-- 
Francisco Vila. Badajoz (Spain)
paconet.org , csmbadajoz.com
From e7f73583f8bca73c7139023e79b3cde193c1b290 Mon Sep 17 00:00:00 2001
From: Francisco Vila 
Date: Thu, 6 Apr 2017 10:14:11 +0200
Subject: [PATCH] Web: Add a new document to what We Wrote list.

vila01 (2015), PhDThesis
---
 Documentation/web/we-wrote.bib | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/Documentation/web/we-wrote.bib b/Documentation/web/we-wrote.bib
index 922be9ef6c..93ab97d165 100644
--- a/Documentation/web/we-wrote.bib
+++ b/Documentation/web/we-wrote.bib
@@ -56,3 +56,10 @@
   note = {(@uref{http://lilypond.org/website/pdf/lilypond_lac2013.pdf, PDF 890k})}
 }
 
+@phdthesis{vila01,
+  title = {Tipografía musical para la educación y análisis de la dinámica del software libre (Spanish language)},
+  author = {Francisco Vila},
+  school = {Universidad de Extremadura},
+  year = 2015,
+  note = {(@uref{https://paconet.org/wiki/index.php?title=Tesis, PDF 20M})}
+}
-- 
2.11.0

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel