With emacs it feels like I can do almost anything.
Emacs: The Editor for the Next Forty Years [video]
51–60 of 272 posts
Re: Emacs: The Editor for the Next Forty Years [video]
#52I'm new to Emacs, but enjoying it very much. Just got mu4e working with Gmail XOAUTH2 (for a G Suite account that the administrators have implemented their own "delightful login experience"). Would there be any interest in reading a writeup?
Definitely. I approached the set up mu4e + offlineimap over multiple accounts (including a GMail one) many times, and I've never been fully satisfied with it. I'd really want to get it to work flawlessly, so I'd love to be able to learn from your experience.
What doesn't not fully satisfied mean for you? I might just have lower standards...
Re: Emacs: The Editor for the Next Forty Years [video]
#53Earlier quoted context omitted.
I'm partial to the Emacs keybindings, but you you're so right about the laptop keyboards. Mine doesn't have an End key (Home, PgDn, PgUp, Power).
The benefit of Emacs's keybindings is that they're the default keys used by GNU readline (though it also supports Vi-style keys.) That means when you know that Ctrl+E and Ctrl+A (`C-e' / `C-a') goes to the end or beginnings of a line in Emacs, you know it'll also work in your bash shell (or indeed any tool that uses GNU readline.)
That's what I'm using while coding, but it's not friendly to all software (e.g. browsers or other programs that don't have configurable keyboard shortcuts).
Re: Emacs: The Editor for the Next Forty Years [video]
#54> Emacs support is on by default in MacOS.
Given that the author is siding with the usability of macOS with something like Emacs over using it in a GNU/Linux distro is somewhat a surprising discovery and perhaps an insight into the falsehood of having a 'consistent' Linux Desktop; even for power-users like the author.
If one has to go through a maze of settings and config files to configure Emacs shortcuts to work 'consistently' on either a GNOME or KDE desktop even for a typical developer, then I would at first question myself if such an endeavour is 'worth it' for something as arcane as Emacs.
While it was a great spectacle to watch the Vi/Emacs wars, I'm afraid that I would favour getting my work done on my MacBook, thank you very much rather than messing around with something that could be easily mistaken as the editor for the prehistoric years.
Re: Emacs: The Editor for the Next Forty Years [video]
#55Earlier quoted context omitted.
The main reason I quit Emacs was the lack of context and semantically aware code completion and re-factoring tools. Such tools are invaluable productivity boosts for me. I have never gotten that to work in Emacs to a satisfactory degree.
This is true for me too. I still do some of my personal projects in Emacs, and I still use Magit, and dired, and a few others, but by and large my professional development is mostly in the family of JetBrains editors. Ideally, their code analysis could work through a server and use Emacs as a frontend, but the existing tools don't even come close to what those IDEs can do. Emacs is great, but it's not the most produc…
I've seen posts about how to set up vim as a frontend for a headless Eclipse server, but it always looked to me like the payoff wasn't worth the effort.
Re: Emacs: The Editor for the Next Forty Years [video]
#56I really started to get lost when he started talking about never wanting to leave his text editor, wanting to read his emails in Emacs, browse the web in Emacs, have slack and discord in Emacs, etc. Serious question: Why? Is it that hard to alt+tab? Especially, why would you want such distracting features inside your editor, while you are trying to focus and work?
You need to change the way you frame this phenomenon. Don't think of Emacs as an editor, but as a fully-introspectable and runtime-modifiable OS built on the "plaintext is king, but 2D" paradigm, that has a high-level language runtime (elisp), and comes with a set of default applications, one of which happens to be a text editor.
The desire to never leave Emacs isn't about making it slightly easier to view e-mails next to code. It's about making it possible to use the same autocomplete, same syntax highlighting, same recursive regex search, same multicursor editing, same whatever "magle this thing and put it in your calendar" hack you wrote the other day, on anything that's made of mostly text - e-mail, chats, code, prose, process lists, directory listing.
You'd probably have to experience it to believe it, or at least see some Emacs-as-OS user live, but this unification of all computing under a sane, end-user programmable, highly ergonomic interface can boost your productivity and experience in a way that isn't seen anywhere else today, not even during regular Linux use.
Re: Emacs: The Editor for the Next Forty Years [video]
#57There are lines in my Emacs config files that are older than some of the programmers I work with, so I can relate. Contrary to what some people think, Emacs does not require constant tweaking and wasting time on configuration. I revisit my setup every couple of years or so, and I always find it is time well spent, as my productivity goes up as a result. I do not know of a better environment for multi-language program…
I have lines in my .emacs that go back to when I used gosmacs.
I constantly add to my setup, mostly for email handling, though. I have a filtering system built in CL on top of MH-E on top of nmh.
Re: Emacs: The Editor for the Next Forty Years [video]
#58Emacs - the editor that STILL doesn't have a simple way to duplicate the current line?
If that's something you do a lot, you could write a ~3-line function and bind it to a key.
Re: Emacs: The Editor for the Next Forty Years [video]
#59There are lines in my Emacs config files that are older than some of the programmers I work with, so I can relate. Contrary to what some people think, Emacs does not require constant tweaking and wasting time on configuration. I revisit my setup every couple of years or so, and I always find it is time well spent, as my productivity goes up as a result. I do not know of a better environment for multi-language program…
> Emacs does not require constant tweaking and wasting time on configuration.
Unless you are using org-mode, in which case updating org-mode may cause issues that require reading up on the breaking changes that were introduced between org-mode versions.
(This is meant as a heads up for newcomers using org-mode, since it's pretty popular at this point.)
Re: Emacs: The Editor for the Next Forty Years [video]
#60There is an amazing project of converting Emacs into the more modern language - Rust (the C parts of it). It is called REmacs[1]. It is sad that the port of Emacs to Guile[2] didn't work out. And for the people who want to convert their C code to Rust, I quite recommend trying c2rust[3] transpiler and refactoring tool. [1] https://github.com/remacs/remacs [2] https://www.emacswiki.org/emacs/GuileEmacs [3] https://git…
reading the GuileEmacs thing it sounds like the project was a success? Is there pushback against using this upstream?
It was working, but not good enough, indeed.