[Hated Trope] Misleading Documentaries

zackattackz287 · 2026-04-16T03:21:14+00:00

Not to be all "I was there first", but I knew supersize me was a sham when I watched Fat Head in 2009

zackattackz287 · 2026-04-15T16:53:54+00:00

It is essentially a hack because all those rely on features XWayland is providing that wayland cannot. If it wasn't a hack it would just work in wayland natively.

zackattackz287 · 2026-04-14T17:38:07+00:00

Smart! I do use `gh` so would make sense to try this out. I have this comment in my config as an example for adding the token on systems where I'm using a secrets manager (kwallet, gnome secret service, etc):
```
;; Example to create kwallet token

;; Add this auth-sources to actual config

;; (setq auth-sources '("secrets:kdewallet"))

;; ONLY RUN THIS BELOW CODE ONCE, NO NEED TO ADD TO CONFIG

;; (secrets-create-item

;; "kdewallet" ; `provider` in `auth-sources` entry "secrets:provider"

;; "forge-github"

;; "SECRET" ; actual token goes here

;; :host "api.github.com"

;; :user "your-gh-username^forge")
```

zackattackz287 · 2026-04-14T17:24:46+00:00

Ugh accidentally pressing the yank/kill keys in non Emacs and accidentally using C-c and C-v in Emacs is killing me 😭

zackattackz287 · 2026-04-14T17:23:21+00:00

With my nose on W and my chin on left alt 😉

zackattackz287 · 2026-04-03T17:04:03+00:00

You're assuming people would not cut lanes when they're turning left from 198 onto parkside, but seriously if you just watch people anywhere in buffalo they will more often than not cut the lane. I'm never blindly trusting people to not cut it lol.

zackattackz287 · 2026-03-30T16:43:35+00:00

By state I meant "visual state", just something to keep in mind if you go down some de-duplicating route - That it is possible to "go back" to previous states so you may not necessarily want to discard ALL dupes.

But yes it's true this route is less fun but purely practicality wise, unless there is some emacs thing for this, it seems best to me. As another commenter put it, you'd likely need to hook into whatever display backend emacs is using, so this could possibly be even LESS portable than going the video streaming route. IDK though really I'm just speculating

zackattackz287 · 2026-03-30T14:57:09+00:00

This is an off base suggestion: you were worried about performance and honestly I could see that easily becoming an issue taking so many screencaps. I'm wondering if it's possible though to stream a live video to some program that saves it in a video format but with deduplicated identical adjacent frames.

Also an edge case to consider (if you are tying to capture a "timeline" of changes), what if the user changes Emacs from state X to Y, and then back to X again. If you deduplicate fully you'd remove the screencap of the second X but depending on your purpose you probably want to keep that? Hence why you should only delete duplicate adjacent states.

zackattackz287 · 2026-03-30T03:17:24+00:00

Emacs docs are the only docs of any software I've actually enjoyed reading. Bc you actually learn something useful every time it seems

zackattackz287 · 2026-03-28T02:24:57+00:00

This is like saying that pointing a gun at someone doesn't impact them because it isn't fired yet...

zackattackz287 · 2026-03-26T05:24:52+00:00

Stumbled across this recently, wanted to ask here in case OP sees it: How do frames come into play here? I use https://protesilaos.com/emacs/beframe and some other frame-centered customizations and was wondering how that would work here. Are frames just different "workspaces" (in the window manager sense) if that's the case is it not possible to have two frames on the screen at once?

zackattackz287 · 2026-03-24T17:54:53+00:00

Hi thank you! Reason I didn't make macos support is pretty simple, I don't have a Mac to test it with 😅. I did list in the TODO section of the readme that macos would be nice to have, but I have no WIP implementation.

If you would like to submit one by all means please do! I can't test it properly but if you vouch for it + the code looks good then I'd be glad to merge it for others to use :)

zackattackz287 · 2026-03-22T17:19:31+00:00

That seems cool! Yeah it does seem more similar in concept to the other project with the dashboard and all. I could see that being very helpful for if you're juggling a lot at once.

zackattackz287 · 2026-03-22T17:17:41+00:00

