Re: Volta enhancements tranche 1 (issue 6398055)

[Phil Holmes]

----- Original Message ----- 
From: "Ian Hulin" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, July 18, 2012 6:48 PM
Subject: Re: Volta enhancements tranche 1 (issue 6398055)


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18/07/12 14:54, Phil Holmes wrote:
> > ----- Original Message ----- From: "Ian Hulin" <address@hidden>
> > To: <address@hidden> Sent: Wednesday, July 18, 2012 2:50
> > PM Subject: Re: Volta enhancements tranche 1 (issue 6398055)
> >
> >
> > > Hi Arnold, On 18/07/12 09:16, ArnoldTheresius wrote:
> > > > David Kastrup wrote:
> > > > > ... Disagree.  That sort of symbol should count as silent
> > > > > when reading IMO, even if you might spell it out in phone
> > > > > dictation.
> > > > >
> > > > > http://codereview.appspot.com/6398055/
> > > > >
> > > > > _______________________________________________
> > > > > lilypond-devel mailing list address@hidden
> > > > > https://lists.gnu.org/mailman/listinfo/lilypond-devel
> > > > Just some quotes from notation.pdf ("old" version 2.15.37):
> > > > "An \autoBeamOff call in the first arbument of partcombine ..."
> > > > "... brace of the next in an \alternative block, otherwise ..."
> > > > "... occurring in an \adQuote command ..." "... custos with an
> > > > \override if desired, ..." "When an \augmentum dot appears ..."
> > > > "... by naming them on an \include statement." "... will insert
> > > > an \allowPageTurn at the final bar line ..."
> > > >
> > > > Common practice seems to vote for 'silent' backslash, just as
> > > > David said.
> > > Oh joy, another slice of inconsistency, I've got used to reading
> > > the commands the other way mentally as the docs go to great
> > > lengths to index then all under '\'. Nice catch for arbument,
> > > David, Cheers, Ian
> >
> > Not exactly:
> >
> > http://code.google.com/p/lilypond/issues/detail?id=855
> Oh greater joy, issue 855 seems to have fizzled out as wibble, worse
> it seems to be a continuation from issue 788.
>
> Looks like a case for a GOP topic - do we already have one on the
> queue, Graham?
>
> If not, here's one to kick things off:
>
> Proposal
>
> The current set of indices in the NR of the format \<command> should
> be replaced with a single entry stating "for LilyPond commands, please
> see the entry below under the entry for the command without the '\'
> character, e.g. for '\score' see the index entry 'score'."
>
> Each command will then appear under an entry without the \ in the main
> command index.
>
> Related Issues/Proposals
>
> Discussion on current structure of indices LilyPond Command Index vs
> LilyPond Index - restructure to LilyPond Commands - LilyPond Variables
> - - LilyPond Concepts?
>
>
> Implementation
>
> <tbs> by a grown-up who understands how the docs are compiled.
>
>
> Cheers,
>
> Ian


My understanding was that there was a desire to index /foo and foo as the 
same, and have a single index.  You want to fix that, go ahead.

--
Phil Holmes