Any other modus theme users think modus-operandi sounds like a dark-theme and modus-vivendi sounds like a light theme? It's kinda like a kiki/bouba thing methinks.

nostr:npub1dtw0ve3yrtslcda2l46lmm7t5z7m7sc6xf9r7cd98e37pd92utdsd885ra IRC communities are great, but the tech sucks

When installing Windows select "I don't have internet" and you won't be forced to make a M$ account 🧠

The main thing I miss about static typing is being able to look at a function in isolation. When working on a function in a dynamically typed language it's so hard to know what exactly is valid input to the function and what in the world the input actually means in human terms. You basically just have to know all the call-sites by heart. Not ideal imo.

While transitioning from #golang to #clojure, I really missed being able to hover over any variable and field and learn what that thing actually means and what the different variants of a thing are. I found that Go code is exceptionally well documented. Exported names are almost always documented, so finding out what a thing is just consists of going there and reading it. In Clojure I have to do code archeology to find out what I'm dealing with.

nostr:npub1yhj4ua6580h3w0kucwwrtwl4uv9pg7m2drxzplq5x3364jczp36s4h3h3t my chatgpt says 0 which is technically a valid answer, since it doesn't say whether sally and the brothers are half or full siblings, but the reasoning chatgpt made doesn't make sense:

Sally has 0 sisters. Each brother has Sally and another sister, making it seem like there are 2 sisters, but they're counting Sally herself.

nostr:npub1plqnj4m42g56qeqtext4vr66x3d9j093wwy6eqh475qx73dmkhms86efde Haha, I'm just in the living room because I wasn't done working on the pc :)

If you're an #emacs user who has been postponing structural editing, or just not gotten into it when trying paredit (or one of the million alternatives), try just using the built-in, prebound commands:

M-x forward-sexp (C-M-f)

M-x backward-sexp (C-M-b)

M-x kill-sexp (C-M-k)

M-x backward-kill-sexp (C-M-)

They're really unintrusive and makes for a natural way to get into structural editing, without disrupting your current workflow or having a high learning curve. They work for #clojure too :)

nostr:npub1g62l2pvxdk40jyw2750yv7lrf728yfpv6v3cpugtc6l6nkcen9eqvpf33t Ohh, thanks for the PSA! If I might add, Railwaycat's Emacs formula actually packages Mitsuharu Yamamoto's fork. He deserves some credit too :)

Any computer experts on here who knows if this RAM https://www.corsair.com/ww/en/p/memory/cmk64gx5m2b5200z40/vengeance-64gb-2x32gb-ddr5-dram-5200mt-s-c40-amd-expo-memory-kit-cmk64gx5m2b5200z40 will work on this motherboard https://rog.asus.com/motherboards/rog-strix/rog-strix-b650e-f-gaming-wifi-model/?

The RAM is not listed on the qualified vendor list, but I can't see why it wouldn't work.

nostr:npub1jz4fkl2yy7ar6n7lxg8ahd6ydps2pwrxngsj0y8yueqv3n3rv77s7rd2ua How does using the command line teach you how something actually works any more than using a GUI?

I say use the best possible UI for interactive use cases and use the best possible API for programmatic use cases. Apps designed to run inside emulated 80s hardware are usually neither.

Today's episode of underappreciated #Emacs features: M-x highlight-phrase

pst: I know it's "its", no need to correct me :p

https://media.emacs.ch/media_attachments/files/110/742/547/921/921/634/original/bb65ddb72e3f0bde.mp4