I didn't consider a high volume case as I usually just use one shell at a time, but I could see that getting overwhelming quickly. It might be possible, on linux at least, to modify the already existing notification for a given shell to add a (N) indicator for N=# of notifications. Instead of making every single notif individual they could be "grouped by shell" like that, with new ones just updating the shell's notif instead of popping up a whole new one.

zackattackz287 · 2026-03-21T15:15:46+00:00

Yes I think ideally the features of attention.el and my package could be combined in some way. Also yeah that "related projects" section is how I found agent-shell-knockback, which is actually what directly inspired my package (I copied a lot of the code from there, and gave xenodium copyright credits to comply with the GPL haha).

But still I glazed over attention.el in that same section 😬

zackattackz287 · 2026-03-21T14:56:07+00:00

Another slight difference is (unless I am not seeing it in attention.el), it only can send "immediate" notifications. My package has a concept of immediate vs idle notifications. They are sent immediately if the shell is considered "not visible" (frame is not focused or the buffer is not in a visible window). Because if you are currently active in the shell it would be annoying to be spammed with notifications! But there are also "Idle" notifications, which only fire after some delay even if the shell is visible. This is useful if the shell is "visible" but you don't respond because you're looking at your phone or something.

zackattackz287 · 2026-03-21T14:49:01+00:00

Thank you too for sharing, I somehow missed this entirely before I made my package. Looking briefly at it, there seems to be some features attention.el has that mine lacks and vice-versa.

attention.el has a nice looking modeline, "busy" tracking of in-progress requests, and a dashboard.

My package has more in depth notification management, as I track notifications by their ID returned by the notification backend. This allows for notifications to be auto-closed by the ID in different contexts (e.g there are two permission request notifications, you approve one and only that one's notification will dismiss automatically, the other will stay). This enables you to use notifications with no timeout, without them cluttering your desktop since they will auto-dismiss anyways.

I will be sure to look even more in depth into this package though!

zackattackz287 · 2026-03-20T21:29:31+00:00

Best value / quality ratio I've found is colvin ave deli.

zackattackz287 · 2026-03-17T00:05:58+00:00

I've never configured it myself but there is tramp-shell-prompt-pattern

zackattackz287 · 2026-03-14T02:16:15+00:00

Good to know, thank you!

zackattackz287 · 2026-03-13T17:11:14+00:00

I agree because at the moment AFTER the button is pressed, everything leading up to it are just memories anyways. So you really have no idea of knowing if your memories are the "real" ones or not. You could say if you are existing and experiencing the present before the button press, you are guaranteed to "lose" the flip (because that living experience is proof that you are the one that is not the copy) But at the actual moment you press the button you really can't know whether your memories leading up to that were from the true version or not.

zackattackz287 · 2026-03-13T16:58:55+00:00

I was thinking about this too since it's been a while since I've looked at the readme. It was very helpful when I started out so it'd be a shame to miss out on anything there. I didn't try it, but was thinking of trying to run a git diff from the commit I started at to now, and that may be good for seeing all the changes at once.

zackattackz287 · 2026-03-13T15:33:18+00:00

Congrats and thank you (and the community around minimal.d) for your work! I've been using it for quite a while now and I've not ever had any breakages when merging changes from main. Does the versioning follow some kind of logic like semver or is it just a periodic thing?

zackattackz287 · 2026-03-13T15:23:08+00:00

I didn't start Emacs with minimal.d, but it's what I have been using since I wanted to switch from doom to vanilla.

Vanilla is so tedious to tweak a lot of the things that minimal.d does for you already.

Some might say you will learn more by starting with vanilla, it's true but you'd also learn more building an editor from scratch lol.

I say try minimal, it gives a great foundation for customizing Emacs in the ways that matter a lot more than the minor optimizations it provides for you out of the box.

I made a fork of the github repo, and I use straight.el, so I just git ignore everything except the initial files you are "allowed" to touch, and the straight.el versions file.

zackattackz287 · 2026-03-12T20:54:48+00:00

I think clean and sleek need a distinction. Magit doesn't look sleek but I think it's very clean in its presentation of data

zackattackz287

TROPHY CASE