Still a vimfag. I thought about getting into emacs once until I realized it just dumps temporary files all over my system and doesn't clean them up. Made me angry and I gave up.

Maybe I'll try it again one day.

I don't, because nonmodal editing is bad for your hands. It really hurts. You might say, ``use evil/vile/viper mode!'' but I already have vi (specifically nvi) installed on my system. I have an emacs installed on my system too, called mg, but I rarely use it anymore, other than for occasionally doing the tutorial to practice emacs keybindings.
https://man.openbsd.org/mg
>>2
vim has a lot of weird files too, like .viminfo

>>3
you'd want to ues evil or vile or whatever becaues you want to use emacs as your operating system.
I use sam though. The mouse is better than you think it feels.

>>3
>because nonmodal editing is bad for your hands. It really hurts
I mapped alt to ctrl, and caps lock to alt and haven't had any discomfort since.

>>2
You can change that behaviour.

>>3
An infinite number of editing modes can be created for various contexts with hydra.

>>6
No matter how customizable something is, the default behavior must be judged.

>>7
The default behaviour is to evaluate Lisp code.

I started going through SICP a couple weeks back. An IDE called racket was recommended to me (and so far it works decently well), but I'd like to try out Emacs. Would you recommend Emacs for SICP?

>>9
I'd recommend Edwin instead.
https://www.gnu.org/software/mit-scheme/documentation/mit-scheme-user/Edwin.html

Is there an Emacs-tan? There must be a moe rms, right?

>>2
Oh wow, just saw my post here from last year and I'm happy to report that I actually ended up switching after all.
I switched because 2 things dawned on me simultaneously after I had the thought:
>gee I wish there was a simple, hackable, text editor that can be customized in lisp or scheme, because lisp and scheme are cool!

Shortly after starting to research the topic the 2 things which dawned on me were:
1) That's literally just what emacs is, and nothing more
2) Everything I had ever heard about emacs being too featureful, all the jokes about being able to run things like music players in emacs, or the stuff about emacs being an operating system, etc.. were all greatly blown out of proportion just because emacs is so hackable

It's sort of like you make a program in python that runs fairly fast and some people will thank you. Then you modify 1 little thing to make it so the application can load arbitrary python code (which doesn't matter because the program was already written in python anyway, so it's literally not any more "bloated" than it was before) and suddenly people start complaining that your program sucks because now it can do too much.
It actually kind of makes me angry that nobody ever clarified this for me. The only reason for all those memes that I fell for is just because emacs' configuration language is a real programming language too which enables people to do crazy things with it like turn the text editor into an IRC application. That's it. That's what all the fuss has been about and why it's been the butt of so many jokes. How tragic.

I use emacs as my only editor now, with evil mode.

>>12
Naisu.

What else are you doing with it? Post config.

I use it regularly, mostly for editing config files, IRC, RSS feeds, dired, and tramp. I don't really program aside from elisp and shell scripts.
There isn't much in my init.el, I configure it with an org file based on uncle dave's config with some stuff I added/removed progressively. I should revamp it soon it's getting messy.
https://github.com/daedreth/UncleDavesEmacs

I've been using mg more lately.

Is there any version of vi that simply doesn't do that dumb thing where it moves the cursor one to the write (or left!!) when you're done editing a file? None of the hacks for it work.

>>16
I don't understand what you mean. When you're done editing a file vi closes and you go back to the command line.

>>17
Sorry, I mean when you exit insert/replace/whichever mode.

>>18
Just enter insert mode with "a" rather than "i"

>>19
No difference, as far as I can tell.

>>20
I still not sure I understand then. Is this possibly a bug you're experiencing?
What it sounds to me like you're talking about is if you press "i" (to enter insert mode) then immediately press escape (to exit insert mode) the cursor will be 1 character to the left of where you started.

But if you do the same thing with "a" instead of "i" then the cursor will be where it started.
Are you referring to something different?

Nope, that's exactly what I mean. Maybe I was making some kind of mistake though, or it's inconsistent. It didn't work when I tested it then, but it is now.

>>12
Same story here. I think >>9 was me.
I've taken it really slowly with SICP, really I've just been trying exercises here and there when I get bored.
As was recommended to me, I tried Edwin for a bit, and though it was nice, it was pretty alien to me and I soon looked for alternatives. I then tried Emacs with evil-mode and haven't really looked back.
Recently I've actually started using EXWM, and I've found it to be surprisingly usable. It feels so natural to treat individual programs as Emacs buffers. It's very easy to switch out my xinitrc so that I can switch between OpenBox and EXWM. I'm still working on setting up the simulation keys, suspend, and a second monitor, but other than that it's been great out of the box.

