Re: Volta enhancements tranche 1 (issue 6398055)

[Graham Percival]

On Thu, Jul 19, 2012 at 12:55:41PM +0200, David Kastrup wrote:
> Graham Percival <address@hidden> writes:
> 
> > to remove any backslash from the sort-order but still print the
> > backslash?
> 
> We have @funindex, our own macro.  If we use this (or something else)
> consistently without backslash, the macro definition can, for now, add
> the backslash back.

oh!  I completely overlooked that use of a macro.  Yes, that could
work.

I see a need for an additional macro, though: we'd need something
like
@commandindex repeat
// adds a backslash, places into both indices

@variableindex staff-system-spacing
// does not add a backslash, places into both indices

@cindex repeated music
// does not add a backslash, only places into the concept index.


I've lost track of what we'd achieve by doing this, since this
only applies to the formatting of our doc source and doesn't
actually change the way the doc output.  I'm then have two
concerns about this:
- seeing "@commandindex \repeat" in the source seems that it could
  avoid potential confusion about whether "repeat" in this context
  is an actual \command or not.  The doc source is already
  intimidating enough for casual doc writers.
- it would take a fair amount of effort to go through the docs
  changing existing @funindex \foo to @command foo.  Or maybe not,
  since it just occurred to me that a regex could probably handle
  that.

Still, if the macro isn't going to have an immediate improvement
to the doc output, I don't think it's worth doing.  Unless I've
missed something again.

(checks archives)
... oh wait, the idea was to only index "score" *instead* of
"\score" ?  no, I don't think that's a good idea.  New users won't
recognize the difference between commands and grob properties;
having the backslash is a very useful clue.

- Graham