4 ms·
Interesting, it was mutlicursor bugs in SublimeText that never got fixed the drove me to finally switch to VSCode.
by shkkmo 4y ago
Interesting, it was mutlicursor bugs in SublimeText that never got fixed the drove me to finally switch to VSCode.
- ben-schaaf 4y agoST dev here, what multicursor bugs specifically?
- FredPret 4y ago> ST dev Just wanted to say thank you for a fantastic text editor. It feels like a superpower when I show it to non-tech people
- ElectronBadger 4y ago> Just wanted to say thank you for a fantastic text editor. This. ST has been my best coding tool for the last few years. A keeper. Thank you!
- shkkmo 4y agoFirst off, thanks for years of productive development with ST. I really enjoyed using your software for a long time and it carried me through a significant portion of my early career. It was a bug where selecting some text and using the key shortcut to multi select the next instance would select incorrect text for certain strings. It was a while ago so I don't remember the details, it may have been some combos of whitespace and non-alphanumeric characters. It wasn't the only reason, but it was the final impetus to try some other solutions.
- Mawr 4y agoHere's an annoying one: https://github.com/sublimehq/sublime_text/issues/1054 https://github.com/sublimehq/sublime_text/issues/1054
- TehShrike 4y agoah yeah, that one has me disabling word wrapping on files where I wouldn't otherwise. Hasn't been enough motivation to leave ST though