Developer at Sublime HQ here, pleasant surprise to see this stable build reach the front page :)
If you have any questions related to ST or otherwise feel free to ask.
If you have any questions related to ST or otherwise feel free to ask.
That's the only thing that stands between me and buying ST.
It could be useful to open a feature request for 'code-based' folding, if the existing 'text-based' one is considered to be working as intended. That way we're not fighting over a definition but rather showing demand for a new capability that everyone would agree is absent.
https://github.com/sublimehq/sublime_text/issues/101
Editors like visual studio IDE properly fold code so that it results in a compact layout once it's folded. I would guess indentation-based folding could be made more compact and not take unnecessary lines.
I believe Sublime HQ could really bring something in this space, because there are some good existing ones but none are great. Sublime DB could be great :)
e.g.
switch (something) {
case one:
return;
case two:
foo();
break;
}What's your test suite like? Whenever something is regressed in a dev build, do you try to cover it with tests? Or are the UI side of things not tested in an automated fashion?
What are the plans for matching VSCode's useful features, like the one whereby all syntaxes can inject themselves into Markdown fenced code blocks etc?
It'd be great to see some better SQL syntax highlighting support - I saw a community effort on the Packages repo aiming to address this. Will there be a way to switch "active" sql dialect? Or configure it per project?
Thanks, that means a lot :)
> What's your test suite like? Whenever something is regressed in a dev build, do you try to cover it with tests? Or are the UI side of things not tested in an automated fashion?
The UI toolkit as a whole and platform integrations don't have tests, but the core parts like file encodings, data structures, syntax highlighting, etc. are pretty well tested using both integration, unit and manual fuzz tests. We also make heavy use of debug asserts and asan to catch bugs during development.
> like the one whereby all syntaxes can inject themselves into Markdown fenced code blocks etc?
I can't say when, but something like this is certainly on my radar. It seems like a clear incremental improvement on the existing syntax highlighting functionality.
> It'd be great to see some better SQL syntax highlighting support - I saw a community effort on the Packages repo aiming to address this. Will there be a way to switch "active" sql dialect? Or configure it per project?
This one is a lot more tricky as there are various tradeoffs to make. It's in my backlog of things that need to be discussed with other package repository contributors.
Maybe I’m misunderstanding, but I think you can do that with multimarkdown rendering.
# my code example
```python
This = {“codeblock”: “is colored”}
as = [“python”, “code”]
```In v3 I can type “def”, hit Tab and it works right away.
Are you considering adding the option to change auto-compete behavior to what was in version 3?
Thanks for listening and fixing the issue I've requested (handling files renames/deletes outside Sublime).
The only thing I'd like improved would be syntax-aware code folding, and folding support for Markdown files.
We have our own fully custom UI toolkit with a platform abstraction layer. Since we're the only users of this toolkit we have the flexibility to quickly make sweeping changes that can go all the way from the platform, through the toolkit and to the application code. We also generally make platform integration a priority - which you can see from about ¼ of the changelog being platform-specific fixes. This would probably make a good blogpost some day :)