Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.unix.shell
Subject: Re: LOL, managed to suspend "fg" command somehow.
Date: Mon, 07 Apr 2025 20:19:11 -0700
Organization: None to speak of
Lines: 16
Message-ID: <87wmbvxrv4.fsf@nosuchdomain.example.com>
References: <20250407172401.859@kylheku.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Tue, 08 Apr 2025 05:19:14 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="eb9757dfc1fa39d24f8b16770c2d3244";
	logging-data="1285561"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX188MS0xXLEGeXhWnDdQ5/nz"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:JNlh/ZUH/NCDqFB41Rq5OLxC7gg=
	sha1:8O6M4aVXSjn2IROU/ILzrRP8GsY=
Bytes: 1443

Kaz Kylheku <643-408-1753@kylheku.com> writes:
> Says it all:
>
> $ jobs
> [39]-  Stopped                 fg  (wd: ~/jp-hash)
>
> :)

I've seen a bash bug where the names reported by the jobs command are
incorrect.  I don't recall the details, but this looks familiar.  Try
`jobs -l` to see the process id, then `ps` (if and only if you're
sufficiently curious).

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */