Hacker News Reader

Comment by erksa | Hacker News Reader

Use both heavily. Vim is fantastic for editing one off files.

Emacs on the other hand is fantastic to work on a computer for a long period of time. I do use evil mode, as I do think it's a much better way to work in a file. Project management, magit, org-mode, being able to edit functionality of the editor within couple of mins to adjust for an temporary change/or indefinitely is what keeps me coming back to emacs.

I've tried vim variations that build in project management and all I'm missing from emacs, but left it at some own written telescope functions to cover base needs.

Love for both, but to me they are not comparable.

(Maybe because I picked up emacs at the same time a good friend picked up vim, and it's been a parallel editor journey for 6+ years)

View on HN

Vim has terminal support, gdb support built in. We have vim plugins maintained by the top Vim plugin specialist for git and project management. We have vimwiki, markdown, org mode support. We have fuzzy finding, autocomplete, lap support. I really don't think you can reasonably tell me you can't live in Vim, when I have had the same session open editing the linux source tree for like two months now.

>I really don't think you can reasonably tell me you can't live in Vim

Vim at the end of the day is a terminal application and when it comes to debugging objectively it does not live up to the graphical interface of a proper IDE. Emacs is only slightly better in that regard, it's a GUI application but the age shows as well.

I don't think it's an accident that a lot of vim users are obsessive print-debuggers and that's just a plain handicap coming from living in a terminal. From just observing a lot of developers work I would say not knowing how to fully utilize debuggers and the modern interfaces we have for them is the number one productivity killer.

Maybe a Vim expert can help me out. I’ve used Vim for a long time, but never with any plugins, and only a few lines in my .vimrc.

My problem is that the syntax highlighting, specifically for TypeScript is pretty bad. I have a regular expression (for parsing front matter) that seems to cause Vim’s syntax highlighting to go haywire (it stops and sometimes crashes).

Is anyone aware of a way to get more reliable syntax highlighting in Vim, ideally with a minimum of fuss?

using lsp with typescript-language-server?

most of the neovim setup scripts (lazyvim etc) get this set up automatically

An LSP seems overkill for syntax highlighting? This seems more like a treesitter thing.

(Mind you, I have no experience with TypeScript, just saying this as a general remark on what those components do.)

Oh, my initial research (reading the Neovim docs) indicated that setting up Neovim would require a lot of manual configuration for getting an LSP working. I will give it another look, thanks!

Most blog posts I found seemed to assume you already had a gigantic custom config, plug-in manager, etc. I couldn’t find a “how to set up better highlighting and/or an LSP for people who know Vim but don’t know anything about configuration” guide.

Not disputing that VIM has those things, but I am telling you that I can't live in Vim based on your plugin setup. But of course, I'm glad there are good crafted ext/plugin communities on both sides so we can all can tweak it the way we like!

Reply on news.ycombinator.com