Graham Percival wrote:
> But not until later, pending one of the long discussions
> I'm waiting to introduce on -devel.
Oh, *great*...
;)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Sun, Jul 26, 2009 at 02:31:15PM +0200, Nicolas Sceaux wrote:
> Le 25 juil. 09 à 11:39, Dénes Harmath a écrit :
>
>> On 2009.07.23., at 21:58, Mark Polesky wrote:
>>> This suggests that the command is derived from "hideNotes":
>>> "un" + "hideNotes" = "unHideNotes"
>
> But then \set and \unset ar
Le 26 juil. 09 à 14:56, lilypondt...@organum.hu a écrit :
Also for a user syntactic keywords and variables are
indistinguishable.
No, they aren't. A user can change a variable value.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists
The general rule in the CamelCaseWorld is to change the case on word
boundaries.
In this sense I also think that unhideNotes should be unhideNotes.
Also for a user syntactic keywords and variables are indistinguishable.
(And not just for users, as if I remember well \override is a music
function
Le 25 juil. 09 à 11:39, Dénes Harmath a écrit :
On 2009.07.23., at 21:58, Mark Polesky wrote:
This suggests that the command is derived from "hideNotes":
"un" + "hideNotes" = "unHideNotes"
That logic isn't applied in the case of \set and \unset. That's why
I am (and
maybe also others are)
On Sat, Jul 25, 2009 at 09:34:09AM -0700, Mark Polesky wrote:
> Dénes Harmath wrote:
> > Sorry for nitpicking about syntax issues, but a consistent
> > convention is easier to remember.
Yes.
> Anyone else care to comment?
Yes, but not at the moment. There's three *major* changes
happening in li
