Version: (using KDE 4.3.0) Installed from: SuSE RPMs Auto completion in kate/kwrite is very inconsistent in the way it works compared to the kde3 version. In kde3, though annoying at time, auto completion worked on every word, every time. In kde4, just the opposite is happening. Realistically, auto-completion works correctly about 30% of the time. 40% of the time is will not complete the word (variable) you want it to complete, and the remaining 30% of the time, auto-completion is hit-or-miss working sometimes and then not for the very same variable. Auto-completion is enabled with the default minimum word length to complete set at 3 (default). The link below is a kate screenshot showing the cursor immediately after: cp $k $DUPD where $DUPD should be auto-completed to $DUPDIR but kate will not complete the word no matter what. Whatever is preventing auto-completion from doing its job needs to be fixed. Like I said, though slightly annoying, in kde3 auto-completion worked every time for every word over the minimum completion length, consistently and every time. Auto-completion in kde4 is "like a box of chocolates", you never know what you are going to get. This is much more annoying than knowing what to expect. If you can think of a test to help narrow down the problem, let me know and I'll be happy to run it. Thanks.
Created attachment 35983 [details] Screenshot showing no completion Sorry, I forgot the screenshot. Here it is attached and at: http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kate-completion.jpeg
Same problem here. Although switched on, one often needs to press C-Space to get auto-completion which is very annoying. I'm not quite sure when exactly completion works and when it needs to be triggered manually. Example: type the following: $myvar->thisIsATest(); $myvar->this Now "thisIsATest" should be auto-completed! Even more stange: if you now add a space and type "this" again $myvar->thisIsATest(); $myvar->this this then Kate does auto-completion: $myvar->thisIsATest(); $myvar->this thisIsATest Now hat C-Backspace to delete the thisIsATest and type Backspace to remove the space. Not type I - and Kate will happily auto-complete the word it didn't auto-complete before!
I'm going to look into this, since it annoyes me like hell too. If I remember correctly, for the completion to kick in there is a start threshhold of three or four typed characters and the word has to have at least three furher characters. I often get the feeling, that the start treshhold is only evaluated correctly after a backspace key press or if the characters of the start threshold are typed very fast. As said, I'm going to investigate that.
Experiencing the same bug on Gentoo, kate-4.3.0 Driving me slightly crazy :P
Same problem here, using opensuse KDE 4.3.1, rpm version: kate-4.3.1-78.2 It depends on where you are coming from when you type. Relocating the cursor helps. Typing in PHP: $foo->fubarMethod(); $foo->fubar [no word completion] Press right arrow, left arrow, backspace, then 'r': word completion appears.
With KDE 4.3.2 these problems are still experienced. Since it worked fine and quick in 4.2 series, could changes to word completion in Kate be reverted?
I'm having the same problem in Kubuntu. I filed a bug in launchpad: "auto completion in kate is slow and unreliable" https://bugs.launchpad.net/bugs/440916
Still present in KDE-4.3.3. Is there any info we can give to help get this fixed? It's my least favourite feature of KDE 4.
Still present in Kate 3.3.3, KDE 4.3.3 release 1, opensuse 11.1. See my previous post for an easily reproducible case - fails every time. It looks like the highlighter fails to realize that we have left one word ($foo) and started on another (fubarMethod).
Still present in Kate 3.4.0, KDE SC 4.4.0.
I voted on it many moons ago. On Thursday 11 February 2010 12:48:41 Nick W wrote: > https://bugs.kde.org/show_bug.cgi?id=203039 > > > > > > --- Comment #10 from Nick W <nick customdesigns ca> 2010-02-11 20:47:03 > --- Still present in Kate 3.4.0, KDE SC 4.4.0. >
with regard to comment #5: typing fub, the completion shows up. typing a, completion is still there. when typing the 'r', completion hides, because it completed the word currently seledted in the popup. If you previously select the word fubarMethod in the completion popup, it will not hide. In other words, the behavior of the completion list is rather smart in this case. I bound Tools > Invoke code completion to ctrl+space. Whenever I want the completion I simply hit this shortcut and the popup shows up. Hence, is this really a bug or even the correct behavior? Maybe it should indeed show the remaining words. Is that what the report is about?
(In reply to comment #12) > with regard to comment #5: > typing fub, the completion shows up. typing a, completion is still there. when > typing the 'r', completion hides, because it completed the word currently > seledted in the popup. If you previously select the word fubarMethod in the > completion popup, it will not hide. In other words, the behavior of the > completion list is rather smart in this case. This behaviour sounds fine, but it's not the behaviour I'm seeing. To clarify, as I type the second line of my example, there is no auto completion popup at any point. Not until I do the magic relocate cursor trick: - type '$foo->fubarMethod();' - type '$foo->fuba' (bug: no popup) - arrow right, arrow left - type 'r' (ok: popup shows) Wild guess: It looks like the autocompleter is being disabled in some contexts (perhaps in the '->' string) but it isn't enabled again when it should be. The arrow right, arrow left trick seems to fix the context and enable the autocompleter again. > I bound Tools > Invoke code completion to ctrl+space. Whenever I want the > completion I simply hit this shortcut and the popup shows up. Hence, is this > really a bug or even the correct behavior? Maybe it should indeed show the > remaining words. Is that what the report is about? No, it is about the failure to auto popup the completer in certain situations, as described.
Ok, please build Kate yourself with the following howto (is very easy!): http://gitorious.org/kate/pages/Building%20Kate Does it work with the development version?
First, I tried upgrading to KDE 4.4.3, this did not change the behaviour. (In reply to comment #14) > Ok, please build Kate yourself with the following howto (is very easy!): > http://gitorious.org/kate/pages/Building%20Kate > > Does it work with the development version? Yes! I get the autocomplete popup as soon as I have typed 'fub'. Thank you very much!
Great, then we have a fix :P KDE 4.5 will contain it ;)
Whilst this worked great in 4.5 it seems to have reverted to its previous sporadic behaviour now I'm using 4.6.3 (kate 3.6.3). As before it s the auto popup which fails, using ctrl-space works ok, so in the exampl above:- $foo->fubarMethod(); $foo->fub <fail no popup> but $foo->fu (move off line then back to line - i.e. up/down or right/left) b <popup appears>
(In reply to comment #17) > Whilst this worked great in 4.5 it seems to have reverted to its previous > sporadic behaviour now I'm using 4.6.3 (kate 3.6.3). This issue you are describing is most likely the one tracked in bug 266708. Please update to KDE 4.6.4 - it's fixed there.
Thankyou, indeed it is, sorry for the noise.