You and I have very different definitions of “same”.
If the keyboard shortcuts where just “use ctr instead of command” I’d probably agree with you, but the shortcuts are changed dramatically between the 3 systems.
For example, replace uses F on Mac, but H on windows.
Als i sometimes still accidentally start ST3 and i cant seem to disable the update check? I have tried a bunch of google answers but it still pops up, anybody else had/has this?
I've been using VS Code for years now, and while it is measurably slower (I still use sublime to handle ad-hoc grepping log files as code just won't handle that, and scrollable, highlighting and multicursor is MUCH better than smacking bash pipes together), the batteries included "It just works" approach of code means I don't really see a reason to head back.
Maybe it's changed since the sublime 2/3 days, but the packages ecosystem always felt a bit unpolished and anemic.
>Maybe it's changed since the sublime 2/3 days, but the packages ecosystem always felt a bit unpolished and anemic.
As far as I can tell it's only gotten worse. The rise of Atom and then VS Code sapped a lot of the energy that went into creating plugins.
If I want to edit config files for basic things, isn't vim better? And if I want more power, isn't an IDE better? At this point I honestly like Atom more than Code. Even on Linux.
The packages ecosystem is fine and always has been.
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.
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 :)
Also Sublime-LSP is awesome.
In his documentation he mentions that he made the plugin in part because he did not want Paredit mandated by a plugin. I was curious to see what kind of structural editing he used instead, so I tuned into one of his streams. Turns out he just writes raw lisp in sublime text, and he's fast as hell at it too.
Since then I've been trying out using Sublime for Clojure development and falling back on Intellij when I need anything more than basic inline/REBL debugging, and I'm very happy with it so far.
I also started using sublime Merge recently and I think I may feel the same way about it
That used to be my reason for not using VSCode, but then I started using this: https://marketplace.visualstudio.com/items?itemName=ms-vscod...
I really still like sublime for editing text or log files on my dev system, but not for development.
I know new engine is supposed to speed up rendering, but on my linux boxes, everything feels slightly slower than before.
Not a big deal for an IDE or IDE light, but for what I use sublime for (quick text editing), it's a disappointing change.
VSCode is excellent, but I don't think that I do enough of the kind of coding that VSCode is optimized for, to make it worth it.
When it notified me about the version 4 license change, I was ready to make the purchase. However, it has been a while since then and, besides the "LICENSE UPGRADE REQUIRED" text on the top right corner, I still can't notice any restriction. The current installation still has my license purchased for v2 applied. I just upgraded to build 4126 today and it worked fine. Am I misunderstanding the licensing terms or is this a bug?
You're expected to purchase a license if you continue to use the software.
They're just asking nicely instead of crippling their software after an arbitrary time limit.
Though for day to day, i switched to nvim and neovide (rust frontend). Given that, I guess I spent too much money on text editors ...
Yes it's slower and clunkier but the extensions ecosystem is worth it. And also features like intellisense, unused vars, automatic updates of imports on file renames, and a long etc of QOL features ST doesn't have interest or capacity in implementing.
I write my Ruby and Elixir code with it, even if I know I get better experience with other tools.
I wrote my book Deployment from Scratch with Sublime as well.
I sometimes evaluate other editors but so far always returned :).
build 4119 works fine though
E: misspelling
In light of the above, it makes sense for it to be proprietary and closed source.
Were it open source, people could fork it and distribute it freely, with no remuneration going back to the developers. I doubt the developers could offer any other incentive such as support to make up the shortfall.
"Source available" licences where the user is prohibited from providing the software to others doesn't meet the FSF's definition of freedom, so even that wouldn't please everyone.
As one of the people supporting it’s continuing existence, I think there will be more focus on what I need. For open source projects, the focus will be (and should be) on what the people putting in the time and money need.
There’s considerable overhead (in terms of optimizing workflows) to switching editors too, so just because an editor is good for today doesn’t mean it will be good tomorrow. Not that proprietary editors can’t change in a way negative for me. I just figure it’s less likely and, over time, will happen less often.
Of course, I could have the perfect editor by doing my own, but it’s orders of magnitudes less effort to pay someone $x. (Personally, I think sublime should go to a subscription model. Pay per release encourages feature bloat, which I do not want in a text editor.)
It's just so much faster than every other GUI editor, even VSCode which is "tolerable". I can open multi-gigabyte XML files without bringing my computer to its knees. The extension ecosystem is pretty weak compared to VSCode but it does what I need. And something is just better about the way Sublime renders text. It's easier on the eyes. And the multi-line / multi-cursor editing flow is better.
I still pull out other editors if I need some advanced refactoring or debugging feature but if I can avoid it, I do.
I must have overlooked this. While most of my programming is over ssh with vim, I’ve very much enjoyed Sublime on my own systems. Minimalism and unobtrusiveness has been very appealing to me. Free software is more important, though, so perhaps it’s back to vim, then.
I wish that the Xi editor was maintained more efficiently than it is.
Are you aware of good IDE’s besides vim and emacs? What do you use? I love vim but sometimes I just want something “friendlier” for a change.
A lot of people swear by jetbrains. I'm still a newb with it but I can see it being useful. But I learned to not hold my shift key too much (and disable defaults). Search everywhere is nice but difficult to use if you have motor difficulties.
- Linux: gedit, geany
- macOS: TextMate
- Windows: Notepad++
And the one to rule them all: emacs (also gvim).