>>11
Can't say that I've seen an Emacs-tan. Here's an SICP + Gentoo-tan though.

>>23
After looking around I realized I got this image from another thread on here a couple days ago. Oops.

>>23
That's not gentoo-tan, it's just satori. This is gentoo-tan

>>25
Oh, I had assumed that was a Gentoo logo. Wow, there are a lot of 2hus that I simply don't know of. Even random images on my own computer are secretly Touhou characters.

>>26
Yeah, touhou has worked its way into just about everything. If I didn't know better I'd suspect it was an illuminati conspiracy

>>1
Default, with some things for loading some packages and such, but nothing out of the ordinary.

I can't use Emacs without use-package, bind-key, and the counsel/ivy/swiper suite.

ace-window, avy, hydra, helpful, lispy, and eyebrowse are very nice too.

I'm trying exwm a bit but it gets slow on OpenBSD on a C2D.

moo

Here's some code that I worked on recently in my init.el:

(defun bufferkill () (interactive)
(if (exwm-buffer-p)
(kill-this-buffer)
(setq kill-buffer-query-functions nil)
(kill-this-buffer)
(setq kill-buffer-query-functions
'(process-kill-buffer-query-function))))

The EXWM part isn't too important, it's just there becuase EXWM would freak out whenever one of its buffers was closed following kill-buffer-query-functions being changed.
The purpose of this code was to have a keybind that would kill buffers without asking for confirmation, the only problem I have is that if buffers are closed in quick succession then sometimes the variable doesn't seem to be set back properly, which seems to cause major problems for EXWM.
I think it's a race condition of some sort, but I've got no clue what to do about it. Any ideas?

Emacs-tan. I use her as my fancy-splash-image.

>Show me your init.el
No

> https://protesilaos.com/codelog/
I really like this guy's emacs videos. He is really deliberate in how he uses emacs which is kind of inspiring.

splash images for a text editor...

>>12
Elisp is a love/hate kind of thing. Love it because Emacs, hate it because it's not Scheme. EXWM was life-changing for me, but it's also a nightmare because of quirks idiomatic to Elisp like not being asynchronous where broken modules freeze the whole session.

>>11,25,32
>There must be a moe rms
Closest you're ever going to get.

>>37
Moe Stallman + free software song in Japanese

>>36 Can't wait for guile emacs to be finished.

You might have to wait for a while, I don't think there's anyone working on it at the moment (“at the moment” as in “these last few years”).

>>2
Add this to youre .emacs:

;; Where emacs should keep its saves
(setq backup-directory-alist `(("." . "~/.emacs_saves")))
(setq backup-by-copying t)

(setq delete-old-versions t
kept-new-versions 5
kept-old-versions 2
version-control t)

Places all youre files in one dir, it saved my emacs experience for me and is the oldest code in my config.

>>41
you can also mirror the directory structure, it keeps stuff nice and tidy

;; make backup to a designated dir, mirroring the full path

(defun my-backup-file-name (fpath)
"Return a new file path of a given file path.
If the new path's directories does not exist, create them."
(let* (
(backupRootDir "~/.emacs.d/backup/")
(filePath (replace-regexp-in-string "[A-Za-z]:" "" fpath )) ; remove Windows driver letter in path, for example, “C:”
(backupFilePath (replace-regexp-in-string "//" "/" (concat backupRootDir filePath "~") ))
)
(make-directory (file-name-directory backupFilePath) (file-name-directory backupFilePath))
backupFilePath
)
)

(setq make-backup-file-name-function 'my-backup-file-name)

http://ergoemacs.org/emacs/emacs_set_backup_into_a_directory.html

I came across this pretty nice overview of the history of emacs lisp.

I was linked to this place from the lisp thread on 4chan.
https://desuarchive.org/g/thread/100727002/#100747581

Here's an elisp function I wrote the other that's a user-friendly wrapper around M-x set-frame-font. It lets you pick the font and size seperately. It also shells out to fc-list to get the list of fonts, so it'll probably only work on non-Mac unixes.

(defun i/set-frame-font (&optional font size)
"Set the font and size for the current frame."
(interactive (list
(completing-read
"font: " (process-lines "fc-list" "--format=%{family[0]}\n"))
(completing-read
"size: " (mapcar (lambda (n) (format "%d" n)) (number-sequence 12 22 2)))))
(set-frame-font (concat font " " size)))

Enjoy.

>>2
Former vimfag here.
I just turn that backup behavior off.
If I care about a file's history, it'll be in version control.

(setq make-backup-files nil)
(setq auto-save-default nil)

>>2
I think that was my post. I still haven't gotten into emacs, but yeah, I realised I could just redirect those files to being under /tmp, right where they should be.