Summary: | Unindenting code sometimes doesn't trigger reparse | ||
---|---|---|---|
Product: | [Developer tools] kdev-python | Reporter: | Nicolás Alvarez <nalvarez> |
Component: | Language support | Assignee: | Sven Brauch <mail> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | antonis+kdebugs |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kdevplatform/74926cc388978e376d7ca50d9e1d15bbba6afb81 | Version Fixed In: |
Description
Nicolás Alvarez
2012-05-11 19:07:15 UTC
Git commit 74926cc388978e376d7ca50d9e1d15bbba6afb81 by Sven Brauch. Committed on 10/10/2015 at 15:25. Pushed by brauch into branch 'master'. Fix the WhitespaceSensitivity feature for reparsing. This never looked at removed text ... M +13 -11 language/backgroundparser/documentchangetracker.cpp http://commits.kde.org/kdevplatform/74926cc388978e376d7ca50d9e1d15bbba6afb81 > Very strangely, if I unindent by pressing Shift-Space
> instead of deleting the four spaces, the code *is* reparsed
> immediately, and both highlighting and completion correctly reflect the scope change.
That is because Shift+Tab removes the line, unindents it and then inserts it again. ;)
|