Introduction to Python While Loop Lesson - 10Įverything You Need to Know About Python Arrays Lesson - 11Īll You Need To Know About Python List Lesson - 12 Python For Loops Explained With Examples Lesson - 9 Introduction to Python Strings Lesson - 7 Python Numbers: Integers, Floats, Complex Numbers Lesson - 6 Understanding Python If-Else Statement Lesson - 5 Top 15+ Python IDEs in 2023: Choosing The Best One Lesson - 3Ī Beginner’s Guide To Python Variables Lesson - 4 How to Install Python on Windows? Lesson - 2 I think Code really is shaping up to be the next generation Emacs, but as many, many people might point out, the original generation Emacs is still doing pretty well.The Best Tips for Learning Python Lesson - 1 And I just don't buy the "we need to put all our resources behind Glorious Editor X and embrace a monoculture" argument I've seen in some quarters (particularly a few folks who insist that Nova needs to adopt Code's extension API). While I don't use Panic Nova (I tried for a bit, but BBEdit 14 has just been better for me as far as aggressively Mac native editors go), I find it really interesting, and v9 suggests they may go after JetBrains more than after VS Code. On topic to your first question: at this point I don't know if we "need" CodeEdit, and of course CodeEdit has to have more to it than a nice README document and a cool icon before we can really make even educated guesses about where it might go in a few years. editorconfig file to enforce basic style standards, but beyond that, I'd be inclined to think that you're going to get more productivity by letting people use editors that they're familiar - and fast - with. Off the top of my head, I don't think I agree - I'd consider mandating that everyone use an editor that supports EditorConfig and check in an. ![]() This allows checking in of editor-specific files that increase productivity > I also think there is a benefit to a team using the same editor for a project. I'd love to be wrong, though, and see an example (blog post, youtube, whatever) of Sublime working for TypeScript development with all/most of what VS Code offers out of the box (even if it involves some configuration steps). So, maybe I'm doing it wrong, or maybe it doesn't work. I mean it didn't highlight errors in TypeScript as a typed them, and "go to definition" didn't jump to the correct definition, but rather offered me a list of every place in the project where a symbol with that name was defined (including the correct one, but also several incorrect ones).) restarted Sublime Text 4 (just in case) use that to install Package → LSP-typescript However, since we are in the thread I googled it with, and then followed the top blog post results, which involved: ![]() Not really trying to criticize it just noticing that it doesn't work out of the box, and I personally have never had the time to fiddle with it to see if it can be made to work. I'd be happy to find that I'm wrong about that, though.Ĭool. There was a lot I liked about Sublime back in the day, but I felt like it just failed to keep up with the basic-level state of the art for a code editor. But are you saying these features can now be made to work in Sublime (perhaps with some configuration, or something)? To me, these basic features are table stakes for an editor in 2022, and should hopefully "just work" if you open a TypeScript file. Unfortunately, while it did offer to autocomplete the titleId property, that property is from a completely unrelated class to Hoge that isn't imported in the current file (but I can see in the hover popup where it Sublime is getting the definition), and also that property is a string, but Sublime lets me go ahead and assign a number to the property without flagging it as an error. I just fired up Sublime Text 4 and opened a vanilla Angular project to try the TypeScript support. ![]() ![]() It's interesting you mention LSP support, because that is basically why I stopped using it - the as-you-type auto-completion, error/warning highlighting, and doc/reminder/hint functionality was sorely lacking (compared to leading non-native editors like VS Code / Jetbrains). I bought Sublime Text through v3 but didn't really use it anymore, so declined to buy v4 (so far).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |