I can confirm the command pallete grows as well on OSX 10.12.6
Another bug I’ve found: My HTML and PHP syntax highlighting suddenly stopped working:
error: Error loading syntax file "Packages/HTML/HTML.sublime-syntax": no such target scope:source.css#rule-list-body
error: Error loading syntax file "Packages/PHP/PHP.sublime-syntax": no such target scope:source.css#rule-list-body
Any clues ?
This “issue” was discussed several times recently. It is caused by disabling the default CSS.sublime-syntax which was proposed by the CSS3 author. HTML and PHP rely on the default CSS syntax.
but then those scopes should be part of the guidelines and included in the default color schemes
It’s up to the core devs, but would like to see that, too.
Given the thousands of legacy color schemes …
New sublime-color-scheme format will change a lot anyway, including easier patches for plugin specific features without duplicating whole color-scheme files.
see region.colorish as a reliable fallback
The region.colorish would still need to be supported by plugins, which would need to add a couple of scopes instead of a single one, then to support region.colorish next to markup.. Don’t think it would improve anything but just move the requirement of defining a couple of scopes from color-schemes to plugins.
I agree with this sentiment, which is why you can (probably?) specify the scope to be used in e.g. add_region and syntaxes as region.redish markup.error and if the scheme doesn’t define a color for markup.error it falls back to region.redish. I do not know whether these are active for syntax definitions however.
Cool feature. The new command pallet adds a lot of value.
Based on the provided examples a Preferences command could new be added, which suggests the available settings files. This way all package settings were accessible without the need for each package to provide its own “edit_settings” command definitions.
Here is a simple example of a modified settings.py to achieve it.
{ "caption": "Preferences", "command": "edit_settings" },
import re
import os.path
import sublime
import sublime_plugin
class BaseFileInputHandler(sublime_plugin.ListInputHandler):
PACKAGES = "${packages}/"
# The pattern to extract the path and basename of a file.
SETTINGS_RE = re.compile(
r"(?i)Packages/(.+/)(.+?)(?: \(.+\))?(\.sublime-settings)")
def name(self):
"""Return argument name."""
return "base_file"
def placeholder(self):
return "Settings File"
def preview(self, value):
"""Show the full path in the preview area"""
if value:
return sublime.Html("<b>File:</b> " + value[len(self.PACKAGES):])
else:
return None
def list_items(self):
"""Create a list of unique available settings files."""
names = []
items = []
for f in sublime.find_resources('*.sublime-settings'):
path, name, ext = self.SETTINGS_RE.match(f).groups()
if name not in names:
names.append(name)
items.append((name, "".join((self.PACKAGES, path, name, ext))))
return items
class EditSettingsCommand(sublime_plugin.ApplicationCommand):
def input(self, args):
if "base_file" not in args:
return BaseFileInputHandler()
else:
return None
def run(self, base_file, user_file=None, default="{\n\t$0\n}"):
... # the rest is unchanged
Now the command palette is using sublime.KEEP_OPEN_ON_FOCUS_LOST, but on the last build 3153 it was not the behavior.
I’ve been commenting on this very thing here: .sublime-color-scheme and region.colorish
I think this is broken. This is for Vue.js. I have the Vue plugin installed. Latest version of ST 3154. Theme is Monokai (the one that comes installed with ST). I believe this was working in the previous build.
I tried testing it with Mariana and Breakers and I come across the same result.
What would you suggest ?
Thanks
See this issue.
It looks like the Vue syntax, which was never updated to the sublime-syntax system, is embedding the JavaScript syntax in a very brittle way. This left it vulnerable to changes in the internal implementation of that syntax. The Vue syntax needs to be updated to include the JavaScript syntax in a more robust manner. This will fix this bug and forestall any future problems that might otherwise result from changes to the JavaScript syntax.
Alternatively, you can put a semicolon after the closing brace. It’s technically mandatory, although the automatic semicolon insertion algorithm will muddle through regardless.
@ThomSmith It works after adding a semicolon. Thank you, Sir.
I have a request please (I am not sure if you have already done so and if you have some spare free time ), can you please help fix this case in the vue component package , please ?
I would fore ever be beholden.
Thanks
I’ve tested 3154. There is a regression, – content_margin of overlay_control doesn’t work.
Steps to reproduce:
{
"class": "overlay_control",
"layer0.tint": [255, 0, 0],
"layer0.opacity": 1.0,
"content_margin": [50, 10]
},
Also it would be great to have max width option for command palette.
[quote=“addons_zz, post:28, topic:33286, full:true”]
You should use double star ** for exponentiation[/quote]
@gj1118
Furthering this: With the Arithmetic command, Python’s math class module’s constants and functions can be accessed using the math. prefix, e.g. math.sqrt(81), math.pi. Note: ST3 uses Python v. 3.3 so functions added to the math module later than that will not work, e.g. math.gcd(a, b).
With the new Command Palette if the cursor is not already on the far right of the entered text, e.g. the user has moved the cursor left to correct a typo letter, then the next time the down key is pressed the cursor jumps to the end of the entered text instead of scrolling down one item in the list of commands. Note that the opposite does not happen when pressing the up key. I suspected that this might be related to the move_to_limit_on_up_down setting, but it happens even when that setting is false.
Confirm this behavior. Would like to see up+down to select the prev/next item in the list immediately, too.
