8 ms·
VS Code is an acceptable emacs
by zitterbewegung 4y ago
VS Code is an acceptable emacs
- Buttons840 4y agoYou sure? I don't think VS Code is open-source (happy to be proven wrong) and that's an important part of Emacs.
- deleted 4y ago[deleted]
- FPGAhacker 4y agohttps://github.com/Microsoft/vscode https://github.com/Microsoft/vscode https://github.com/VSCodium/vscodium https://github.com/VSCodium/vscodium
- coldtea 4y agoIt's not the important part of Emacs for everybody though.
- trelane 4y agoPerhaps you mean Free Software rather than Open Source? Parts of VS Code are open source but they are not Free Software.
- kjhughes 4y agoArguably not without a Lisp-based implementation and extension language. That said, as a multi-decade Emacs (and Lisp) user, I do like VS Code and its JavaScript/TypeScript basis.
- nickysielicki 4y agoNot until it gets something akin to helm/ivy/consult. I like emacs and have been using it for like 8 years, and doom makes my additional configuration small and manageable, but I’d switch to vscode in a heartbeat if it was possible to replicate basic features of an extended emacs. I just want a good editor at the end of the day. * wgrep is hugely useful. * Fuzzy searching with orderless is unmatched in any other editor. Being able to resume is hugely useful. Being able to plop the results into a saved buffer is hugely useful. * magit is the only way to do complicated rebases. I really want to move on but until vscode fixes their search, I’m stuck. I can live without a good git interface, I can’t live without navigating projects in a grep-oriented way. Vim doesn’t have this either, by the way.
- peoplefromibiza 4y ago> magit is the only way to do complicated rebases I use this https://marketplace.visualstudio.com/items?itemName=kahole.magit https://marketplace.visualstudio.com/items?itemName=kahole.m...
- jedbrown 4y agoIt's a start (and I use it too), but it's so far from parity with Magit that even when working in VSCode (where rust-analyzer is better), I often switch to Emacs for Magit.
- peoplefromibiza 4y agoI feel it when edamagit fails me I rely on smagit I've never been proficient enough with Emacs, no matter how much I tried,but Magit is its killer app https://github.com/maio/smagit https://github.com/maio/smagit
- ducktective 4y ago>Vim doesn’t have this either, by the way. look into fzf vim plugins.
- nickysielicki 4y agoI’m aware of denite/fzf/telescope/clap. They don’t come close to what’s possible in emacs.
- least 4y agoWhile I'll agree that you can't accomplish all that's possible in Emacs in vim, I'd love to know what you can accomplish using fuzzy search in Emacs that you can't in vim.
- nickysielicki 4y ago
- prescriptivist 4y agoThe most annoying thing to me about VS Code is it cannot be extended in a way that doesn't require developing a plugin. In short there is no ~/.vscode.ts. Instead you have to create a plugin to add custom commands. I say this a a former emacs user now using VS Code.
- EnderShadow8 4y agoYou can write an extension which evals a JS file to recreate this
- tomcam 4y agoOn the surface that appears to make no sense at all. Do you mind being a little more descriptive?
- rgoulter 4y agoAmong developers, probably the most popular text editors are VSCode, vim, and emacs. On a spectrum of "notepad to IDE", vim is closest to "editor only"; although with effort it's possible to get an environment with nice bells & whistles. Emacs has always been 'heavier' than vim (although I don't think it's "works well out of the box enough" to count as an 'IDE'). A couple of ways in which it's heavier is e.g. its fancy UI for customising properties; or its "apps" like org-mode or magit, or having an elisp shell or support for virtual terminals. VSCode's also not quite an 'IDE'. But it's also heavier than just a pure 'editor'. VSCode doesn't quite have the insane level of customisability that Emacs has. VSCode also doesn't have people bragging about e.g. reading email from VSCode. -- But, VSCode does have some of these features (e.g. an 'app' for interacting with Git, or inbuilt terminal). I like to think that VSCode's discoverability owes a bit to Emacs (e.g. the key bindings showing in the command palette reminds me of emacs' which-key).
- tomcam 4y agoThank you. I thought you were getting at some kind of fundamental alignment between the two products, but as I see it, you view VS Code as a product it’s as extensible as Emacs, or something close