GNU bug report logs - #33397
"guix environment" does not warn about stopped jobs

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33397 in the body.
You can then email your comments to 33397 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: swedebugia <swedebugia <at> riseup.net>
To: bug-guix <at> gnu.org
Subject: "guix environment" does not warn about stopped jobs
Date: Thu, 15 Nov 2018 13:13:49 +0100

Hi

I use emacs in a terminal to hack on packages.
I start an emacs, press C-z to pause it after trying something
in bash I then build the package from the source tree
press fg to return to emacs
and so forth.

Typing guix environment will enter a new environment where apparently my 
paused emacs is not available.

Is this a bug?
Probably not.

Should we make guix environment warn/refuse to create the env. if 
stopped jobs exist?

Yes, I think so.

What do you think?

-- 
Cheers
Swedebugia

Message #10 received at 33397-done <at> debbugs.gnu.org (full text, mbox):

From: Brett Gilio <brettg <at> gnu.org>
To: swedebugia <swedebugia <at> riseup.net>
Cc: 33397-done <at> debbugs.gnu.org
Subject: Re: bug#33397: "guix environment" does not warn about stopped jobs
Date: Mon, 23 Dec 2019 19:54:06 -0600

swedebugia <swedebugia <at> riseup.net> writes:

> Hi
>
> I use emacs in a terminal to hack on packages.
> I start an emacs, press C-z to pause it after trying something
> in bash I then build the package from the source tree
> press fg to return to emacs
> and so forth.
>
> Typing guix environment will enter a new environment where apparently
> my paused emacs is not available.
>
> Is this a bug?
> Probably not.
>
> Should we make guix environment warn/refuse to create the env. if
> stopped jobs exist?
>
> Yes, I think so.
>
> What do you think?

This is not a bug, as far as I can tell. Especially with the recent
proposed and adopted changes to how jobs function in `guix environment`
you might have better luck with this issue now.

I am closing this in the mean time, but feel free to open a /new/ bug
report documenting the expected and true behaviors if you wish.

-- 
Brett M. Gilio
GNU Guix, Contributor | GNU Project, Webmaster
[DFC0 C7F7 9EE6 0CA7 AE55 5E19 6722 43C4 A03F 0EEE]
<brettg <at> gnu.org> <brettg <at> posteo.net>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.