zlacker

[return to "I still like Sublime Text"]
1. ben-sc+w8[view] [source] 2025-01-29 08:24:38
>>james2+(OP)
Sublime Text developer here, thank you for all the praise! I'm looking forward to what we can accomplish this year. If you have any questions I'd be happy to answer.
◧◩
2. bruce3+Sz[view] [source] 2025-01-29 13:06:51
>>ben-sc+w8
Why does sublime do code navigation in such a clunky way? Such as "go to definition". Control click does not work, instead you need to press the far away F12 key. It then opens up a new tab instead of an inline dropdown. Apparently that tab isn't normal text, it's clickable text. it contains usages as well as definitions so you need to manually scan and decipher the results. When you click on a result, it opens the file, but doesn't quite scroll to the definition, although it's in view (but not highlighted! So you have to scan for it again!)

The little pseudo terminal that pops up at the bottom when you press ctrl+b (build) is also highly annoying. Why does it not accept keyboard input? I keep having to open a separate terminal where I can compile and test my TUI apps. If I just use ctrlB, then my app hangs waiting for stdin that I can never provide. And that waiting process never gets removed by ST either when I press ctrlB again.

Furthermore, ST isn't capable of recognizing my various Makefile build commands. ST only shows make clean and make when I press ctrl shift B.

Farthestmost, why does ST not recognize when I'm in a different directory, that it should use a different build system? Why do I have to manually tell it to use python instead of C when I am editing a python file?

Ok last one. Setting up a "replace occurances within selection" is highly unintuitive. When you enter the search term, that RESETS your selection. And you have to start over. Ugh. I want to select my search area, then tell it what to look for, then tell it what to replace with, then replace all within that area.

[go to top]