verbose backtraces when “invoke” fails
Hi Guix, I’d like us to catch the errors raised by “invoke”, so that the output of a failing build looks nicer again. Before we used “invoke” build phases evaluating to #f would cause the build system to abort and print a nice message. Now users get an ugly backtrace that is much too verbose for what it’s trying to say, namely that a command invocation failed. There is no value in the backtrace itself (users don’t care where “invoke” is defined, for example); we only want the error message. Shall we fix this on core-updates? -- Ricardo
Re: Merging ‘wip-newt-installer’ in master?
Hey! > I've had a quick go and I must say I like it a lot! Great job, Mathieu! Thanks Pierre :) > - Add and extra warning before partitioning! I did it wrong at first but I > did > not expect the installer to proceed straight away, I thought I would have a > second chance at reviewing the changes before proceeding. > > - More generally, I like the idea of a two-stage process: first collect the > details from the user (without actually performing any change), then show a > summary of the changes, ask for confirmation and only then apply all the > changes in one go. I added both of your suggestions to the "Installer" section of the TODO file! Thanks for your feedback, Mathieu
Re: Merging ‘wip-newt-installer’ in master?
> Thanks! But what about the first one with the timeout and incompatible > displays? ;) Well no clue for where this display issue comes from, it might be related to kmscon/framebuffer support on your GPU. Your fallback timeout message seems like a good idea to me, even though I'm not sure how to implement it yet. I added an entry in the TODO/Installer section about it. Mathieu
Re: verbose backtraces when “invoke” fails
Am 21.01.19 um 09:21 schrieb Ricardo Wurmus: > I’d like us to catch the errors raised by “invoke”, so that the output > of a failing build looks nicer again. +1 -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
Unofficial Neovim channel
Hello Guix developers, I have set up an unofficial Guix channel for Neovim (and possibly for related projects in the future): https://gitlab.com/HiPhish/neovim-guix-channel/ The plan is to use this channel first, and then submit patches to Guix when everything is deemed correct and reliable. I also wrote a blog post[1] on the topic, although it's primarily addressed at people familiar with Neovim and unfamiliar with Guix. I would very much appreciate if someone could go over the code in my channel and see if everything is in order. HiPhish - [1] http://hiphish.github.io/blog/2019/01/21/neovim-guix-channel/
Re: Install doc + templates overhaul
Hello Pierre, Pierre Neidhardt skribis: > I've just re-installed Guix from a 0.16 image. My first time in a year, > and I've had the opportunity to have a fresh look at the installation > manual. I've taken note of a few confusing points that gave me a hard > time installing Guix (even the 2nd time :p) so here they are. I'll send > a patch to address them if you people agree. Did you try installing with the new installer? Hopefully most of this documentation becomes secondary when one uses the installer. :-) Anyway, the changes you propose overall LGTM. Thanks, Ludo’.
“Creating a reproducible workflow with CWL”
Hello Guix! If you’re into bioinfo or reproducible scientific workflows, you may enjoy this new article by Pjotr: https://guix-hpc.bordeaux.inria.fr/blog/2019/01/creating-a-reproducible-workflow-with-cwl/ Happy reading! Ludo’.
Re: verbose backtraces when “invoke” fails
Hi, Ricardo Wurmus skribis: > I’d like us to catch the errors raised by “invoke”, so that the output > of a failing build looks nicer again. Yes, please! That can be done in ‘gnu-build’ in (guix build gnu-build-system). Ludo’.
Re: Unofficial Neovim channel
Hello, HiPhish skribis: > I have set up an unofficial Guix channel for Neovim (and possibly for related > projects in the future): > > https://gitlab.com/HiPhish/neovim-guix-channel/ > > The plan is to use this channel first, and then submit patches to Guix when > everything is deemed correct and reliable. I also wrote a blog post[1] on the > topic, although it's primarily addressed at people familiar with Neovim and > unfamiliar with Guix. I would very much appreciate if someone could go over > the code in my channel and see if everything is in order. Nice, thanks for sharing! And yes, do feel free to contribute the package(s) to Guix itself when you deem appropriate! :-) Ludo’.
Re: Plan for fish shell in Guix.
Hello everyone, Thank you for your patience. I investigated the problem and chose to parse /etc/profile from fish rather than generate separate configuration files for fish. I think this will make the Guix project easier to maintain in the future. I looked NixOS's solution. They choose this approach too, but their patch is more complex. I implemented my patch in a minimalistic manner. The patch has been sent to guix-patc...@gnu.org: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34153 I set fish as my login shell and every thing is working well. Please try the patch and report bugs if you are interested. Thanks. -- Meiyo Peng https://www.pengmeiyu.com/
Re: Plan for fish shell in Guix.
Hi, I’m trying it now. Everything seems to work pretty well! Thanks so much! This has been one major issue for me for a while! - John > On Jan 21, 2019, at 12:32 AM, Meiyo Peng wrote: > > Hello everyone, > > Thank you for your patience. > > I investigated the problem and chose to parse /etc/profile from fish > rather than generate separate configuration files for fish. I think > this will make the Guix project easier to maintain in the future. > > I looked NixOS's solution. They choose this approach too, but their > patch is more complex. I implemented my patch in a minimalistic manner. > > The patch has been sent to guix-patc...@gnu.org: > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34153 > > I set fish as my login shell and every thing is working well. Please > try the patch and report bugs if you are interested. > > Thanks. > > > -- > Meiyo Peng > https://www.pengmeiyu.com/ >
Re: Install doc + templates overhaul
I've pushed the doc changes onto the install-doc-overhaul branch. Feel free to merge if you are happy with it. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
Re: Plan for fish shell in Guix.
Hello, I just have one issue with the patch so far: I can’t seem to unset an abbreviation. An old configuration file seems to be “sticking” around for lack of better term. Otherwise, good stuff! John > On Jan 21, 2019, at 12:32 AM, Meiyo Peng wrote: > > Hello everyone, > > Thank you for your patience. > > I investigated the problem and chose to parse /etc/profile from fish > rather than generate separate configuration files for fish. I think > this will make the Guix project easier to maintain in the future. > > I looked NixOS's solution. They choose this approach too, but their > patch is more complex. I implemented my patch in a minimalistic manner. > > The patch has been sent to guix-patc...@gnu.org: > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34153 > > I set fish as my login shell and every thing is working well. Please > try the patch and report bugs if you are interested. > > Thanks. > > > -- > Meiyo Peng > https://www.pengmeiyu.com/ >
Re: Plan for fish shell in Guix.
Hi John, John Soo writes: > I’m trying it now. Everything seems to work pretty well! Thanks so > much! This has been one major issue for me for a while! Thank you for your feedback. I'm glad you like it. -- Meiyo Peng https://www.pengmeiyu.com/
Re: Plan for fish shell in Guix.
Hi John, John Soo writes: > I just have one issue with the patch so far: I can’t seem to unset an > abbreviation. An old configuration file seems to be “sticking” around > for lack of better term. Otherwise, good stuff! This is most likely caused by the transition from fish 2.7 to fish 3.0. Fish 3.0 automatically migrates your abbreviations to a new storage format. Please have a look at the man page of `abbr`. You should now manage you abbreviations with: #+begin_SRC sh abbr --show abbr --add ec emacsclient abbr --erase ec #+end_SRC -- Meiyo Peng https://www.pengmeiyu.com/
Re: Plan for fish shell in Guix.
Ah! Makes sense! I haven’t had a chance to use 3.0 yet! I’ll try that and see. > On Jan 21, 2019, at 5:24 PM, Meiyo Peng wrote: > > Hi John, > > John Soo writes: > >> I just have one issue with the patch so far: I can’t seem to unset an >> abbreviation. An old configuration file seems to be “sticking” around >> for lack of better term. Otherwise, good stuff! > > This is most likely caused by the transition from fish 2.7 to fish 3.0. > Fish 3.0 automatically migrates your abbreviations to a new storage > format. Please have a look at the man page of `abbr`. You should now > manage you abbreviations with: > > #+begin_SRC sh > abbr --show > abbr --add ec emacsclient > abbr --erase ec > #+end_SRC > > -- > Meiyo Peng > https://www.pengmeiyu.com/
