Bug 373008

Summary:	kate/kwrite autocomplete typecast in ternary deletes variable after conditional
Product:	[Applications] kate	Reporter:	David Rankin <drankinatty>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kare.sars
Priority:	NOR
Version First Reported In:	16.08
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Rankin 2016-11-27 22:49:58 UTC

In kate/kwrite in a C source, attempting to insert a typecast before the variable name in the 'true condition' of a ternary causes autocomplete to overwrite/delete the variable name. This is reproducible 100% of the time.

Example, save the following a as a C-source file (e.g. bug.c)

/* attempt to insert (ssize_t) as typecast following '?' with autocomplete
 * will cause autocomplete to delete 'idx' resulting in:
 *
 *   return idx ? (ssize_t : -1;
 *
 * after accepting the proposed autocomplete
 */
return idx ? idx : -1;

Now, with autocomplete enabled, attempt to insert '(ssize_t)' prior to the 'idx' following the '?'. [ e.g. start typing '(ssiidx' ] When autocomplete suggests 'ssize_t in the autocomplete window, hit 'return' to accept the proposal. 'idx' is delete leaving only:

return idx ? (ssize_t : -1;

Comment 1 Kåre Särs 2016-11-28 08:01:56 UTC

Hi,

This is a feature :)

Actually it _is_! Pressing ctrl-z will undo the deletion of "idx", but if you find the feature too annoying you can disable it by removing the tick in Settings-> Configure Kate -> Editing -> Auto Completion -> Remove tail on complete

Regards,
  Kåre

Comment 2 David Rankin 2016-12-03 15:51:54 UTC

OK, Laughing... That's what that option does for which there is no help available or '?' tooltip to determine. Yes, that option is getting unchecked. But KUDOS!!! to the awesome dev that knew "A new feature is a bug if it cannot be turned off!" and was smart enough to provide an option to disable it.

Now, if you can just pass that around to the rest of the KDE team who dream up the latest "gotta have feature" that "everybody will just love..." and fail to include an option to disable it, that would be a huge leap forward.

Good job KDE team on providing user control to this feature.