IRC channel logs
2026-01-14.log
back to list of logs
<bdju>If anyone's taking requests for the next stable release ISO, I would like to see an option to do LUKS + btrfs together in the guided installer, and more options in the DE section, like sway and niri. <bdju>Fedora ships a Sway spin now so you could probably look at their package grouping for inspiration there. <mange>The DE options are in gnu/installer/services.scm. I expect a PR would be welcome. <Dora>Hello, can you help me please to understand why my pure guix OS has a value 2052 in /proc/sys/kernel/tainted ? <Dora>I don't see any tainted info in the dmesg, wtf? <csantosb>Try this: for i in $(seq 18); do echo $(($i-1)) $((2052>>($i-1)&1));done <csantosb>To show the individual bits, this will provide a hint on the origin <Dora>I'm using an old Lenovo t400 with custom coreboot - that could be the reason ? <jlicht>How do I force guix to 're-fetch' the keyring branch on a personal fork of guix when using a channels.scm file with guix pull? I keep having to destroy my entire cache to work around this recently <identity>Dora: that could explain bit 11; i would guess bit 2 is because of old CPU microcode <Dora>dmesg in the very beginning is showing that '[ 0.000000] x86/CPU: Running old microcode' <Dora>btw. and what is official GNU stand related with updating microcode is it considered as binary blob ? <identity>if you can not update the proprietary firmware, it is good. you can update microcode, so the best course of action is to not, or so they say. <Dora>so there is no way to use guix on not tained linux ? <identity>but, for now, i would recommend turning off hyperthreading in the BIOS settings, at the very least <Dora>and what's the best GNU endorsed hardware for guix ? <efraim>I use a modern CPU with an old graphics card, but IMO the best option is normally whatever hardware you already have <identity>the hardware is always free-er on the other side <fanquake>Where can I find/download tarballs to test 1.5.0rc1 ? (for aarch64) <fanquake>Basically to run install.sh and set GUIX_BINARY_FILE_NAME <cdegroot>Dora: I'm on AMD, that works well for both desktop and laptop (the laptop requires a non-free driver for the WiFi card, alas, I still need to open it up and replace it, but that's the only thing I had trouble with) <m4xxed>Hey, I figure that feature / team-branches in guix don't need to be in a workable state, and when I run `guix time-machine --branch=rust-team -- guix shell rust` then It complains that it does not find `(rust-cbindgen-0.29)` and I checked out the current latest commit of rust-team's branch and checked and there is only `(rust-cbindgen-0.28)` . Is <m4xxed>there anything I can do about that so that I have a working shell with rust > 1.85? :) <yelninei>m4xxed: If 1.88 is recent enough it is available but hidden, access it with e.g .guix build -e '(@ (gnu packages rust) rust-1.88)'. if you need later versions you could define your own variant similarly how rust.scm defines new rust versions <m4xxed>yelninei would that also work with the time-machine command that I used? <yelninei>assuming there are no errors trying to build the branch yes <Rutherther>m4xxed: are you sure you are building only guix and not other channels? Recently rust-team branch worked for me fine <m4xxed>Rutherther I might be building the nonguix channel aswell, it is in my channel.scm file... I'll check it now <loquatdev>Hello, everyone. I get the impression that Emacs is the standard editor used by Guix hackers. However, I personally prefer the Kakoune editor. Is there anyone else here who has managed to better integrate Guix workflows into their editor of choice? <loquatdev>I'm considering picking up Emacs because it really does sound great, but it also sounds like a bit of work to learn a new editor. I figured I might as well ask before I start making the switch. <m4xxed>Rutherther yep, you were right, this works with a custom `channels.scm` file: `guix time-machine --branch=rust=branch --channels=channels.scm -- shell rust rust:cargo` <identity>loquatdev: while (info "(guix) Alternative Setups") does not mention Kakoune, still see <identity>i would also recommend against guile-studio; learning Emacs is easier when it is not trying to pretend to be something that it is not <GNUtoo>(1) Are there known issues that prevent retrieving source from software heritage ? <GNUtoo>(2) Is the code responsible for that in the daemon or in the rest? <loquatdev>identity: Thank you, I hadn't seen that. I'll look into some of the scripts and see if there's a good solution. <loquatdev>I do see many people trying to "convert" people to Emacs by advertising bundled versions of it, but I agree that that is a little misleading. <loquatdev>Would you personally recommend Emacs, or maybe some other editor? <loquatdev>I think it might be best to just go with it since it's the best tool for the job in this scenario. <cdegroot>The advantage of Emacs is that I learned it in the late '80s and I'm still profiting from that investment. No other editor/IDE/window manager/email reader/news reader/organizer/... has that long term ROI. <ente>I got into emacs with spacemacs and later doom <identity>loquatdev: Emacs is bad, but i am yet to see anything better <ente>can't say the ROI is that great, it often breaks <yelninei>ACTION is confused how hurdish login can verify passwords without suid <ente>of course if you're doing lisp development it has a bunch of great features for that, or great gdb integration for C programming, and so on <identity>…and if not, you can throw together some Elisp that will do that <ente>but using mu4e for email has been a bit of a hassle <cdegroot>ente: must be your config? It never breaks on me (I'm on Doom, decided to stop handrolling after it appeared and I tested it) <ente>cdegroot: I barely have any config <loquatdev>I might use it if only for Lisp development. What is unattractive for me about Emacs is that it seems to suffer from scope creep. I prefer applications that perform hyper-specific tasks, and Emacs seems like it tends to swallow roles faster than any other program. I'm sure it can be configured to be minimal, though. <identity>loquatdev: that is like saying Python suffers from scope creep because of all the libraries people wrote for it; nobody forces you to use any of that, and it will probably never get loaded <loquatdev>identity: Fair point. I don't mean to criticize Emacs itself - that's just my impression. <GNUtoo>Maybe it's an issue with i686, I'll tr to narrow it down <cdegroot>I don't know of many editors that can also do X11 window management. It's more a platform than anything else. But you can configure it in a very lightweight way, just Scheme support and you're good to go. <ente>I like that it's generally well integrated <ente>you can link to a message id in an org-mode file and if you open that link it takes you to your mail reader where you can read that mail <identity>yeah, if you are just starting out i would get just Geiser and not bother with anything else past the tutorial <ente>there's no real reason this should be restricted to only work within emacs though <loquatdev>I might have been exposed to many "Emacs is an Oprating System" memes, haha. I'll give it a shot. <ente>it's just that desktop-linux tools rarely interoperate with tools that came from somewhere else <loquatdev>Has anyone read Mickey Peterson's "Mastering Emacs" book? If so, would you recommend it? <identity>loquatdev: i never read anything besides what comes with Emacs and some blog posts i found online. i think Mickey P. posts about Emacs online, too <ente>I read the doom/spacemacs tutorial and other than that a bunch of M-x info <ente>still prefer vim editing keys but didn't want to configure everything myself which is why I settled on those <loquatdev>Is terminal Emacs a good place to start if I'm just aiming for basic editor functionality? <loquatdev>I that what the `emacs-minimal` Guix package is for? <ente>terminal emacs is decent but I prefer graphical <ente>I usually have `emacs --daemon` running on session start and create frames in that with `emacsclient` when I want to edit a file from a terminal <ente>(emacsclient can also create a terminal client in the same terminal you're running the command from, it mostly saves on startup time.. I just ended up barely using terminal editing anymore) <cdegroot>I have muscle memory to use `vi` for editing, so that's aliased now to emacsclient. For getting started, if you have a GUI, use that. There's menus and stuff so less to remember when starting out. <cdegroot>(Emacs is the best Vi implementation out there, I'll die on this hill ;-)) <identity>loquatdev: i would advise against using Emacs in a textual terminal if you can use a graphical one; do not use emacs-minimal, it is mainly intended for use by the build system for Elisp packages, just use ‘emacs’, or ‘emacs-pgtk’ if you are on Wayland <ente>the main use case for emacs in a terminal for me is when I'm editing files on a remote server and tramp-mode is too unbearably slow to use <loquatdev>Thanks, identity. I'll take your word for it. <ente>but then oftentimes I just use vim instead <loquatdev>Is there an important difference between 'emacs' and 'emacs-pgtk'? <loquatdev>I'm guessing the pgtk version just uses GTK for the graphical backend and regular emacs uses some special custom one. <loquatdev>By the way, thanks for your help, everyone. Y'all are great. <identity>loquatdev: normally Emacs just wings it and uses raw X11 APIs along with GTK ones; not so in a Pure-GTK build <ieure>I also strongly prefer GUI Emacs. <ieure>There are things about Emacs that are bad -- opening large files / files with long lines is the thing that annoys me the most, its single-threadedness is a close second. But once you get used to the tight integration of tools it offers, nothing else compares. <civodul>this long line issue remains a mystery to me <civodul>there’s even a mode that’s supposed to work around it (doesn’t work for me) <ieure>civodul, Yeah, not sure what the deal is with it. But it stinks! <PotentialUser-37>Hello, I am new to guix. I can see there is a package available for xe-guest-utilities. I have tried installing it. I am then able to run xe-daemon. However, I cannot for the life of me figure out how to make it a service that starts on boot. I have found some reference to a service for it on codeberg, but the documentation is not good enough for a <PotentialUser-37>noob like me to understand what to do next. Any help would be much appreciated <attila_lendvai>PotentialUser-37, a word of warning: unfortunately the word 'service' is used in guix for stuff that is more like a component, i.e. something that just adds things like files without starting any process. this got me confused for quite some time initially. <Rutherther>the xe-guest-utilities-service-type does add files necessary for shepherd to start the daemon as a shepherd service though:)