Dev Build 3156

[spd]

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]

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

Issue: Does not support ▷ ligature

[sexybiggetje]

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]

Is there any time estimation on that, since this build has been out for weeks, and it’s still killing productivity.

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]

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]

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]

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]

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]

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.

[s_mcleod]

For anyone reading this, the (I hope temporary) fix is:

1. Install the package ‘chainofcommands’
2. Add the following to your keybindings:

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

[prmaple]

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.

[malloc]

Command Pallet: the previous behavior, previous command text highlighted … was PERFECT. please revert or add an option
THANKS

[spd]

That’s perfect - thanks!!

[315234]

Bump. This behaviour change is amazingly annoying on a minute-by-minute basis, any estimate on when we might get a fix?

[wbond]

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.

[wbond]

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.

Can you provide some more info about your platform and configuration? I’ve tried to reproduce on Windows (2x dpi_scale) and Mac, but haven’t seen it yet.

[crodgers]

[
    {
        "caption": "ExampleCommand",
        "command": "example_command"
    },

    {
        "caption": "Preferences: Example Command Settings",
        "command": "edit_settings", "args": {
            "base_file": "${packages}/ExampleCommand/ExampleCommand.sublime-settings",
            "default": "${packages}/User/ExampleCommand.sublime-settings"
        }
    }
]

Gives me an error:

TypeError: run() got an unexpected keyword argument 'default'

Most of my plugins now give this error if I try to edit the settings from the command palette.

[wbond]

Most of my plugins now give this error if I try to edit the settings from the command palette.

Does this happen if you revert to a fresh state? If not, it may be a customization of the edit_settings command.

[crodgers]

How do I achieve a fresh state? I’m pretty new to plugin dev.

EDIT: Found it. Will update when i figure it out.

[wbond]

If you check out Resources and Bug Tracking, it has a link to reverting to a fresh state, plus links to the bug tracker, default package repository, etc.