Currently on Emacs 28, on my personal machines. I see that there is a Emacs 29 pretest version available, for Windows. Are all Linux users building Emacs 29 from source?
Emacs 29 is nigh
141–150 of 267 posts
Re: Emacs 29 is nigh
#142Earlier quoted context omitted.
LSP is so much better than alternatives to work with that I feel compelled to make it work and work well. Even for python, running pyright pays dividends for me. But luckily lsp-bridge looks promising so I don't feel like I need to jump ship for VS code quite yet.
To be frank, for Python I still use just elpy - it's good enough. The biggest headache I've had on Emacs with Python is dealing with virtualenvs.
Re: Emacs 29 is nigh
#143Earlier quoted context omitted.
> When I configure company to trigger instantly on a single keystroke, Emacs completely locks up pretty much every time I hit a key. Emacs using an elisp JSON parser is about 15x slower (!) than using a native JSON parsing lib. It's borderline criminal (just kidding): I think LSP should simply test if native JSON parsing is avail and refuse to run if it isn't. I'm using LSP-mode and it flies (AMD 3700X / 32 GB of RAM…
I'm also on an AMD 3700X, 32G of RAM, with Emacs native compilation branch. I'm totally unaware of elisp vs native JSON parsing though, I was just using stock Eglot that came bundled with Emacs.
Re: Emacs 29 is nigh
#144I’ve seen various opinions about eglot vs lsp-mode… anybody care to explain if eglot is better and in general why it was chosen for inclusion in emacs?
Re: Emacs 29 is nigh
#145I am loving all this emacs love lately (I am an emacsophile), but I do find all this attention it is getting suddenly a bit surprising. Is it just that "long lines, LSP, fast syntax hightlighting" is making new people interested, or is it just us neckbeards coming out of the woods? I mean, many of these things are just a package-install away right now. I seldom see vim put in the same lime-light, for instance. Or may…
For years emacs is what I used for C/C++ coding. Then CLion came on the scene, and it would be very hard for me to walk away that from and train my fingers back to meta super land. But it does seem like Emacs is getting competitive as an alternative to IDEs.
My new job is all in Julia, and I suspect emacs will provide a better experience for that than a Jetbrains IDE. I'll give it a whirl.
Re: Emacs 29 is nigh
#146I am loving all this emacs love lately (I am an emacsophile), but I do find all this attention it is getting suddenly a bit surprising. Is it just that "long lines, LSP, fast syntax hightlighting" is making new people interested, or is it just us neckbeards coming out of the woods? I mean, many of these things are just a package-install away right now. I seldom see vim put in the same lime-light, for instance. Or may…
It's encouraging to see the big quality of life additions in 29, if only because one person's “just a package-install away” is another's “should be bundled by default”.
And it's not just the headline features. There are many little things from the 29 notes[1] that solve minor niggles or replace chunks of my old “retired” config:
- New command to change the font size globally. To increase the font size, type 'C-x C-M-+' or 'C-x C-M-='; to decrease it, type 'C-x C-M--'; to restore the font size, type 'C-x C-M-0'.
- New command 'restart-emacs'. This is like 'save-buffers-kill-emacs', but instead of just killing the current Emacs process at the end, it starts a new Emacs process (using the same command line arguments as the running Emacs process).
- New command 'rename-visited-file'. This command renames the file visited by the current buffer by moving it to a new location, and also makes the buffer visit this new file.
[1]: https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS.2...
Re: Emacs 29 is nigh
#147Unrelated, but to anyone from Google. When I search for "emacs" and your product pops up a line saying "Did you mean Vi?" it really makes me want to quit using your search product. Your search is not best in breed anymore, so cute gimmicks like this are a flat turnoff.
XEmacs has long been obsolete, so anyone finding old references to it & searching it out is almost certainly helped by being redirected to GNU Emacs.
Re: Emacs 29 is nigh
#148Wow, Eglot/Treesitter/better package support in 29 make me want to try Emacs again. > Install packages from source with package.el Emacs users updating to 29: do you plan to use this instead of Straight now? If not, can you help me to understand what more Straight provides? Emacs on macOS users: do you generally compile new versions of Emacs from source, or wait for ports like Mitsuharu Yamamoto's one[1] to update? […
Re: Emacs 29 is nigh
#149Earlier quoted context omitted.
Ooo we could go on forever. Let’s start with VS Code. What we want to do is list features. For example, people prefer the GUI and the mouse, non-modal, batteries included. It’s not a bad thing. It’s just been a while. Those editors were written for a time that don’t exist anymore.
That's my point. How did emacs influence this? Emacs is nothing like that. If anything, emacs has failed. Everything else is either proprietary or company/plugin based. And mouse based. Imagine spending 8 hours a day for the rest of your life and you still want a cursor based popup telling you what you might or might not want to do instead of having muscle memory of what you do.
Yeah the free software stuff didn’t work but that’s not all the editor wars were about.
I think we’re just missing each other here. The best features of eMacs spread to other editors.
As for the scenario, I don’t see that as a hellish situation. I’ve been using vim for a while. Im actually ok at it.
Do I regret learning it? Hell yeah. Lol. But at least I got vim mode to soothe the wound a little