From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brenton Horne 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 Message-ID: References: <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a1140298cd096bf05505d5789" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51272) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDxSZ-0004I7-1Z for bug-guix@gnu.org; Thu, 25 May 2017 14:26:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDxSU-00030U-2l for bug-guix@gnu.org; Thu, 25 May 2017 14:26:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:35380) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dDxST-00030M-Rq for bug-guix@gnu.org; Thu, 25 May 2017 14:26:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dDxST-00005a-Lr for bug-guix@gnu.org; Thu, 25 May 2017 14:26:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 27067@debbugs.gnu.org --001a1140298cd096bf05505d5789 Content-Type: text/plain; charset="UTF-8" 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 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 --001a1140298cd096bf05505d5789 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm afraid I have no knowledge of Guile or Scheme. Loo= king 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.=C2=A0

<= div class=3D"gmail_quote">On 26 May 2017 at 04:10, Arun Isaac <ar= unisaac@systemreboot.net> wrote:

Brenton Horne writes:

> Thanks. I did ask in the #guix IRC channel first and no one provided t= his
> solution (not using this as some criticism, I realize the IRC channel = is
> people volunteering their time to help others, just mentioning) and on= e
> person agreed with my suggestion of reporting this as a feature reques= t.
> 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, aft= er
> 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 a= nd 3
> CPU cores (3.3 GHz i7 cores), so it might save users interested in fil= ing
> bug reports a lot of time (on re-running the problem command with `| t= ee
> output.log` after it) if the output was logged automatically. Saving u= sers
> 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 e= ntire
> 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.



--
Th= anks for your time,
Brenton
--001a1140298cd096bf05505d5789--