Earlier quoted context omitted.
I find that lsp-mode works pretty well most of the time. If you look at the commit history, the project is very active. It's also pretty easy to set up.
I found that it didn't work out of the box for me (Rust and Python) but that eglot did work out of the box. Eglot, not lsp-mode, will be the LSP implementation that makes it into the GNU Emacs distribution (because it is being developed with FSF assignments, and because the maintainer is active in the GNU Emacs development community, maintaining eldoc and flymake, and maybe others).
Toward a “modern” Emacs
361–370 of 539 posts
Re: Toward a “modern” Emacs
#362Earlier quoted context omitted.
I doubt they have had 20 years of using to it though.
This kind of ties back in to the point of the article. For people who have used $EDITOR for 20+ years there's little incentive to change to something else, but if you want to bring in fresh eyes to your project so that there'll be enough people around in another 20 years to maintain the whole thing it behoves you to think about attracting those people. Sane defaults and being more approachable is a good way to do tha…
Re: Toward a “modern” Emacs
#363I don’t know. I read the whole article and it seems the suggestions boil down to emacs needing to be more “modern” by defaulting to dark mode, making color theming easier, changing right click behavior, the menus, and changing the shortcuts. And the author of the article would like the development process to be more “modern.” Emacs is one of the most successful text editors of all time if not the most successful. It…
It’s quite silly to think that dark mode is a modern invention. It’s just a example of how software trends are a form of fashion, and they do behave cyclically.
See also: return to lightweight clients and fat servers as we moved onto the web, and then moving the bulk of work back to fat clients with React etc
Re: Toward a “modern” Emacs
#364Earlier quoted context omitted.
This is amazing. I already wrote this to another comment, but quoting myself: > Is this a USA vs the rest thing? I've worked in many startups in the US and almost everyone uses emacs. Last few years, VSCode has been getting popular though. I had a similar experience when I was a student in UC Berkeley, although it seems like there were more vim users in school than in industry. Anyway, pretty much all my current cowo…
I am using Vim. Is it worth it to try emacs?
Re: Toward a “modern” Emacs
#365Re: Toward a “modern” Emacs
#366Earlier quoted context omitted.
This is amazing. I already wrote this to another comment, but quoting myself: > Is this a USA vs the rest thing? I've worked in many startups in the US and almost everyone uses emacs. Last few years, VSCode has been getting popular though. I had a similar experience when I was a student in UC Berkeley, although it seems like there were more vim users in school than in industry. Anyway, pretty much all my current cowo…
I am using Vim. Is it worth it to try emacs?
Re: Toward a “modern” Emacs
#367Earlier quoted context omitted.
Your reference to musical instruments resonates with me (I play piano) and the fact that emacs call they keyboard bindings "chords" further complements that view. I guess the issue that is being handled here thought is that, just like the piano, the road for those actions to become unconscious is a long painful one. When I started using Golang for work the first thing that I did was buy GoLand from jetbrains. It just…
It's really not that painful. In college I spent two weeks forcing myself to use emacs for everything. I printed out a reference card and unplugged my mouse to prevent cheating. It was not a productive two weeks, but afterwards I was proficient in emacs editing and have been ever since. (Of course true emacs mastery goes much deeper, but it really doesn't take that long to become proficient.)
Re: Toward a “modern” Emacs
#368I don’t know. I read the whole article and it seems the suggestions boil down to emacs needing to be more “modern” by defaulting to dark mode, making color theming easier, changing right click behavior, the menus, and changing the shortcuts. And the author of the article would like the development process to be more “modern.” Emacs is one of the most successful text editors of all time if not the most successful. It…
Re: Toward a “modern” Emacs
#369I don’t know. I read the whole article and it seems the suggestions boil down to emacs needing to be more “modern” by defaulting to dark mode, making color theming easier, changing right click behavior, the menus, and changing the shortcuts. And the author of the article would like the development process to be more “modern.” Emacs is one of the most successful text editors of all time if not the most successful. It…
transparency, gradients and rounded window corners. oh, and a thin sans-serif font. maybe a soundtrack
Re: Toward a “modern” Emacs
#370Earlier quoted context omitted.
I don’t wish to do a point-by-point rebuttal as you’re entitled to your view — just that it misses the perspective of a large fraction users. As for me, I’m fairly happy using Emacs Doom. > While I agree that a convenient way to download things from MELPA would be nice, I hardly see not having it as a barrier. Most people new to, say, Visual Studio don't start with "How do I download plugins". I think this statement…
> I think this statement is untethered from reality, and matches approximately zero people I know. Note that I'm referring to Visual Studio, not VS Code. In my last job, we didn't use any plugins with Visual Studio for a bunch of years before one developer convinced the rest to use Resharper. > Almost everyone using a text editor is using it for purposes which would definitely be helped by task-specific enhancements…
Those still need addons/plugins like org, mu4e or some other mail client, etc. This my point — not just a vanilla text editor.