Notices by lhp (lhp@mastodon.social), page 2

Initially starting out as a fun hack in between talks at a conference, iwd.el is now - thanks to a contributor - reasonably functional and can be used to connect to wireless networks via #emacs (if you are using iwd standalone).

https://git.sr.ht/~leon_plickat/iwd-el

@prahou I showed you my ~/.config/emacs/init.el, please respond

@dnkl however the protocol isn't really documented. There is an assuan doc for the wire protocol and there is one for the pinentry protocol, but they disagree with each other and with reality. Also sometimes they use "character" when it really should be "byte". Not that anything actually checks line lenghts. Pinentry protocol requires lines lengths which are technically illegal with assuan, but no one seems to care there either...

@dnkl when I implemented the pinentry protocol, first I copied the messages sent by the "official" pinentry implementations bit-for-bit. It did not work. Then I tried following the protocol spec, which did end up working, kinda. However this means the official ones are doing it wrong, but somehow still work in a way I could not reproduce nor did I ever figure out why they are allowed to do it wrong while my program gets killed by gpg-agent.

@dnkl the protocol actually has a way to set $DISPLAY without needing a command arg. In fact, there are two different ways to set various variables.

Also there is a handy error code to indicate your implementation doesn't support some feature. But don't think about using it, because gpg-agent will just abort. Instead always say OK and silently drop it.

gpg is the best argument against hand-rolling IPC.

Just merged patches updating wayprompt, a #wayland native pinentry implementation using the layer-shell, to #zig 0.13. It was stuck on 0.11 for a while, so this is - at the very least - a nice QoL improvement for users compiling from source.

Thanks @uncomfyhalomacro for doing the work! I only needed to change a few minor things. And thanks #emacs and magit for making the workflow of pulling patches from another remote, then reviewing and amending them, very comfortable.

@aral @nekohayo @nah @fvsch @sonny @matt You literally were just told - multiple times - that people know the problem and care about it and that this change is not even in the next version precisely because people are aware of this and other problems. You were told there are active and funded efforts to imprve the linux accessibility stack. Isn't that exactly what you want? Your last message in this thread feels very dishonest. Maybe there is a miscommunication here?

@lispi314 @dushman @astrid It would be nicer though if it used scheme instead (really sad guile emacs died), used more system libraries (slowly getting there) and shipped less lisp code by default. The last point is not because "bloat", but because if you want non-standard behaviour you have to override a lot of stuff which often feals janky. F.e. evil just does not feel good and it's a popular package. And if you want less popular things like kakoune-like keybinds and the experience is just sad