Re: EXWM
Arun Isaac writes: Hello, >> My suggestion is simple: remove the added layer of complexity introduced >> by the .exwm file; don't force a default Exwm config on the user. > > I think I agree with you now. I checked, and exwm indeed does not run > when emacs is opened in the console even though my exwm config is > defined in my ~/.emacs. Interesting. So the extra, unneccesary initialization code does not hurt there. I just tried adding my ~/.exwm into my init.el and running a nested emacs and now I get a GUI dialog: Replace existing window manager? Y/N Not great! Not very suprisingly, the extra unnecessary initialization /does/ hurt here. > So, I see no reason to continue having ~/.exwm. If no one else has any > objections, please do send a patch fixing this. I would very much like for this nested emacs issue to be addressed first. I just don't really see the point in mixing two bits of code that are meant to run in different scenarios, and then disabling one of them. Greetings, Janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
Using G-Expressions for public keys (substitutes and possibly more)
Hi Guix, let's say I wanted to add my own substitute server to my config.scm. At the time of writing, I would have to add said server's public key to the authorized-keys of my guix-configuration like so: (cons* (local-file "my-key.pub") %default-authorized-guix-keys) or similarily with append. This local-file incantation is however pretty weak. It changes based on the current working directory and even if I were to use an absolute path, I'd have to copy both that file and the config.scm to a new machine were I to use the same configuration there as well. However, it turns out that the format for said key files is some actually pretty readable Lisp-esque stuff. For instance, an ECC key reads like (public-key (ecc (curve CURVE) (q #Q#))) with spaces omitted for simplicity. Were it not for the (q #Q#) bit, we could construct it using scheme- file. In fact, it is so simple that in my local config I now do exactly that. (define-record-type* ...) (define-gexp-compiler (ecc-key-compiler (ecc-key ) ...) ...) (ecc-key (name "my-key.pub") (curve 'Ed25519) (q "ABCDE...")) Could/should we support such formats out of the box? WDYT? Regards, Liliana
