So far my favourite thing about emacs is that the “GNU and Freedom” help entry is followed immediately by the all caps notice disclaiming any warranty or responsibility for the software at all.

The “GNU and freedom” link doesn’t work. The disclaimer link sure does though.

I am presently not understanding the commitment to the idea that a ‘meta’ key is something that has existed in the wild since 1980.

…. Ah, there it is. The documentation says, right at the top, that pressing ‘h’ will give you a primer for first timers, and what it actually gives you is an error message saying “info file info does not exist”. Now I remember why I started using Vim.

I’m going to push through this but my early impressions are that emacs definitely does not want new users.

The starting screen of emacs offers me a dedicated pair of keystrokes that will permit me to order paper copies of the emacs manual. C-h RET returns “Info file emacs does not exist”.

Again, I am going to try to push through this, but the first impressions I’m getting here is that emacs is abandonware. Tier-1 menus that don’t work. Documentation that’s totally untested, inconsistent and full of dead links and weirdly dated terminology (“visit new file”?) This software has not cared at all about new users’ first impressions in a really, really long time, if ever.

Me: “Activate menubar”, that looks like it should help, let’s try that.


@mhoye i would go straight to using Spacemacs config for Emacs, brings you a little bit closer to our era where most Devs use vscode

@suetanvil @mhoye also solely responsible for crippled hands around the world! (Including mine and GNU emacs' own author.)

I'm not sure what "user friendly in the late 80s" even means exactly. Although for sure Macwrite was much more approachable than emacs. FWIW the built-in help in emacs was pretty great for its time.

@nelson @mhoye

I found it easier to use than vi on the Unix systems at school.

This was after four months of using vi and getting somewhat proficient at it. I can do the mode switching but it's always imposed mental friction.

But emacs worked like the PC editors I was used to in that pressing a key got you the character, so that's what I went with.

(It turns out vi is way better on a mobile keyboard though, fwiw.)

@scruss @mhoye

I've never used VMS. I'm not sure whether this is a good thing or a bad thing.

@suetanvil It's basically Windows' CMD, but with file versioning and written in the 1980s. It's rather lovely


Hmmm. Someone should fork ReactOS, strip out the GUI stuff and turn it back into a VMS-alike.

@mhoye I don't really understand why they didn't just do a mass search&replace from "M-" to "Alt-" 20 years ago. Same with "kill and yank" to "cut and paste"

@fraggle Jesus Christ is that what kill and yank do?

@fraggle it might be easier for me to fork this and update the docs myself as I go than to learn from these docs.

@mhoye it's definitely a weird hill to die on in terms of terminology to insist on clinging to

@fraggle @mhoye Doesn’t meta-key refer to alt on Windows/Linux and cmd on Mac?

@Gargron @fraggle It refers to the “meta” key on the Symbolics Lisp Machine’s original “space cadet” keyboard, that IIRC happened to share a keycode Alt and Cmd on later PC and Mac keyboards.

@Gargron @fraggle sorry, not cmd whatever that other key on a Mac is. The clover-leaf thing? That two-horizontal-line glyph?

@mhoye @gargron ah I forgot alt is called option on Mac keyboards

Which is weird because I've always interpreted that symbol to represent "branching off and taking an alternative path", like a train

@mhoye The thing that really stuck for me ~12 years ago was just the dozen or so core movement and editing keybinds, everything else around it has always been weird clunky dross. But I haven't yet found another editor that does those core binds the same way, so I've dragged my minimally customized dotfile across innumerable new setups.


When I catch Emacs behaving like a conventional app (e.g. entering text replaces the selected text), I often treat it like a roach in the kitchen and edit my .emacs/init.el to squash that shit dead.

I.e., Emacs is its own wierd thing and it invented this stuff before it became common.

I view this with the kind of affection one has for an eccentric that one has learned to deal with (e.g. a sysadmin 🥁) but acknowledge it's not necessarily healthy.


Emacs falls into the category of tools that require some up-front time investment to learn before it becomes useful.

(I have some half-formed thoughts on how the field of UX tends to conflate "easy to use" with "easy to learn to use" or "easy to use without upfront effort" and that a lot of the most powerful software tools available are considered hard only because you need to learn to use it up front, but that's tangential.)

@suetanvil I have some sympathy for that position in general, but this is Stockholm Syndrome. There’s a difference between “this is challenging to learn because it is a big, complicated tool” and “this is challenging to learn because the documentation is missing, outdated or wrong”.


Less Stockholm and more sunk cost fallacy. I've made the investment and am reaping the benefit; it's possible that better design would have reduced that cost but it's too late for me now.

Also, apologies if I come across as an Emacs partisan. I have lots of complaints about it but it also works pretty well for me.

(FWIW, I've had no problem getting docs, so I'm wondering if it's a packaging issue on your end. Of course, I also just Google it most of the time so it may just be that.)

@suetanvil @scruss has pointed out that I’m hitting an ideological schism between the FSF and Debian that dates back to 2006.

@mhoye I admire your patience. I don't think abandonware is the right word. When I first tried Emacs back in 1990-s, it was just as bad as it is now. I tried for a few days (naive young fool that I was), but eventually I gave up and never looked back. It wasn't abandoned, absence of empathy to its users has been the defining quality of its UX design throughout its history.

@angdraug @mhoye

It's not just Emacs

It's the whole GNU project

It's a deeply entrenched cultural problem

@abbienormal @angdraug @mhoye totally agree with this statement. Emacs looks awful at first glance, but yet it provides a great base for extending for your concrete use cases. Emacs is the best in providing user freedom.

@jplebreton @abbienormal @angdraug @mhoye from restrictions made by devs. Basic example is it is free software, so you can mess with your code however you want, but its not only about code availability. Compared to vim Emacs has greater ways to extend itself, its not "limited" to vimscript and what devs let you "script", almost everything is changeable.

@w96k @jplebreton @abbienormal @angdraug “let me do whatever I want” is the most narrow, selfish kind of freedom imaginable, though, and doesn’t admit the existence of things that turn out to matter a lot. Like “other people” and “society”, to name two.

@abbienormal @angdraug @mhoye

Definite 80s-high-school-computer-club vibe to it. I also used to say things like "if it was hard to write, it should be hard to understand." But then I reached my mid-twenties.

@suetanvil @abbienormal @angdraug it’s an accessibility problem. There is a fundamental difference between “this is difficult because what we are trying to do here is inherently difficult” and “this is difficult because we have not put the effort in to making it easy.”

@mhoye I can confirm that after using emacs for a decade I have completely lost all comprehension of how normal people expect programs to work, except for a vague idea that it involves using the mouse for everything and the "view/edit source for this command" feature has been removed

@mhoye if you want an answer for "why do people continue to put up with this shit for so long?" it is 100% because "where else can you find an OS with a view/edit source for this command function that actually works?"

(without going back in time and using smalltalk, I mean)

@technomancy @mhoye my theory for why the tutorial&info documentation is broken is the same as for gnome/kde ui efforts: built by experts for their mental model of a non-expert.

Full-time emacs users don’t need or use the tutorial, and anyone who isn’t one yet but needs one, self-selects out.

@antifuchs @technomancy that’s not “self-selecting out”, that’s being structurally marginalized.

@technomancy @mhoye or that. At any rate, it’s not observed by the people building the introduction UX.

@mhoye the only part of emacs that I use in my daily life is remapping capslock to ctrl.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!