Notices by @kmicu@mastodon.social (kmicu@mastodon.social), page 4

@sirgazil Yep, that verbose verification message is confusing for newcomers.

Manual could show an example verification output to avoid similar doubts.

FYI ‘sha256sum guix-binary-1.0.0.x86_64-linux.tar.xz’ returns
‘630c53703ce0abdfb6def2c21afa7e1d2a14abccae86126143508dc6a2b5c987 guix-binary-1.0.0.x86_64-linux.tar.xz’

@lthms That’s understandable. No rush; take your time 😺

(If you make your setup work once on Guix/Nix it will work forever though. That’s nice.)

@otini that’s correct on distros following FSDG†.

Outside of official Guix places we can do whatever we want including switching to upstream kernel Linux, installing firmware blobs, or even proprietary user apps. (There are already examples of those e.g. on Gitlab or Github).

Inside official Guix places there is no support for proprietary software.

†https://www.gnu.org/distros/free-system-distribution-guidelines.html.en

@Kensan Finally a proper *summit*.

@amdt I’ve no recommendations. Alas with lisp we have total freedom and total freedom is naturally messy. 🤷

@amdt Pretty much yes. For me use‑package’s more about forming clear config structure and habits. E.g. with use-package it’s easier (for me) to keep all gnus related tweaks inside (use‑package gnus …) and not all around my .emacs file.

I have a feeling .emacs is less messy thanks to it.

Enclosed (use‑package …) declarations and :keywords give more consistency and rhythm to my config file.

For me it’s about look&feel and sorry that sounds abstract and subjective.

@amdt use-package is not a better way but only a different style of configuration that *could be* beneficial when .emacs starts to be very messy and long.

Using org-mode and a literate configuration to tangle .emacs is another style to keep long config tidy.

When config is relatively short those styles have more cons than pros.

It’s a matter of preference; not a One True Way™ 😺

@amdt quoting John Wiegley’s original goal could also help:

“The `use-package' declaration macro allows you to *isolate* package configuration in your ".emacs" in a way that is performance-oriented *and*, well, just tidy. I created it because I have over 80 packages that I use in Emacs, and things were getting difficult to manage. Yet with this utility my total load time is just under 1 second, with no loss of functionality!” [emphasis mine].

@amdt for *me* it’s :chord, :disabled, :if, :diminish, :load-path, :defines, :requires, :after
*and* the fact that I could write all of those by hand in stock Emacs *but* use-package offers me a consistent configuration interface.
After that I can profile my config startup with use‑package‑report.

As of today my .emacs has ~8k lines but Emacs starts under 2 seconds.

@amdt use-package is a configuration interface (it doesn’t replace built‑in package manager but uses it under the hood).

If we only use basic functionality from use-package like :bind then use-package is unnecessary.

@technomancy

“Sautern

Satern has numurous moons and has buitiful rings. some of the chuncks making the rings are the size of your house!”

Please, more.

@MadestMadness I’d just like to interject for a moment. Guix is not a kernel hence Guix System is the best GNU/Linux distribution *and* the best GNU/Hurd distribution.
🤭

@pzmyers To be fair EHT team members have some issues with that too “There are more of us. Katie's algorithm, despite the media's stance, was not used to produce this image. There were three algorithms used and combined to form the final image, and a team of 40 scientists part of that aspect of the project (including myself and more women).”
https://mobile.twitter.com/SaraIssaoun/status/1116304522660519936

@Morn Tell me about it.

@feld
Not only generalizing about GPL based on kernel’s GPLv2 but also making a strong conclusions based on one data point.

Thank you. Me and my OpenWRT router had a good laugh 😹

@conservancy

@sirgazil
“The two most popular window configuration packages are elscreen and escreen. Both are fairly old and have their share of bugs. The closest package I've found so far to eyebrowse with workspace-specific buffers would be perspective. wconf is a minimal alternative with half the lines of code (and features). To have fancy features such as morphing, try workgroups or workgroups2.”
— https://github.com/wasamasa/eyebrowse

We could also force Emacs to only use frames and then manage them in a WM.

A stream anole lizard attempts to eat a very large blue morpho butterfly it has captured.

Photo by David Herasimtschuk.

@hund I dislike compiling Qt so much that I don’t use Qt apps anymore 🤭