I have loads of dot files (if you refer to /.config ecosystem) but I am not a github hacker. I tend to build from seat of pants by orchestrating what I see on the screen. That is by UI automation. Much depends on UI compatibility cross OS. I focus on Ubuntu but can experiment with Windows/Mac , if I must, to collaborate. I don’t often write Packages/Plugins since they begin to clutter the landscape and workflow. Just leverage / orchestrate what you can see. Like stage props. For example with a few mouse clicks I can open any Subl Text file in any desktop app … sans packages or plugins. Although I do use some that are required. Exalt for one for XML compatibility (such as SVG et al). I can’t easily remember key combos so I use aliases instead to map to key bindings (much written on that recently - bewildering to me - see here Table of Key Bindings). I use a different, visual way of desktop binding I guess. Orchestration is the key word. Take a look at enabling (in partnership with Subl on same desktop stage) venerable tools such as Actiona (Actionscript days - needing Actionscript package) and then more comprehensive TagUI. Then become a “desktop playwright”, managing Actors, Acts, Scenes, Stage props. They are all found in Ubuntu. Subl is just one key Actor but easy on my elderly eyes as prime editor across different scopes. Hope that explains my odd visual thinking. Let me know what “dot file” is of interest. What process? Which OS?
Anyone else still sticking with Sublime in 2026?
Hi, @marryjoseph8.
If you haven’t already tried it, I have recently been developing a lot of Python code with the LSP and LSP-pyright Packages, and am EXTREMELY impressed! Right-clicking the text, and selecting LSP > Goto Definition... feels a great deal like some of the best IDE’s I’ve ever used. As an example, as a test, I placed my cursor on the str type (in a typing hint) and did that, and it took me to buildins.pyi to the class str definition! Plus it is extremely agile in the type-hinting arena. In the package I am currently developing, it has already saved me (literally) dozens of bugs that never ran and generated a run-time exception (or presented any future danger) because LSP-pyright caught them first. This is a huge blessing in local code. Plus, after a year of extensively customizing my own environment, may tail is wagging about Sublime Text more than ever…
Kind regards,
Vic
P.S.
If you place pyrightconfig.json in your project with this content:
{
"extraPaths": [
"/path/to/app_code/Lib/python3.14.zip",
"/path/to/app_code/Lib/python314",
],
//"typeCheckingMode": "strict",
"executionEnvironments": [
{
"root": "./",
"pythonVersion": "3.14",
},
],
// Install LSP-json to get validation and autocompletion in this file.
// "venvPath": "./myenv",
// "venv": ".venv",
}
The LSP-pyright Package will ALSO do you proud with the Sublime API!!
I recently switched to Sublime. I was doing exclusively Apple-platform development for more than 20 years, so I was using Xcode, but now I’m doing a project where I have to do a bit of ts, so I had to find an editor for that.
Being in the Apple ecosystem completely, I tried BBEdit, but it did not convinced me, especially due to its poor LSP support.
I tried Zed because it’s the new hotness, but it “felt wrong.”
I tried Sublime and fell in love with it.
So much that I even “resurrected” an old plugin for Modelines, because I needed proper Modelines support in my project (not for ts, but for my IaC repo).
Over the years, I’ve tried most of the existing paid and free editors. My experience with Sublime has been the most influential. Over time, Sublime naturally became my main editor. And it remains so. I see no reason to switch from Sublime to anything else.