Case sensitive keywords auto-completion #87
Comments
Not sure it is related to #1. At that time the problem was that there was a mode that was converting any key pressed to upper case, meaning it was impossible to type in lower case. This was not related to auto completion. At that time we agreed that:
That's why auto completion propose reserved keyworkds as UPPER CASE. |
Instead of having both versions (upper case and lower case) as you suggest. I would prefer to have an option that let you choose your preferred convention. |
Yes, it's a convention and it should be better to let the user choose it (I don't know a lot of languages where we have to put the keywords uppercase, and I find that disturbing in my code, and problematic when you are on a mainframe/as400 where you cannot use CapsLock because it affects some commands) |
Right. Then let's add that option. All I have to do is to check the setting and transform any keyword to lower case here: https://github.com/pyQode/pyqode.cobol/blob/master/pyqode/cobol/backend/workers.py#L45. |
Yep it works, thanks! |
Good catch! I think this is a bug I introduced in a recent commit where I improved the names parser (it used to respect the original case). I don't have a test for lower case variables at the moment so this bug was undetected. |
Should be fixed now (and I added a test). You need to upgrade pyqode.cobol from source checkout. |
Le 22/12/2014 13:32, Colin Duquesnoy a écrit :
Yep it works thank you! |
This issue is related to issue #1.
OCI proposes to auto-complete lower variable name with upper names, for example
end-
suggestsEND-PERFORM
but notend-perform
.A quick fix could be to add the lower names into the keywords in pyQode:
https://github.com/pyQode/pyqode.cobol/blob/master/pyqode/cobol/api/keywords.py#L105
The text was updated successfully, but these errors were encountered: