unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brenton Horne <brentonhorne77@gmail.com>
To: 27067@debbugs.gnu.org
Subject: bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged
Date: Fri, 26 May 2017 04:25:18 +1000	[thread overview]
Message-ID: <CANb+58+xQZRQE1Sp1YFedj3awZNBHa=mnV5S=nscfGHrg-Ju+A@mail.gmail.com> (raw)
In-Reply-To: <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

I'm afraid I have no knowledge of Guile or Scheme. Looking at the Guile
manual seems to indicate to me it's a language quite unlike most languages
I've coded in. The only exception is that it does look a little like Emacs
Lisp.

On 26 May 2017 at 04:10, Arun Isaac <arunisaac@systemreboot.net> wrote:

>
> Brenton Horne writes:
>
> > Thanks. I did ask in the #guix IRC channel first and no one provided this
> > solution (not using this as some criticism, I realize the IRC channel is
> > people volunteering their time to help others, just mentioning) and one
> > person agreed with my suggestion of reporting this as a feature request.
> > Still this feature would be useful, but your idea makes it less urgent.
> > Automatic logging still sounds like a good idea as Guix is quite slow for
> > some operations at the moment (not dissing the developers of Guix, after
> > all at this early stage of development issues like this are to be
> > expected), for me at least running GuixSD in a QEMU VM with 8 GB RAM and
> 3
> > CPU cores (3.3 GHz i7 cores), so it might save users interested in filing
> > bug reports a lot of time (on re-running the problem command with `| tee
> > output.log` after it) if the output was logged automatically. Saving
> users
> > time will probably mean users will be far more motivated and able to
> > provide bug reports on issues they experience, which is good for the
> entire
> > Guix community as bugs would get reported and resolved faster.
>
> You could work on this issue, and submit a patch. I'm sure that would be
> welcome.
>
> Regards,
> Arun Isaac.
>



-- 
Thanks for your time,
Brenton

[-- Attachment #2: Type: text/html, Size: 2243 bytes --]

  parent reply	other threads:[~2017-05-25 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  7:54 bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Brenton Horne
2017-05-25 16:41 ` Arun Isaac
2017-05-25 17:05 ` bug#27067: Reply to Arun Isaac's reply Brenton Horne
     [not found] ` <a7836b86.AEAAKjHnUF4AAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJwlc@mailjet.com>
     [not found]   ` <CANb+58K6AENjXCrPF=gE=ou+AKE=G+R9+qscPjj3vQjSE-eijQ@mail.gmail.com>
     [not found]     ` <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com>
2017-05-25 18:25       ` Brenton Horne [this message]
2017-05-25 20:10 ` bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Ricardo Wurmus
2017-05-25 20:33   ` Brenton Horne
2017-05-25 21:30     ` Ricardo Wurmus
2017-05-30 20:14 ` Ludovic Courtès
2018-12-17  9:30 ` swedebugia
2018-12-18 11:21   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANb+58+xQZRQE1Sp1YFedj3awZNBHa=mnV5S=nscfGHrg-Ju+A@mail.gmail.com' \
    --to=brentonhorne77@gmail.com \
    --cc=27067@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).