deathaxe
deathaxe
How about ... ```ruby def symbol_at_point(view, pt): separators = view.settings().get("word_separators", "[]{}():.") symbol = view.substr(view.expand_by_class(pt, sublime.CLASS_WORD_START | sublime.CLASS_WORD_END, separators)) locations = lookup_symbol(view.window(), symbol) if len(locations) == 0: symbol = view.substr(view.word(pt)) locations...
Doing so will again result in `!test_goto_definition?` being computed as symbol lookup candidate as before. The only general solution is probably to expand selection by scope. It won't help in...
The current implementation ignores scopes at all. So even if the function was scoped (correctly), it wouldn't work. But overall behavior - for other syntaxes - could be improved by...
ST's scope naming guidelines don't express current state of implemented scope naming schemes of operators. 1. The `word` scope was designed for syntaxes which primarily use symbolic operators with some...
FWIW, here's an excerpt of TextMate's scope naming guideline: - `keyword` — keywords (when these do not fall into the other groups). - ... - `operator` — operators can either...
This PR is obsolete.
Maybe related with: https://github.com/SublimeTextIssues/Core/issues/2919 Probably fixed by explicitly calling `window.set_focus()` after `window.set_layout()` which has been introduced in the recent commits?
Ignoring the overcomplicated structure, the only thing finally needed is a reference to `repl_open` with correct arguments. The following example shows content of _Packages/User/Default.sublime-commands` to add a REPL for Gambit...
Yes, a `.python-version` file with `3.8` is all which is needed.