#(shitposts)

[punkitt-is-here]

sitcom

[theunmarkedtombstone]

You walk through a house and read notes.

[catboybeebop]

2nites gunna be a good nite

i gotta feelin

[fittlebottom]

this got 9k on twitger dats gay as hell bro

[thetwilightroadtonightfall]

another hit powerpoint from yours truly!

some of the slides have gifs so I've decided to just link it

[xander-morrison]

Well? Do you love yourself?

yknow kinda something special about the fact that i got a cut on my left hand ring finger while working on someone’s christmas present. that’s gonna leave a scar. every time i look at my ringfinger i’ll be reminded of it. the “wedding band” finger… kinda more intimate than marriage…

[thatisaloaf]

Good job will wood. good job seeing the voices

[17panicattacksinatrenchcoat]

do you ever just find the most inscrutable shit in your notes app from three months ago and think what the fuck was i planning to do with this? because me too

[cheldobryakk]

[rust-official]

This time round trying emacs is different because I'm using doom (at the brilliant recommendation of one of my partners, mentioned above), which is kind of like one of the neovim distributions but for emacs. Good defaults that match what a 25 year vim veteran wants, enough customizability to fit to what I need. Like any massively complex piece of software, it's taken a lot of getting used to, and there's always more to learn. The doom docs say that learning emacs is an adventure, and I agree.

org mode is cool! There are some plugins that simulate it in (neo)vim of course, but nothing really manages to match org. The more I learn about org, the more I love it--it is always the marquee feature which gets me playing with emacs every time I've wanted to try it. Of course, the most basic features for outlining are state of the art, even among commercial outliners like omnioutliner, everyone knows that. But it also supports cool things like tables with integrated calculator support and exports to every format you can think of and and and. org's manual is hundreds of pages and it can do so, so much. And it's just one package!

Continuing from the above, neovim can't have a plugin that does everything org mode does, for a variety of reasons. It's too mature and has too many people working on it for a few loosely-associated plugin writers to be able to accomplish the same thing. Beyond this, even neovim just doesn't have the same extensibility that emacs does. Most of neovim is still written in C with a thin layer of lua for extensions, whereas the emacs philosophy is a small core in C and the rest in elisp--a lot like atom or, more recently, visual studio code--but using a real language, of course, and not JS.

evil mode is a far better approximation of vim than I was expecting. Just about every other vi mode falters and has bugs / missing features. I've not run into any such limitations or bugs with evil, again probably due to its popularity compared to the vi modes in those other tools, which are often an afterthought (or just removed / dropped entirely, like in the new repl for python 3.13).

The emacs philosophy is as it was 30 years ago when I first tried learning it: it still expects you to open the editor when logging in and never close it. As such it has better tools for managing lots of open buffers (I particularly like ibuffer, it mostly approximates vim's bufexplorer plugin, but it's missing a few things from vim or I don't know about them yet; will be looking at the manual).

There's seemingly a package for everything, and often a few different ones for the same thing. The "emacs is my operating system" mantra makes a lot of sense when viewed from this angle. Lots of things have good documentation, too, and of course, as I said above, so much more is possible in emacs than neovim.

doom's out of the box LSP support seems nicer than neovim's. I'm sure I could get similar results with configuring neovim, perhaps with more plugins or config, but things just feel more robust right from the start. I still need more time to evaluate this, as I've spent the least amount of time editing code. Mostly I've been focusing on editing documents with org mode and the occasional dabbling with magit for doing git stuff. magit is quite nice and very mature; I know it'll work quite well for managing code repos once I'm more comfortable with emacs as a code editor. I have lots of custom keybindings for neovim's LSP support that I'll need to relearn if I want to use emacs as my code editor.

One criticism I do have is that none of the emacs terminal emulators I've tried work well with vi keybindings in my shell; when I press esc to enter normal mode in the shell, the buffer for the terminal emulator goes into evil's normal mode. There may be a way to fix it, but I've not looked into it yet.

Am I going to switch? I don't know. I'm giving it an honest try, a more honest try than I have in the past, and having someone to ask questions is proving absolutely critical. I can't answer this question right now. Maybe? I cannot say how helpful evil has been with this. Modal editing is how my brain works and I don't think I'd be able to learn non-modal editing.

Given how @neovim-official hates me (see here) I have started learning @emacs-unofficial , using @doom-official and hence @emacs-evil-mode.

(this is not entirely a shitpost, one of my partners has been showing me around, largely for org mode but I've always been curious. Back when I got my start with Unix/Linux in the late 90s on a shell provider, emacs was the first editor I tried, but it was so slow to start back then that I switched to vim. How things would've been different for me if computers were faster when I started!)

[daburubareru]

[punkitt-is-here]

first art of 2025 btw

[great-and-small]

[starryjoy]

someone: wow, time flies

me: you can see them too?

someone: what?

me: the time flies?

[deathpov]