IRC channel logs


back to list of logs

<the_tubular>How can I tell if this has --with-native-compilation ?
<KimJongWell>ceephax: I was thinking a guix container, to run it on boot to use as a virtual machine
<KimJongWell>with systemd, we have machinectl for example, it can start containers on boot through a
<KimJongWell>I'm not sure how you'd approach this, do you write a shell script and somehow run it with Shepherd, or is there an idiomatic Guix-way
***rekado_ is now known as rekado
<KimJongWell>is it possible to encrypt a string in the system config
<KimJongWell>I'm thinking of adding a private key, it would have been cool if the guix command stopped to ask for password
<GNUtoo>jpoiret: here I only need valgrind to work during the tests. Though I can try.
<GNUtoo>I'll try tomorrow though
***marwan5 is now known as marwan
<the_tubular>Will emacs-next always exist ? I'm inheriting a packages from it, can it just be remove one day ?
<zacchae[m]>Hi Guix! I'm sending this message through my matrix home server which is now managed by guix home :3
<kitty1>ayyy nice uwu , while I'm not exactly a fan of matrix, I def need to mess with guix managing hosting things some time hah
<kitty1>thats very cool :3
<zacchae[m]>Thanks. I see it as a stepping stone after getting syncthing working. Next goal is managing email.
<zacchae[m]>Any particular reason you don't like matrix?
<zacchae[m]>Also, I don't see any guix home in the cookbook. Are these the sort of things that should be added to it? It definitely would have been nice to see examples when I was trying to make my home config
<kitty1>zacchae[m]: I don't like matrix because for the most part it is just an overly bloated web-dev clone of the more solid XMPP
<zacchae[m]>On a related note, any one know a way to ensure home services are launched on boot? My guess is that I need to spawn SOME proccess owned by my user on boot. Maybe just wrap tmux in a shepherd service?
<bjc>i don't believe the user shepherd service is started automatically on boot, but only when you first log in
<atka>hi guix, any idea what is going on with this
<atka>guix system: error: open-file: No such file or directory: "/var/guix/profiles/system-1-link/parameters"
<atka>when running guix system list-generations
<atka>also I did an update earlier on two machines, after guix pull && sudo guix system reconfigure neither had sudo or su root abilites until a reboot with the physical power button.
<atka>I appear to be unable to roll-back or switch-generations as well
***BSlade[m] is now known as beslayed[m]
<littlebobeep>kitty1: Are you objecting to the Element/Riot client or the Matrix protocol itself?
<kitty1>littlebobeep: mostly to the clients, but the protocol itself at a glance seems a bit more "closed-down-this-is-ours" compared to XMPPs of "everything is made to be easy to understand and extend upon". I don't think XMPP is perfect for the role, but, I like it a lot more than Matrix from the little bits of knowledge I do have. Also in practice it seems a lot more stable and easier for people to host
<littlebobeep>kitty1: I think element is the only Electron Matrix client
<PrincessCelestia>Specifically if you want non element I think ive heard good things of nheko
<kitty1>nheko broke on my randomly, it just like, started to flicker and shit lmao, nheko is ok but its not really my style; I like terminal applications more ngl, and profanity has plenty of good ones of those and good mobile clients etc. their desktop clients can feel a little out of 2003 but they are rock solid regardless haha
<PrincessCelestia>nice nice
<kitty1>XMPP has plenty of good ones* profanity is one ive tried but I plan on messing with more.
<kitty1>well, I meant as in, profanity is more than good enough but im just like, curious lmao
<kitty1>I digress lmao, if anyone here hasn't checked out XMPP before they have a lot of nice documentation on their specification and the specifications of their extensions
<littlebobeep>kitty1: Try ement.el
<kitty1>littlebobeep: ah, I might mess with that some time for the people on matrix ; honestly I really wish there was an emacs client for XMPP that didn't die a few hears back haha
<kitty1>not familiar with
<kitty1>one moment brb haha
<littlebobeep>kitty1: Are ou saying this died??
<GNUverkty[m]>Last release of it was in 2009 so I would say it's dead
<kitty1>there is one that is called emacs-jabber that was last released in 2018, looked like quite a few people where using it but nobody has maintained it since 2018
<kitty1>its kinda surprising that there isn't any actively maintained XMPP clients for emacs that I can find ngl, because there are lots of really active clients for XMPP
<munksgaard>Whenever I try to build something with pre-inst-env, e.g. `./pre-inst-env guix build -f ghc-base-orphans.scm` where ghc-base-orphans.scm is this file, it's like guix never really gets started. It hans at the end of this output for a couple of minutes before silently failing:
<munksgaard>Anyone know what's going on?
<munksgaard>And those notes about having to recompile scm files is the same every time I run guix build, even though I haven't changed anything since last
<atka>I have found something interesting with sudo guix system reconfigure over ssh, if I issue that command then log out, when I log back in I get: -bash: /etc/profile: Permission denied, -bash: /etc/bashrc: Permission denied and sudo stops working, example:
<atka> ~$ sudo tail -f /var/log/messages | grep -i sshd
<atka>sudo: /run/current-system/profile/bin/sudo must be owned by uid 0 and have the setuid bit sety
<atka>but if I reboot everything works normally, but its hard to reboot a remote server when sudo reboot doesn't work..
<littlebobeep>kitty1: Where can I find emacs-jabber (inventive name haha)
<littlebobeep>Cool looks like it supports MUC
***aya is now known as gyara
<jpoiret>munksgaard: your scm files are out of date, and you should recompile them using `make`
<jpoiret>.go files * rather
<munksgaard>jpoiret: I thought I had tried that, but I just found out about `make clean-go`, so I'm trying that out now
<jpoiret>when using guix commands, if any scm files are out of date they won't be recompiled to go files but just used as-is, leading to the slow behavior you're experiencing most likely
<jpoiret>just make should be enough most of the time
<jpoiret>make clean-go is when guix specifically complains about abi mismatch, or other weird behavior
<munksgaard>jpoiret: I see. Thanks for helping out.
<civodul>Hello Guix!
<rekado>Hi Guix
<rekado>I’ll merge today.
***slep is now known as cel_b
<civodul>howdy rekado!
<bovid-19>hello guix!
<civodul>i didn't follow the wip-pyyaml work but it must be nice :-)
<cbaines>morning o/
<cbaines>civodul, I was away last week, but I did pick up your message about bordeaux.guix. compressing tarballs
<civodul>hey cbaines! alright
<cbaines>I also saw apteryx mentioning about the slow connections to bordeaux.guix, which I've been seeing as well
<cbaines>what would be good is to record these things somewhere more permanent than IRC, maybe debbugs?
<rekado>civodul: wip-pyyaml is just two commits :)
<rekado>lots of rebuilds but nothing interesting
<tschilptschilp23>hello guix!
<tschilptschilp23>Is there a way to extract packages listed in the system-config to a manifest file? Like it can be done for the home-config via ~guix package --export-manifest -p ~/.guix-home/profile > file~?
<civodul>tschilptschilp23: hi! yes, same thing:
<civodul>guix package -p /run/current-system/profile --export-manifest
<tschilptschilp23>civodul: great, thanks!
<tschilptschilp23>I noticed that the exported manifests sometimes contain names of 'hidden packages', which can make it somewhat complicated to do ~guix package -m EXPORTEDMANIFEST~. Is there a way to do a 'fuzzy' guix search, which would point me to the 'parent package' via terminal commands? At the moment I use emacs' 'guix-help' to locate it, and can work with that. But it would be very tempting to automate this.
<tschilptschilp23>*this 'replacement work'
<civodul>tschilptschilp23: yes, i noticed that; that's a bug
<littlebobeep>tschilptschilp23: What does it mean hidden packages?
<tschilptschilp23>civodul: thanks -- so for now 'guix-help'!
<tschilptschilp23>littlebobeep: I do not know enough about guix/guile to give an explanation on this concept unfortunately. In practice it means to me, that the package definition in the corresponding module does not start with ~(define public PACKAGE (package (name "packagename") [...]~ but rather ~(define public PACKAGE (hidden-package (package "packagename") [...]~, which makes it 'invisible' to commands like 'guix package' or 'guix search'. I cannot
<tschilptschilp23>tell the proper terminology for what I label PACKAGE above, maybe someone can chime in?
<AwesomeAdam54321>tschilptschilp23: It's called a package variable name
<AIM[m]>Do I need to enable both alsa and pulseaudio sound service?
<AIM[m]>Idk, I've not digged deep into that
<AwesomeAdam54321>AIM[m]: I don't think so, PulseAudio uses ALSA for sound
<wdkrnls>speaking of audio, is there some audio control software anyone suggests? the last system upgrade I did fried my audio and I'm trying to understand why.
<bovid-19>wdkrnls: what do you mean by audio control software?
<bovid-19>maybe pavucontrol?
<wdkrnls>I guess I'm looking for a nicer version alsamixer which lets you test that it is actually working.
<wdkrnls>I was using pavucontrol, but it doesn't seem to do everything I need.
<wdkrnls>Before when sound was working, it wasn't really working the way I expected unless I was using a desktop environment.
<wdkrnls>I feel like maybe guix isn't ordering the sound devices right, but that's only an uninformed guess as to what is happening based on my alsa shows me.
<wdkrnls>alsamixer doesn't make it easy for me to test that sound is actually working and not just appearing to work according to some pixels on the screen.
<bovid-19>I've been meaning to look into pipewire for a while, but I didn't get to it yet. But there's someone who made a home service for it. Maybe worth trying if that helps?
<wdkrnls>thanks, I'll have a look.
<bovid-19>good luck!
<jpoiret>pipewire works very well on Guix, you can remove the pulseaudio service and instead start pipewire and pipewire-pulse
<tribals>Hi folks!
<tribals>I want to restrict `guix` command to only allowed users of whole system - I'm using Guix System as well. So I decided to use /etc/sudoers. There is `sudoers-file` field for `operating-system` which is nice. Now time to write sudoers rule. Mine is very simple: I want to limit guix command only to users of specific group. But I need to specify absolute `guix` command path in produced sudoers file. How to do that in my `os.scm`?
<tribals>In other words, how to write proper Cmd_Alias for `guix` command in `(operating-system (sudoers-file ...) ...)` definition?
<civodul>tribals: hi! note that "guix" is not just for root; any unprivileged user can run it
<civodul>so i'm not sure whether sudo can be of any help
<tribals>Hmm... Do I need sudo to run `guix system reconfigure`?
<tribals>More likely, I want to restrict "administrative" part of guix to specific user (or group)
<civodul>tricon: "guix system reconfigure" needs to run as root
<civodul>if you run it as non-root, it'll stop with "Permission denied" for the last steps
<civodul>(the first step is to build/download things, which it can do as non-root)
<civodul>sneek: seen jlicht
<sneek>jlicht was in #guix 15 days ago, saying: civodul: RE the blog post, "ten-year birthday" seems a bit weird to me; I'm not quite sure how to improve it though ("10 year anniversary", "10th birthday", or perhaps just "Guix will turn 10").
<civodul>anyone knows where jlicht's Node importer is?
<tribals>How to specify proper path to `guix` in sudoers, thoug?
<jonsger>sadly no idea, issues, gitlab, github don't seem to have it. Maybe on guix-devel ^ civodul
<mbkamble>Hello. Guix noob here. Can someone point me to an example for enabling fish shell as the login shell for a user in the Guix system configuration? TIA
<bovid-19>mbkamble: (shell (file-append fish "/bin/fish"))
***sneek_ is now known as sneek
<mbkamble>Do I need to add fish to packages list? Like so: (packages (append (list (specification->package "fish")) %base-packges)) ?
<bovid-19>You have to add 'shells' to 'use-package-modules'
<tschilptschilp23>tribals: you can add the given user to the group wheel in your config.scm, then the should be able to issue sudo (see the manually untouched /etc/sudoers!)
<tribals>I'm asking about something like that: `(format #f "Cmd_Alias GUIX_SYSTEM = ~a system *" (string-append guix "/bin/guix"))`
<tribals>I want more fine-grained control ))
<GNUtoo>jpoiret: I've tried that and it doesn't change anything, I'll keep trying things though
<GNUtoo>I found something strange though, the glibc that I add in the native-inputs is not the same that is being used somehow
<GNUtoo>The one in the (native-)inputs is /gnu/store/6p98zwbg5s28cmfi9qrccp88n3pym2b9-glibc-2.33
<GNUtoo>but valgrind says "Reading syms from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/lib/"
*GNUtoo wants to try mjw 's advize of using --extra-debuginfo-path= but I'd probably need the right path for that
<GNUtoo>Though I can hardcode it for now to test
<mekeor[m]>feature request: when you install or upgrade a package with a git-origin, guix clones the git-repository and checks out the appropriate commit, so that you can easily read and modify the package's source code, when you feel like doing so.
<bovid-19>mekeor[m]: good idea!
<GNUtoo>with guix shell valgrind coreutils, valgrind works but not with guix shell -D valgrind coreutils, so I'll try to fix it there first
<civodul>GNUtoo: did you try ?
<GNUtoo>Ah thanks a lot, I'll look
<GNUtoo>I used something like "/gnu/store/wznq4d1i3znqjhcribfr2m9ljyyrsdyd-glibc-2.33-debug/lib/debug/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33" instead, so I'll try that, thanks a lot
<mjw>GNUtoo, ah, cool, civodul knows what it really is.
<mjw>civodul, yeah, if it would be possible to keep the .symtab in (no need for full debuginfo, just the full symbol table is fine) that would really help out valgrind.
<civodul>mjw: hi! so that means --strip-debug instead of --strip-all, right?
<GNUtoo>I've still no luck with valgrind though, If I don't have glibc-final in native-inputs is it still possible to access it during the package builds?
<mjw>civodul, yes (or strip -g or strip -d or -strip -S for some weird reason there are 4 different options that all do the "right thing")
<mjw>GNUtoo, so the problem isn't valgrind, but the program you are "valgrinding", that program needs to use an that has a .symtab.
<mjw>But maybe I am not clear on what is which here
<GNUtoo>As I understand glibc-final is the glibc that is being used by valgrind and the program that is being valgrided
<GNUtoo>so somehow I need glibc-final:debug and not glibc:debug
<GNUtoo>And so that's probably what is lacking now: with guix shell -C and within packages it's probably not possible to refer to it that easily
<mjw>ok, then I am confused, sorry. I don't know the difference between glibc-final and glibc
<GNUtoo>and if I don't add it in the native-inputs or as package in guix shell it's probably not available
<GNUverkty[m]>AIM: Why not use pipewire?
<AIM[m]>I can actually
<GNUtoo>As I understand glibc-final is what pakcage uses, and the glibc package is not used by packages...
<GNUtoo>like if I valgrind ls from guix, ls will use from glibc-final
<GNUtoo>but I only know how to install glibc
<civodul>mjw: great, we'll change that strip option in core-updates then
<GNUverkty[m]>AIM[m]: then do it, it works better than crackleaudio :)
<GNUtoo>The problem it seems is that it's not exported: (define glibc-final
<mjw>at least it seems to explain why my setup works, it is 88 days out of date. Which seems to be before that core-updates merge.
<GNUtoo>guix build -e '(@@ (gnu packages commencement) glibc-final)'
<GNUtoo>I wonder if I can use that ^^^ somehow in packages
<AIM[m]>GNUverkty[m]: I will try that
<AIM[m]>My mic wasn't working initially
<GNUtoo>mjw: it might also be that you didn't try in the same context than me
<AIM[m]>Found that I had some erraneous kernel param
<AIM[m]>Idk from my old Arch Install
<mjw>yeah, this is a guix system setup
<GNUtoo>guix shell -C valgrind ls # <- This is isolated and has the issue I'm describing
<GNUtoo>But if I guix shell --pure for instance it works
<AIM[m]>I didn't know it wasn't working till now
<AIM[m]>Btw, anyone got ly installed on guix?
<hexo>thats not even googleble :(
<AIM[m]>hexo: Lythe display manager
<hexo>oh, nice!!! thanks
<AIM[m]>Seems very minimalistic
<AIM[m]>* Ly the display manager
<GNUverkty[m]>i have no idea how display managers work in guix but it shouldn't be hard to package
<GNUtoo>(there it works with valgrind -v --extra-debuginfo-path=/gnu/store/wznq4d1i3znqjhcribfr2m9ljyyrsdyd-glibc-2.33-debug/lib/debug/ ls)
<AIM[m]>Ly the*
<GNUverkty[m]>the hard part would be to make a service (i think?)
<cehteh>looks cool
<GNUtoo>I think it works now
<GNUtoo>I did something I don't understand though
<GNUtoo>in native-inputs I added that: ("libc:debug", (@@ (gnu packages commencement) glibc-final) "debug")
<GNUtoo>And I could then refer to it like that: (assoc-ref %build-inputs "libc:debug")
<GNUtoo>Thanks a lot to mjw civodul and jpoiret
<GNUtoo>btw, I'm not sure exactly how to bugreport or fix the underlying issue
<GNUtoo>Should I ask not to strip too much and add the valgrind log with it?
*GNUtoo should probably check if there is already a bug report about it
<jackhill>Is it useful to have multiple wireguard network devices (as opposed to adding more addresses and peers to a single one)? I notice that NetworkManager allows for creating many devices, but our wireguard-service-type does not.
<jackhill>I guess my question is, is it a bug that it does not? I had been using multiple devices with network manager to connect to logically separate wireguard netwoks (e.g. one for work and one for personal)
<GNUverkty[m]>Ugh, can't build gnunet-gtk on latest guix
<yewscion>Hey all, I have a `guix-home` that currently redownloads `texlive-texmf` (3.2GB) every time I run `guix pull`. Is there a guide somewhere that shows an example for pinning a package? I'm a bit confused about inferiors, which is all that's mentioned in the manual (that I've found so far, anyway).
<civodul>yewscion: hi! i'd recommend avoiding the monolithic 'texlive' package:
<civodul>if you do need it, you could remove it from your default profile and use "guix time-machine --commit=XYZ -- shell texlive"
<civodul>it'll be cached after the first use, so that'll avoid redownloads etc.
<peterpolidoro>running "./pre-inst-env guix edit PKG" from a local guix checkout opens PKG in read-only mode. How can you get it to open in editable mode?
<civodul>peterpolidoro: hi! if you run it from a writable checkout, it opens the writable copy of that checkout
<peterpolidoro>it is a writable checkout. if I just run "./boostrap" followed by "./configure --localstatedir=/var" and then run "./pre-inst-env guix edit PKG" it opens in read-only
<peterpolidoro>do I need to run "make" before pre-inst-env runs correctly?
<peterpolidoro>I only need to edit and build a single package, do I still need to run "make" before doing so?
<vagrantc>believe so
<peterpolidoro>I seem to be able to build a single package without running make
<peterpolidoro>but the edit command not working properly makes me wonder if make is indeed necessary
<vagrantc>are you sure the package you're building contains the modifications you've added?
<peterpolidoro>I just tried building with no modifications first
<peterpolidoro>I am running make now to see if it changes the behavior of guix edit
<peterpolidoro>it just takes 20 mins on my machine so I was hoping to avoid make unless it is necessary to modify a single package
<vagrantc>i've definitely seen it where when only some of the files were compiled into .go files, it would return old versions of things, presumably from the guix in your PATH
<vagrantc>to avoid surprises, you can run it ... you don't have to re-run it for every change you make (although if you make lots of changes it gets slower and slower eventually)
<bjc>where is ‘home-xdg-configuration-files-service-type’ defined? i tried looking in ‘(gnu home services xdg)’ but couldn't find it there
<bjc>i'm wondering how my home config is even working. the above xdg module wasn't being imported. i only added it to try and help geiser find things
<yewscion>civodul: Thanks for the link! I'll see about switching to the modular packages instead. Would You recommend doing as stated and only using them in a shell environment? Or is it okay to install them in a profile?
<peterpolidoro>running "make" before running "./pre-inst-env guix edit PKG" does open it in editable mode
<peterpolidoro>so I think you are right that it is just safer to run make before editing even a single package, thanks!
<maximed>peterpolidoro: The first "make" can take a while because it has to compile lots of file.
<maximed>However, if you then modify a single .scm file, then the next "make" will only have to compile that file
<maximed>which should be much faster than 20 min
<peterpolidoro>so you run "make" then "./pre-inst-env guix edit PKG" then "./pre-inst-env guix build PKG", how can you then run that newly built package? "./pre-inst-env PKG" does not seem to work
<vagrantc>so, looking at updating u-boot, wondering if i should switch to git for the origin rather than a tarball?
<vagrantc>the git origins are more likely to be cached on software heritage, but possibly at the expense of a larger download to download the git checkout vs. the (compressed) tarball?
<vagrantc>looks like the tarball is ~16MB bz2 compressed ... the checked out git repository ~200MB ...
<vagrantc>does the ncurses/tinfo defintion there look reasonable? i haven't worked a whole lot with package variants...
<vagrantc>tried to follow the same style as ncurses/gpm
<maximed>peterpolidoro: pre-inst-env expects some command, e.g. "./pre-inst-env guix build hello".
<maximed>You could do ./pre-inst-env guix build hello
<maximed>you'll eventually get a /gnu/store/...-hello-2.10 file name
<vagrantc>./pre-inst-env guix shell PKG
<maximed>then you can run /gnu/store/...-hello-2.10/bin/hello
<maximed>or what vagrantc suggests, that's much more convenient
<vagrantc>use guix shell a lot to test new things :)
<vagrantc>doesn't work so great for bootloaders... but many things it works well for :)
<peterpolidoro>oh yes ./pre-inst-env guix shell PKG works great, thanks!
<peterpolidoro>actually ./pre-inst-env guix shell -- PKG
<maximed>peterpolidoro: ./pre-inst-env guix shell -- PKG probably doesn't do what you would expect
<maximed>it will look for PKG in current $PATH (_outside_ the guix shell), i.e., the old PKG you might have installed in ~/.guix-profile or such
<maximed>instead, I suggest ./pre-inst-env guix shell PKG --pure -- the-binary-name-thats-sometimes-just-PKG
<peterpolidoro>oh I see thanks
<maximed>The --pure is not strictly required here, but it avoids mixing the environment outside guix shell with the environment inside.
<peterpolidoro>very helpful thank you!
***madage is now known as ichichjunk
<atka>hi guix
<weidtn>Hello. When I try to install some clojure tool (deps-new for example) with "clj -Ttools install ..." it tells me "Error building classpath. Unknown tool: tools". But I installed clojure-tools. Is this some error on my side?
<atka>weidtn: clojure-tools-cli?
<weidtn>I think thats a tool for parsing cli arguments. But I tried it with it installed and it doesn't work
<atka>ok, not sure what it needs
<jab>Hey Guix!
<lilyp>weidtn: as a general rule, you need the interpreters in the same profile as the thing they're supposed to use
<lilyp>e.g. `guix shell clojure clojure-tools`
<weidtn>I am using my current profile in a freshly installed guix system
<weidtn>and even in this shell it does not work
<lilyp>I have little experience with clojure, so there might be more factors at play here – the classpath thing suggests some relation to Java that I can't figure out atm.
<atka>weidtn: did you try logging out then back in?
<lilyp>they said it didn't work inside guix shell, so that won't work either
<atka>on a fresh system my tools don't show up in guix home until a logout
<atka>oh ok
<weidtn>logging out and in does not help
<jab>I am really liking learning about srfi 1. fold, map, remove and the rest are awesome!
<lilyp>weidtn: I highly suspect you need a JRE in your profile as well
<lilyp>SRFI 1 is the best SRFI :)
<lilyp>SRFI 26 is the cutest, though
<jab>lilyp: the cutest eh?
<weidtn>JRE should be installed when I installed openjdk. "java --version" tells me OpenJDK Runtime Environment is used.
<lilyp>okay, I know the problem: neither Java nor Clojure actually set classpaths
<lilyp>you need to painstakingly provide those on the command line
***jackhill is now known as KM4MBG
***KM4MBG is now known as jackhill
<jab>weidtn: you are doing java development with guix!? You're braver than me. Best of luck!
<weidtn>Right now I'm realizing it was a mistake to make the shift to guix on my laptop...
<jab>weidtn: what problems are you bumping into ?
<flaminwalrus[m]>Virtualization may help ease the transition
<weidtn>I just want to have clojure and python running. No problems on python so far.. But I cant even install the tool to create a new clojure project?
<the_tubular>What is the purpose of emacs-next package ?
<the_tubular>Is it going to be updated, or will it stop ?
<lilyp>emacs-next points to the current development version of emacs, i.e. roughly (1+ (package-version emacs))
<lilyp>so it ought to have a fairly accurate emacs 28 tree atm
<tschilptschilp23>I'm having troubles to properly use the ~(mount-may-fail? #t)~ option in file-system part of my config.scm. It is a luks-encrypted drive, that I'd like to get mounted, if it's attached. This part works flawlessly. But my system won't boot, if this drive is /not/ attached. I thought that maybe the mentioned option would solve this problem, but it makes no difference, whether this is set or not. Any ideas on that?
<the_tubular>Sorry, I worded my question poorly, lilyp I meant to say will it be updated to 29 now that 28 is stable ?
<lilyp>Ahh, once Guix maintainers have indeed bumped Emacs to 28 it will be 29, yes.
<the_tubular>Nice, I'll base my emacs package off of emacs-next then :)
<morganw>Could I ask, is there not an emacs-lucid because it is easy to install it with different configure options, or is it because no-one submitted that package yet?
<morganw>(because if you run it as a server I don't think there is any other way to avoid some crashes except use a different X toolkit)
<lilyp>I think the latter, do we even have the lucid toolkit?
*the_tubular has no clue what Lucid is
<morganw>It is in the source tree, so you just specify --with-x-toolkit=lucid
<the_tubular>But what is it ?
<the_tubular>A different X server ?
<daviid>anold CL implementtion
<daviid>):, an emacs backend
<daviid>as well, and a research lab in belgium
<ss2>the_tubular: an old toolkit that is part of Emacs.
<morganw>"Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
<morganw>Using an Emacs configured with --with-x-toolkit=lucid does not have this problem."
<ss2>lilyp: I've got a Emacs mod with lucid sitting around, which builds just fine.
<tschilptschilp23> this would be the configuration, it's the lower part which causes problems, when not physically attached.
<daviid>morganw: indeed, i had that exact problem no solong ago, and someone recommended to uninstall emacs-gtk, install and use emacs-lucid instead
<daviid>but ithink in the end, itis a wayland bug, at least on debian, that was my understanding after trying to solve theproblem
<morganw>I don't think it is anything to do with wayland.
<ss2>can I ask here? I'd like to prepare a v2 patch series to submit after doing some modifications. I'm slightly confused now with how to deal with the commits (said modifications) that should be part of the first commits. Should I rebase these commits, or squash them?
<daviid>i had to switch to gnome usingan X11 backend, instead of wayland, otherwise, emacs-lucid would still crash
<ss2>Otherwise that patch series would needlessly be too long.
<daviid>morganw: fwiw, that is the only way got rid of the problem, emacs-lucid still crashed untill i switch the gmome backend
<jab>weidtn: I do not think that guix has bootstrapped closure....I think guix avoids packaging things if they cannot build it from source.
<daviid>but that is on debin testig, not guix, and clearly depends o the wylnd version, afai could tell - i'll try the wauland baackend agin when i see new version coming ...
<weidtn>I think I found the problem regarding the clojure-tools. On my other (non guix) computer I have a "~/.config/clojure/tools/tools.edn" file, which contains the data for the clojure-tools "tool". Is this something that was forgotten in the guix "clojure-tools" package?
<lilyp>ss2: unless specifically asked to split your patch into multiple ones, squash your new changes into the commit that prompted them
<lilyp>~/.config is not maintained by Guix
<ss2>okay, will do.
<lilyp>though if you want, you could add a home-clojure-service to Guix Home... not that it'd necessarily be a good idea to do so
<jab>I probably need to start using guix home...
<weidtn>yes, but clojure has multiple deps.edn locations. I think there is also one in /gnu/store. maybe the "tools" should be linked there?
<the_tubular>Anyone figured out how to manage emacs with guix home ?
<lilyp>the_tubular: not a guix home solution, but manage your packages with leaf
<lilyp>use :when [package]-autoloads to detect whether an optional package is in your emacs
<maximed>the_tubular: The simplest would be to add 'emacs' and 'emacs-foo', 'emacs-bar' ... to the list of packages in Guix Home
<maximed>I don't think there's anything to manage beyond installing the packages.
<lilyp>if you're used to doing that, then as a step two you could generate your init.el as a file service
<lilyp>config.el might also be something to consider
<maximed>You could even do these kind of things without Guix Home: guix shell --pure emacs emacs-magit -- emacs ~/source-code/guix
<lilyp>ahem, custom.el
<jab>the_tubular: you could define your own emacs package...
<the_tubular>I'm reading the github, looks very interesting. But it should be what guix-home does
<jab>like I did with jmacs...I've stopped using it though...
<jab>getting the link now...
<the_tubular>Yeah, I'll need to get better with guix-home too
<maximed>the_tubular: What are you looking into managing?
<the_tubular>maximed my init.el basically
<maximed>the_tubular: I don't have an init.el
<maximed>Is this for personal macros and procedures and customisations?
<the_tubular>How do you manage emacs
<jab>goes guix home have a git-close-service ?
<maximed>the_tubular: guix install emacs emacs-magit emacs-paredit
<jab>sorry git-clone-service
<the_tubular>And how do you use those packages ?
<maximed>To use the emacs-magit package, I open (C-x C-f) the git checkout and then do M-x magit.
<maximed>Likewise for emacs-paredit.
<lilyp>ahh, my bad, the :when part should actually use (featurep )
<the_tubular>I mean, how do you define your themes, your keybinds, your fonts ... ?
<maximed>jab: CUrrently, no.
<maximed>the_tubular: I don't.
<maximed>I just use the defaults.
<the_tubular>I don't like defaults :/
<maximed>Though I think I added a keybinding and a function in ~/.emacs
<the_tubular>This whitescreen is going to make me peel my eyes
<lilyp>the_tubular: as I pointed out, use leaf in your init.el
<the_tubular>Yes, I'm reading on it lilyp. But this seems to be the job of guix-home no ?
<the_tubular>I could also manage my init.el with git, but I wanted guix-home to take care of it
<lilyp>Not quite – you could of inline your init.el into guix-home, but it'd be no better than actually writing the file
<the_tubular>Mhh, I'm not sure I understand
<morganw>I only started using it, but I just committed the file and let guix-home symlink it with home-files-service-type
<lilyp>as in, there is no smart way of handling emacs-specific things in guix home yet
<vagrantc>if i do "guix weather package1 package2 package3" and guix weather reports 1 of 3 available ... is there a way to get to to be more verbose about which is available?
<maximed>vagrantc: maybe --display-missing?
<lilyp>though as noted home-files-service-type will make sure that you have the files you want managed by guix and not just lying around on your disk collecting dust
<vagrantc>maximed: i guess that shows the opposite of what i want, but can infer by process of elimination :)
<Kalq[m]>vagrantc: here's an example I use to have guix home manage my emacs files
<maximed>vagrantc: oh right
<maximed>I guess a complementary --display-present option could be added
<vagrantc>maximed: that said, i totally missed --display-missing, so, that was helpful :)
<vagrantc>how i missed it, maybe i can blame on my new glasses ...
<the_tubular>Kalq[m] This looks like a good solution
<the_tubular>Kalq[m], You think ther is going to be a better solution in the future ?
<skip_>Hello, I'm trying to compile and run a javafx program (like the one at on Guix system, but can't figure out how. I tried using the openjfx packages (it says javafx.controls and javafx.fxml are missing) and tried installing it manually (I think it can't find dependencies). How can I compile and run that program? (I'm not sure if this is more of a Guix or Java question, sorry if this is off-topic)
<jab>skip_: I am not super familiar, but my understanding was that java has a hard time on guix. Most Java programs are hard (no one knows how) to build them from source.
<jab>guix tries not to include software that we do not know how to build from source.
<atka>vagrantc: did you give a talk at debconf a few years ago?
<vagrantc>atka: yup
<Kalq[m]>the_tubular Don't know, somebody will probably write a proper emacs service for guix home eventually.
<the_tubular>This is where my mind is breaking
<atka>vagrantc: oh cool, my brain finally put two and two together after our short chat about SBCs the other day
<the_tubular>So a service written in scheme for emacs ...?
<the_tubular>Where you'll be able to configure emacs in scheme ?
<atka>vagrantc: do you still have the same concerns around security and users managing their own packages?
<jab>the_tubular: that makes me think of the project to run emacs on the scheme vm. I would prefer to write emacs in scheme code...
<vagrantc>atka: the biggest security concern i had was that there was no trust path in guix, which is now solved since guix verifies the signed commits by default
<atka>thanks :)
<Kalq[m]>the_tubular: If you want to write your emacs configuration in scheme, I think that's already possible with guile emacs. Never used it myself though. Pretty sure it hasn't been touched in like 7 years.
<Cassio>Hello everyone!
<Cassio>Is there a plugin-manager for neovim in Guix?
<weidtn>I think I found the error causing the error with clojure-tools. The line "("tools.edn" "lib/clojure/")" is missing in the arguments #guix:install-plan. But I don't know how to fix this, I never worked with a mailing-list.
<jab>Kalq[m]: do you know of anyway using guile-emacs?
<Kalq[m]>never used it but it's packaged in guix so you can give it a shot i guess
<morganw>the_tubular: if you look at rde that has elisp-configuration-service, but the setup looks quite involved.
<the_tubular>I don't even know what rde is, but will take a look!
<jab>the_tubular: it'll probably be a little slower than regular emacs. and buggy.
<the_tubular>Yeah, I don't plan on using scheme emacs, it doesn't look very active as of now
<Cassio>How can I manage neovim plugins declaratively?
<atka>Cassio: are they packaged in guix? if so a manifest perhaps?
<Cassio>atka, they are not.
<Cassio>Is there a pluggin manager for neovim in Guix?
<Cassio>I couldn't find one...
<atka>not sure as I don't use neovim
<vagrantc>anyone able to reschedule builds on seemed like a spurious failure ... and blocks building all the u-boot packages
***ichichjunk is now known as madage
<vagrantc>maximed: or maybe even/additionally a --display-all :)
***sneek_ is now known as sneek
<robin>iirc the guile-emacs is currently broken; i haven't had time to bisect the breakage with time-machine etc. (it definitely worked at one point)
<robin>there are also quite a few elisp patches waiting to land in guile that were originally missing full ChangeLog entries
<robin>rebasing the emacs patch series is the really fun part, though ;)
***madage is now known as pussyriot