-
Notifications
You must be signed in to change notification settings - Fork 299
Feature/remove commandline timeout #2334
Feature/remove commandline timeout #2334
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2334 +/- ##
==========================================
+ Coverage 37.34% 37.58% +0.23%
==========================================
Files 298 299 +1
Lines 12352 12472 +120
Branches 1632 1645 +13
==========================================
+ Hits 4613 4687 +74
- Misses 7490 7536 +46
Partials 249 249
Continue to review full report at Codecov.
|
@bryphe this PR should address the performance issues raised in #2329 as well as the tab highlighting, running it locally with no issues. Re. codecov I think it's not quite picking up salient changes as other than some styling tweaks, shuffling the same code to different and some deletions I haven't really made any changes that should drop the coverage (though it seems to..) can always remove the styling changes (they just mean the component would hide if its parent were hidden rather than be re-created every time) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just gave this a quick test!
The highlight worked fine, and the commandline worked as expected.
My custom binds needed updating to use <cmd>
, which we already knew, but perhaps worth tagging this PR as "breaking-change", such that @bryphe sees it and knows to call it out in the next release.
Is this alright to merge @bryphe I'm planning to add a section to the docs to explain using a |
Go for it! If both you and @CrossR are cool with it, I'm cool with it too 😄 👍
A section in the docs would be great! I'll link to it in the release notes for the next release. |
Following on from #2329 this PR removes the commandline menu's timeout and adds a special case to the tab color to handle commandline mode (aka same color as normal mode is used).
As I mentioned in #2329 the plan would be to add some documentation about using
<silent>
or<Cmd>
to prevent any flickering. I think its arguably safe to say users using thecommandline
with mappings aka those who hit this bug are likely to be users who would be comfortable making the required changes to their mappings...I've left off the changes re. keeping the elements vs. destroying them as at a glance this will require a much bigger/ less straightforward change than I currently can spare the time for