I get your point. I messed with eshell for a while, then used vterm. In the end I just hard wired a swaywm key to a scratch terminal wihch toggles an alacritty instance. I can copy and paste in it fine : in short I find it easier to do “terminal shell things” in a “real terminal” but I can see why others prefer to stay inside emacs. Occasioanlly I’ll use a terminal inside emacs via projectile as its quick to open a terminal at your current project location.
Well, if you want to customise Emacs - obviously it’s worth learning. Im not quite sure where you get that idea that because its “old” then its support is somehow worse than “more popular” languages. It has great documentation - in editor too.
The only “performance” issue for me is lsp - but that tends to be at first run on a large framework. And since my “old” laptop (x1c6) is about 1000x faster than the one I started using emacs on in the early 2000s it really isnt an issue.
Less haste, more speed…
Lol. I just realised I never knew. Thanks!
Recently I was reading #emacs and saw that some claim pgtk, or native wayland, is bodged and not feature complete. Is that right? If so, which is the best toolkit to compile from source with to run under XWayland?
That’s a bit of a damp squib to put it mildly.
In fairness, vscode is much better than Emacs in terms of “ease of use” for plugins and debugging. But not a patch on the overall integrated experience. LSP the big game changer that bought me back to coding in Emacs though dap is still very underwhelming.
I’d doubt it’s treesitter. It could be, of course. The LSP server more likely. If using Linux run htop or something and check memory usage. Edit: Mac. Find the htop equivalent.