Re: Lilypond case-insensitivity (was: shall we rename X-offset)

[Eluze]

janek.lilypond wrote
> Uh, have you read David's email
> http://lists.gnu.org/archive/html/lilypond-devel/2013-03/msg00448.html
> ?

sure, but honestly I can't see how the locale would interfere when
internally you change from/to upper-/lowercase.

> The conversion between cases isn't as trivial as it seems.
> 
> I've reread previous discussion about case (in)sensitivity, and i can
> say that making Lily case-insensitive really looks like a bad idea: if
> we did this, significant amount of bugs and inconsistencies would
> appear.  Many of them would be hard to predict and they'd cause us a
> *lot* of trouble.  Please trust us (i.e. David and other experienced
> developers) that the benefits of case-insensitivity are not worth the
> troubles it would bring.

I trust both of you and I won't insist on case-insensitiveness, specially if
the scenario you draw can be improved:

> Nevertheless, there *are* other things that we could do to make
> case-sensitivity more bearable.  LilyPond could give users hints about
> spelling, for example if someone wrote \stemUP, LilyPond could say
> something like "unknown string \stemUP.  Did you mean \stemUp?".  That
> would be a good feature request.

if "the computer" can give an unique alternative he should write a
warning/error message and continue work.

> Also, editors like Frescobaldi could provide some kind of
> "LilyPond-spellchecker" that would correct wrongly spelled commands.

Frescobaldi is also behind schedule (e.g., when I checked not many weeks
ago, \omit or \single were not yet implemented)
I wonder how they update their lists.

> I think that such functions would greatly help users who struggle with
> case-sensitivity, …

… and other spelling problems (is it color or colour? etc.)


the problem is that LilyPond doesn't provide a full list of all

keywords
commands
music-functions
grobs
properties
internal options (the equivalent to doptions)
pitches
contexts
engravers
glyphs
scripts
languages
paper/header/layout … variables
(and probably a few more items)


since at least 2.12. I'm using my own hiliter and auto-completer (with NP++)

for that I had to extract above values from

- pdf/html manuals 
- definitions in …usr/share/current/… .ly and .scm
- …/current\vim\syntax

and feed that to the auto-completer and hiliter and, indeed, it is of great
help.

but it is much recurring work and it isn't complete at all.

so I would be very glad if such a repository could be added in future and
generated for each new release!

thanks
Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Lilypond-case-insensitivity-was-shall-we-rename-X-offset-tp143393p143410.html
Sent from the Dev mailing list archive at Nabble.com.