61–70 of 132 posts
One thing I feel is a strange one to optimize for: startup times. Typical Emacs use is to start it once when the graphical interface of the system starts, and never turn it off. What's even the point of this optimization?
If you’re running emacs 29+ I posit you get less value out of a starter kit or framework than beforehand. Treesitter is baked in for syntax, eglot is baked in for language servers (intellisense), project and tab-bar give you scoped workspaces. use-package is baked in for downloading and configuring dependencies. Modus-themes are also built in now, so you can use modus-operandi and modus-vivendi out of the box. Two in…
If you’re running emacs 29+ I posit you get less value out of a starter kit or framework than beforehand. Treesitter is baked in for syntax, eglot is baked in for language servers (intellisense), project and tab-bar give you scoped workspaces. use-package is baked in for downloading and configuring dependencies. Modus-themes are also built in now, so you can use modus-operandi and modus-vivendi out of the box. Two in…
Makes me want to try out a config from scratch again.. but.. need.. to.. get.. work.. done....
Earlier quoted context omitted.
I heard that some addons (like magit and vterm) run much worse on Windows than on Unix-like. That's my main concern. Maybe it's an outdated view tho.
The big issue here is that spawning processes is (was?) much slower on windows. There’s also wsl2 where I think Emacs will work fine.
Earlier quoted context omitted.
I heard that some addons (like magit and vterm) run much worse on Windows than on Unix-like. That's my main concern. Maybe it's an outdated view tho.
The big issue here is that spawning processes is (was?) much slower on windows. There’s also wsl2 where I think Emacs will work fine.
Earlier quoted context omitted.
For good autocompletion you‘ll need both an autocompletion framework and a language server client. I am still using „lsp-mode“ as a language server client which works well for me and it comes with „company-mode“ integration for good autocompletion: https://emacs-lsp.github.io/lsp-mode/page/lsp-typescript/ Later that day I can paste you the relevant lines out of my init.el. Starting with Emacs 29 you can also use the…
First, for every IDE experience you definitely need flycheck mode: (use-package flycheck :diminish flycheck-mode :init (global-flycheck-mode)) This will underline syntax errors for you. (It'll use the language server as a backend once lsp-mode runs.) Next we install and set up "company-mode" for simple autocompletion. Basically, it starts the (minor) company mode after starting "lsp-mode", sets up key bindings and re…
1. We are on version 30. By this time emacs should have come with some better defaults. It's 2023, not 1960 people.
2. Why are 90% of emacs frameworks trying to make it into vi?? I choose emacs, if I wanted vi-ish I would have used vi from the beginning
Emacs is a relic, it can take weeks of configuring to get it anywhere near as productive as something like VS Code or Jetbrains IDEs. If you want to procrastinate for a few months it's the perfect tool.
> Emacs is a relic People were saying that when I started using it, over 20 years ago. Apparently I was supposed to be using Notepad++ or some MS program du jour which no one remembers now. I wouldn't be surprised if I keep using it for the rest of my career. > it can take weeks of configuring More like decades ;) > to get it anywhere near as productive as something like VS Code or Jetbrains IDE Nope - it's significa…
Totally curious: is anyone using Emacs seriously on Windows, especially with stuff like LSP? My personal experience is that most of the new dev tooling is Linux/MacOS only, and maaaaybe sometimes it's ported badly to Windows. Are people using Emacs with LSPs for Java, Python, for example? Are they solid? Would you be able to use them day to day for software engineering work?
Earlier quoted context omitted.
> most are kinda opinionated non-essential tweaks "That's just like uh… your opinion man." —"The Big Lebowski", I think ;-) I'm mostly of the opinion that vanilla Emacs has some bad opinions with regards to discoverability and ease-of-use-for-newbies, which is what this starter kit is targeting. CUA-mode is on because without it you're gonna have newbies footgunning themselves super hard right out the gate, and that'…
> I'd love to see what you're referring to There is Google, you know. https://ergoemacs.github.io/ It's the biggest thing to happen to Emacs in 30 years. That is presumably why all the beardies ignore it. I used to know 20-30 totally different editors. That all went away circa 1990 when the CUA UI swept the world. https://en.wikipedia.org/wiki/IBM_Common_User_Access All late-era DOS stuff, and Windows >= 3.x, Mac OS…
CUA was "influenced" by the old Mac OS Human Interface Guide mid/end 80s.
The influence on macOS (as it is called now) is tiny. macOS is mostly not compliant.