Sublime Forum

**bofm** · December 7, 2017, 7:51am

+1 Command Palette behavior is broken in this build. I believe the previous command text was preselected in the last 5 years.

**Narretz** · December 7, 2017, 2:42pm

This will be fixed in the next build, see Dev Build 3156

**addons_zz** · December 9, 2017, 3:32am

After restarting Sublime Text the command palette input text is lost. On build 3143, it is preserved.

**deathaxe** · December 19, 2017, 3:47pm

The place holder in the new command panel seems not to be rendered at the correct vertical position. Is this something which can be tweaked by the theme or is it to be optimized by the core?

Would be nice, if pasting the placeholder’s text would only cause the color to change, not the text to move down by about 2 or 3 pixels.

**burakcalik** · December 14, 2017, 2:48pm

@addons_zz could you please release it on PackageControl.io? I tried to run your plugin code, but It did not work. And this issue driving me crazy.

**r-stein** · December 14, 2017, 2:52pm

@burakcalik If you just want to have the old behavior install ChainOfCommand (for easy macros) and add this keybinding:

{
    "keys": ["ctrl+shift+p"],
    "command": "chain",
    "args": {
        "commands": [
            ["show_overlay", { "overlay": "command_palette" }],
            ["select_all"],
        ]
    },
},

**addons_zz** · December 14, 2017, 11:13pm

@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

**burakcalik** · December 14, 2017, 11:51pm

@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!

**sexybiggetje** · December 18, 2017, 1:09pm

<3 just came here to look for a fix, thanks for restoring/fixing this. Frustrated me a few times daily

**bizoo** · December 18, 2017, 2:56pm

When the next build planned ?
This bug is really annoying…

**wbond** · December 18, 2017, 3:39pm

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).

**spd** · December 20, 2017, 1:28pm

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:

**kingkeith** · December 20, 2017, 1:31pm

the correct place to log it is on the Elixir package’s issue tracker:

**sexybiggetje** · December 20, 2017, 2:35pm

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

**wbond** · December 20, 2017, 2:37pm

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.

**sexybiggetje** · December 20, 2017, 3:06pm

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.

**mhenrixon** · December 21, 2017, 1:12pm

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.

**addons_zz** · December 21, 2017, 3:01pm

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?

**mhenrixon** · December 21, 2017, 3:13pm

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.

**etatoby** · December 22, 2017, 2:32pm

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.