podmoon.blogg.se

1. [UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX HOW TO
2. [UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX UPDATE
3. [UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX SOFTWARE
4. [UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX CODE

[UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX HOW TO

In all cases, the optimum solution is to clearly indicate to the user that the file name or contents have changed, preserve both the contents and the filename/location, and give the user the option as to how to deal with this given their particular situation.

[UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX UPDATE

If no: user #2 mad because updating file outside of editor didn't update it within editor as they'd hoped.Ģ) If the file was only renamed - but renamed by mistake - to something generic or wrong: user #3 mad because original filename (which may also have been a location) is now lost. This is not a good solution for two reasons:ġ) If the file was renamed and its contents changed - what should the editor do? Load the changes underneath the user? If yes: user #1 mad because now the only copy of file contents was wiped in OS, and now by the editor in what was originally a mistake. These folks wouldn't even bother wondering if they might be mistaken before unleashing the hounds.

[UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX SOFTWARE

That's always a great way to start the day.Īlso, our corporation had to fend off a few legal threats, because some of our software looked vaguely like some GPL stuff (I guarantee it wasn't -they were anal about the GPL), so zealots would sometimes throw sueballs (or vague threats, thereof) at us.Īt least the patent trolls would do a little bit of homework before attacking us. In the past, I have been contacted (I make it easy to get in touch with me), and told that I was a "corporate shill" for not using GPL.

[UPDATE] SUBLIME TEXT 2.X, 3.X UNIVERSAL LICENSE KEYS COLLECTION FOR WIN, MAC & LINUX CODE

Hopefully LSP is better integrated or documented by now.Įven for code I didn't publish (like corporate SDK internals), I have been contacted (which took some work, because my employer did not like customers interacting with Engineering), and told (not "asked" - told) to make changes to our corporate, closed-source SDK to suit some rando's tinkering around (also, for extra credit, said rando hadn't even purchased one of our cameras).Īnyone that has spent any time at all, on most tech forums, have seen the "Open Source Holy Wars" being fought. Still, I love everything else about Sublime and am excited now for multi-tab-select, so I'll probably give it one more try. The docs were vague, and I think I had to put some JSON configuration structure in some file, but nothing I tried I guess was the right file or right structure. I figured LSP would help in this regard, but I couldn't make it work. The symbols, if I understand correctly, are based on the syntax configuration, and for the common Elixir one, it includes the type definition line, each function head, and the callsites of the function, which makes it nearly useless for symbol navigation. The sort of minimal deal breaker level of support for me is being able to jump to definition. I figured I'd wait until the non beta release, and try again. I couldn't get the LSP to work for me for Elixir, so I ended up back on VSCode for now. I was formerly a paid user of ST3 before switching to VSCode, but gave the ST4 beta a try a month or so ago. It allows ST users to contribute to the LSP plugin, while ST devs can focus on making ST more awesome on their own way and adding new API-s.Īll I can say is that LSP already has first class support, because the ST devs have specifically expanded the API to allow LSP to implement certain features. Having LSP as a plugin allows the best for both ST users and ST devs. So ST would chase after offering the same functionality as VS Code, but then always be a step back.

ST devs would shift focus on implementing the LSP spec which is mainly driven by Microsoft and the spec is somewhat driven by VS Code functionality. The speed mostly depends on the speed a language server returns a response to the LSP client.

Implementing the LSP client in c++ won't make the user experience faster. That would mean that the LSP source code would be closed source too and that would not allow other people to contribute to it. Just wanted to share my thoughts on why LSP as an open source plugin has more benefits than getting first class support from ST devs.Ĭons of getting first class support from ST: