When at the first autocomplete result, pressing up will wrap around to the last result, and vice versa.
This does make test 56 (completion_test) fail with an "Exception: Child aborted" - I'm looking into it.
sraizada |
KTextEditor |
When at the first autocomplete result, pressing up will wrap around to the last result, and vice versa.
This does make test 56 (completion_test) fail with an "Exception: Child aborted" - I'm looking into it.
Lint Skipped |
Unit Tests Skipped |
What happens if the overload selection window is open in addition (like in KDevelop)?
I only use Kate/KWrite so didn't test it on the others previously - sorry.
It actually only works in Kate and KWrite, and has no effect on Kile/KDevelop. KDevelop is obviously doing some special stuff, but visually the Kile autocompletion seems identical to the one in Kate/KWrite so I'm surprised that it doesn't work.
Any idea what's causing this issue or where I should look in the KDevelop code?
I think the idea was that it is an easy way out of the completion.
I am not sure if wrapping is what one would expect.
Indeed, question is if wrapping helps: If you see 5 entries, and you see the last one is correct, then moving up would be ok.
But if the completion contains >> 10 entries, this will not work. And then, there is still the "End" key on the keyboard as dedicated action.