@burakcalik, can you try out @r-stein solution? At the time, I did not had though about using ChainOfCommands package at the time I wrote the original solution.
I had added the fix file on another package I already had: https://github.com/evandrocoan/ClearCursorsCaret you can install it manually on the user’s folder. Currently this package is not on package control, its integration request is pending review on: https://github.com/wbond/package_control_channel/pull/6690
@r-stein Ah it works great! Thank you very much. I only had to modify the ctrl to super because I’m on MacOs.
@addons_zz Thank you too!
<3 just came here to look for a fix, thanks for restoring/fixing this. Frustrated me a few times daily 
Most likely when I finish fixing the issue with macOS ramping up the CPU when a user’s opengl renderer switched and they are using a full-size content window (to have colored title bars).
I am using Fira Code on OS X.
With the Elixir syntax highlighting, it works for pretty much everything but does not support ▷ ligature.
See attached image:
Is there any time estimation on that, since this build has been out for weeks, and it’s still killing productivity.
Thanks for addressing this anyway, but I’ve been checking for updates multiple times a day.
<3
No, I’m working on the third new implementation to try and meet the performance we need, but also work around the bug in macOS. If it is causing issues for you, I’d recommend rolling back a build, or moving to the stable build.
I assumed it was imminent, but that’s my fault. In that case I’ll rollback a version.
Thank you for your work. And best wishes on that nasty issue you’re working on.
Just rolled back to 3143 (stable) but the problem persists. It keeps the previous command around. Whats up with that? I really don’t want to always remove the previous command before typing a new one.
On build 3143 the command is initially selected like this:
Then you only need to type something and the command is erased. If you reverted to build 3143 and the command is not initially selected, it mean that you do not reverted to build 3143. If you enter on the About command, what is the version you see?
You are right! Thanks for clarifying that, I was going crazy not understanding where it was breaking or how it was working before. Really appreciate the details about the issue.
Thanks to the team for all your great work.
To anybody who wants to stay on the dev channel, but wishes to roll back a build, just download the package manually:
curl -O https://download.sublimetext.com/sublime-text_build-3155_amd64.deb
sudo dpkg -i sublime-text_build-3155_amd64.deb
(adjusting for your OS and architecture) and then avoid upgrading until the next one comes along.
For anyone reading this, the (I hope temporary) fix is:
{
"keys": ["super+shift+p"],
"command": "chain",
"args": {
"commands": [
["show_overlay", { "overlay": "command_palette" }],
["select_all"],
]
},
},
Might want to try this package https://packagecontrol.io/packages/ElixirSyntax
The official package uses tm syntax, which is not as easy to maintain or update as sublime syntax definition.
Command Pallet: the previous behavior, previous command text highlighted … was PERFECT. please revert or add an option
THANKS
Bump. This behaviour change is amazingly annoying on a minute-by-minute basis, any estimate on when we might get a fix?
No, I can’t estimate accurately. If I did, I would have given you two dates that I would have missed so far! Unfortunately the heavy CPU issue that I am working on fixing on Mac has been quite a challenge to work around.
I would recommend rolling back a version or two until the next dev build happens.