This might be the first time I've ever seen something productive happen in the Phoronix forums. I love that place. Go to any topic with more than about a dozen posts and it's almost guaranteed to be a flame war. Genuinely one of the funniest places on the Internet.

Check out this one. It took like three posts!

r/cth was originally a subreddit for the podcast Chapo Trap House, but it eventually bloomed into a general-purpose leftist space. IIRC, the sub was around 160k members at its peak and had a distinct posting culture.

It was quarantined by Reddit for violent speech after calling for the death of slave owners and later banned for no particular reason at the same time as r/the_donald, presumably as a "both sides" sort of thing.

The reason that Doom is so portable goes beyond Linux and is an artefact of its development. id developed Doom on NeXTSTEP (i.e. Unix) machines and obviously targeted DOS. This is pretty unique among DOS games at the time and required id to write as much code as possible in a platform agnostic way. This means that the main engine does not care about where it is running and the usual DOS hacks are contained to DOS-specific files. In order to port Doom to a new platform, ideally one only needs to rewrite the system-specific implementation files for video, sound, filesystem access, etc., and this mostly holds true today. (These files are prefixed with i_ in the Doom source).

The Linux port is just one of many versions developed at the time. I don't believe that it was commercially released; it was more of a portability test. The reason that the Linux version was chosen for the source release over the DOS version was because it didn't rely on the proprietary DMX sound library that the DOS port used.

Hexbear is an instance formed mostly by former r/chapotraphouse users after that sub was banned from Reddit a few years ago. Hexbear used to run on a custom fork of Lemmy so that the community could add extra features that they wanted (like custom emoji) but it was recently ported back to mainline Lemmy after merging or reimplementing as many changes as possible.

Currently, Hexbear does not have federation enabled, and there is discussion about who to federate with or even whether to federate at all. The community is very active and self-sufficient and some members prefer the isolation.

Content-wise, it's a leftist-focused instance. Some shitposts, some serious posts, and a lot of inside jokes.

lemmit.online is an instance where a bot reposts Reddit content.

My heart sank upon reading the word "electron" and rose again on the very next paragraph. I'm looking forward to seeing it in action.

Cool small features in Emacs 30 that I really like:

• If you have ever tried to create a custom modeline, you may have discovered that right-aligning elements was a massive pain. Emacs 30 adds a new modeline element mode-line-format-right-align which makes all subsequent elements in mode-line-format right-aligned.
• When Emacs prompts you about recovering an auto-save file, you can now press = to show a diff between the buffer and auto-save. No more guessing whether you had done anything important.
• E in dired opens a file with the default program for that file type (via xdg-open or OS equivalent).

This is the main reason that one should learn to read PKGBUILDs. Any AUR helper like Yay or Paru should give the option. Just make sure that the package downloads from an official source and contains only the necessary build and install instructions.

But I agree. Some people treat the AUR as just another repository, when it most definitely is not.

I have to shout out Wiby. It is focused on like weird personal websites from the early 2000s, that sort of thing. Absolutely not a general-purpose search engine, but mashing the "surprise me" button will take you to all sorts of fun places.

I am a proud Openbox user. In the stacking realm, there is nothing quite like Openbox's customizeability and the great tooling that surrounds it. In particular, opensnap gives me window snapping to the edge of the screen with the mouse, which is sorely missing from most light window managers. Openbox also has really powerful hotkeys (any arbitrary sequence of actions) alongside Emacs-style key chords, which makes it difficult to port my setup to any other environment.

One day, I hope to migrate to labwc, which seems to be carrying Openbox's banner into the Wayland era. Unfortunately, labwc doesn't (and probably never will) support key chords and I have not been able to find a suitable replacement for tint2, which I use as my taskbar. Someday...

Here is an old screenshot of mine. Nothing has changed since then.

Lemmygrad is a Marxism-focused instance and Hexbear is currently making the migration to mainline Lemmy right now.

I don't think that's a good idea. Pretty much all interaction with Emacs is mediated through keybinds. There is no distinction between shortcuts and fundamental behavior. Even ordinary typing is done by having each character on your keyboard bound to self-insert-command. Perhaps there is some way to nuke the global keymap, but then you're left with literally nothing. Besides, this would not prevent various modes from adding their own keys anyway.

You should consider whether Emacs keybinds are actually in the way enough to be bothersome. You can also keymap-global-unset (or keymap-unset) individual bindings that you find problematic. I'd also consider delving into the Spacemacs code to see how they implement their "vi only mode."

Xremap, despite the name, supports both X and Wayland, and can be used to move modifier keys around. Configuration is done with YAML but is otherwise pretty easy. I personally use it for full Emacs keybind emulation.

Emacs 30 is a more low-key release compared to heavy hitting features like native compilation in 28 and Tree-sitter in 29. Probably the headline change is replacing the libjansson based JSON parser with a homegrown one that is several times (~8x) faster, which will significantly benefit features like LSP. This will also mark the official release of the Android port, as well as the usual scattershot of improvements across the board. The NEWS file has the full changelog.

This is something that I am sure will be solved eventually, but one of the major weaknesses of Wayland is the lack of lightweight standalone compositors.

For example, if I want a lightweight stacking window manager on X, I can choose between Openbox, Fluxbox, FVWM, IceWM, Pekwm, JWM, Window Maker, hell even twm if I were a masochist. I have tried out all of these at one point or another and they all have something to offer users. But using Wayland, there's, uhh, labwc, and that's it? Maybe I could try using kwin standalone?

The situation for tiling window managers is similar, with Sway being the only one that feels mature.

I plan on migrating from Openbox to labwc at some point in the future, once it's ready. labwc itself is really good, but some of the other programs I need to recreate my setup aren't there yet. Someday...

Emacs's regular clipboard is the "kill ring" which also allows you to retrieve any previously cut/copied text. It also has "registers" where you can store and retrieve snippets of text, which can be considered clipboards when used for this purpose. Registers can be referenced by any character you can type on your keyboard, including control characters like ^D.

This totals... a lot of clipboards.

Here's one I know. Creates aesthetic wavy things.

https://tanck.nl/wallpaper/

It is an HTML/JS pair, so it would require some wrangling to get it to write to a file instead of an HTML canvas. Though it looks like someone translated it to Python with file output here. (I have not tested this.)

Personally, I flip :defer around by setting use-package-always-defer and :demanding packages that I want loaded at startup.

I recently wrote a literate R document where I added features to a plot one at a time and then showed the result of each. That's a lot of repetitive code. This could have both cut down on copy-pasting and helped to propagate changes in an earlier plot to the later ones. Next time for sure.

I think that this is above all else the reason that I use Arch. Arch Linux makes creating packages trivial, basically just wrapping build instructions into a shell script template. Arch handles the rest. The build systems for deb or rpm packages don't come close, and good luck rolling your own flatpak.

This allows me to use pacman for everything outside of my home directory. Pacman is practically the central feature of my computer, and it's wonderful. I'm sure those Nix people can relate, though I guess my method is a bit less robust.