I don't see the point of forcing recognized keyword to be upper case in the
first place.
Syntax highlighting & keyword recognition will be according to user defined
keyword list. If user defined lower-case keyword, those keywords will not be
properly highlighted or recognized after being forcefully uppercased. It's
hampering user experience.
Judging from test, it seems the intension of forceful uppercase conversion is
designed to change user inputted lower-case keyword to upper case. It's
poorly designed, because the lower case input won't be recognized as keyword
in the first place. Hence the upper() function was actually never take any
effect. But even if it functions as it should. Say, user defined a keyword in
UPPER case, and typing in a lower cased version of that word, most likely
they just want them to be non-keyword. I don't want my orgmode to recognizing
each header I have with Waiting as its first word of the sentence to lose
that word as a keyword.
for letters like ß, not all toupper converter behave as standard
indicate. In this particular case, using python2 or vim's built-in
toupper() will obtain ß. Using python3 will obtain SS as standard
indicate.
All in all, the strange forcefully upper-case converting behavior is not
necessary, experience hampering and buggy in more ways than one. Hence I think
why not just get rid of it.
There are several reasons for this.
upper()function was actually never take any effect. But even if it functions as it should. Say, user defined a keyword in UPPER case, and typing in a lower cased version of that word, most likely they just want them to be non-keyword. I don't want my orgmode to recognizing each header I have withWaitingas its first word of the sentence to lose that word as a keyword.ß, not alltoupperconverter behave as standard indicate. In this particular case, usingpython2orvim's built-intoupper()will obtainß. Usingpython3will obtainSSas standard indicate.All in all, the strange forcefully upper-case converting behavior is not necessary, experience hampering and buggy in more ways than one. Hence I think why not just get rid of it.