Bug 408100 - auto-brackets false; Please also don't "try to be smart" and consume the bracket characters I type during composition.
Summary: auto-brackets false; Please also don't "try to be smart" and consume the brac...
Status: RESOLVED DUPLICATE of bug 407852
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 19.04.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-30 09:12 UTC by Michael
Modified: 2019-06-01 16:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2019-05-30 09:12:57 UTC
I find that, not infrequently, when editing I run across cases where, if my sequence of typed updates were obeyed, the results would have been what I wanted, but instead some characters are not entered as I have typed.


Automatic whitespace when I hit enter?  Yes please.

Automatic SYNTAX, Please, No.  Please obey the comment I've saved with the file at the top of the file and never add or FAIL to add printing I type.

Steps to reproduce.

* Begin editing a new file
* add a line similar to this reasonably near the top: # kate: replace-tabs on; indent-width 4; tab-indents true; tab-width 4; indent-mode python; auto-brackets false; bom false; eol unix;
* Save the file as whatever.py
* type something in the file like... whateverFunc()
* move inside the () (to the middle).
* Type an additional )

This is now eaten, even though auto-brackets is false; auto-brackets being disabled should also NOT automatically try to out-think the operator when preventing the additional of typed material.

I think this might also be related to a not-quite similar bug in kdevelop, 370716 however in my case it's more that turning things off doesn't actually turn them all the way off and restore sanity.
Comment 1 Dominik Haumann 2019-06-01 16:04:21 UTC
Known regression and already fixed, sorry.

*** This bug has been marked as a duplicate of bug 407852 ***