From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: "kill -STOP" as noticed in ksh93u+ gitlab
Date: Tue, 27 Feb 2024 18:04:34 -0800 [thread overview]
Message-ID: <CAH+w=7Z+L_HoC4AkTzxZSn9WtwK6b9MUZgpOds-cMh+iU2J7oA@mail.gmail.com> (raw)
In-Reply-To: <20240227070502.ek5ocpwxm6cpp5gz@chazelas.org>
On Mon, Feb 26, 2024 at 11:05 PM Stephane Chazelas
<stephane@chazelas.org> wrote:
>
> So that's about extending an old (obsolete) behaviour to
> graphical terminal emulators and only for macos which is the
> only system that I've heard of where terminal emulators create a
> login shell.
It may be that MacOS is the only one where the default is that way,
but I nearly always configure my terminal windows to create login
shells on every X11-ish desktop I use. Further if the terminal is
running a remote shell that'll also be a login, and if you suspend a
remote shell it's rather more difficult to resume it (unless you're
using "screen" or remote tmux or something in which case you
disconnect rather than suspend the process).
> But, that seems wrong. It made sense in the 80s where if you
> froze your login session, you would have no chance to recover
> from it. But in the graphical emulator case, you could envisage
> one wanting to suspend their shell (login or not) and resume it
> later with a SIGCONT from another shell (in a different terminal
> emulator or different ssh session...).
Changing the "kill" command doesn't (in zsh at least) affect the
"suspend" command.
schaefer[592] Src/zsh -f -o login
% suspend
suspend: can't suspend login shell
% suspend -f
zsh: suspended Src/zsh -f -o login
schaefer[593] fg
[1] + continued Src/zsh -f -o login
% kill -STOP $$
kill: kill 605210 failed: operation not permitted
%
I think this is more to prevent accidental stoppage?
next prev parent reply other threads:[~2024-02-28 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 21:26 Bart Schaefer
2024-02-27 7:05 ` Stephane Chazelas
2024-02-28 2:04 ` Bart Schaefer [this message]
2024-02-28 5:39 ` Stephane Chazelas
2024-02-28 5:42 ` Stephane Chazelas
2024-02-28 7:52 ` Bart Schaefer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7Z+L_HoC4AkTzxZSn9WtwK6b9MUZgpOds-cMh+iU2J7oA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).