Marshall Conover wrote in <CAK0pxsFBAd6BdpZ9d3KTuPQS_JwUdhKtniSLXzFVUD3kQD5b5w(a)mail.gmail.com>: |In my experience, for the sake of mental organization and not sending the |wrong command to the wrong place, there's a case to be made for |"namespacing" all activity around a certain task/environment in a singular |shell, which makes job handling with fore- and backgrounding relevant. For |example, I'll be iterating on a script targeting a new deployment |environment that requires certain env vars and a history of related |commands, then running it to see if it works, and reflexively I'm more |likely to open & edit the script, then ctrl+z the editor and run the script |than to open the editor in a separate window in my experience. That said, I |certainly have sometimes thought "you know, you could just edit the script |in another window." | |I did only just learn about ":stop" with this message, though. For me, the |surprising thing is implementing in vim what users can do by hitting ctrl+z |(and which I do daily in vim with ctrl+z). Even before getting to the |window system, the shell's already got this covered by giving you the |ability to background the application: why add lines of code to your |application to do it again? But perhaps there is a scripting utility to |having it within vim itself. You may have the desire to strip termios/ISIG at times due to whatever reasons (raw input mode), but still want the functionality to happen upon a certain (configurable) keypress. If you then have the function, why not also offer it to users. (Having said that, the MUA i maintain, for example, has ‘\cZ’ raise(3)∞ ‘SIGTSTP’ (mle-raise-tstp). which then does exactly that, after restoring normal termios; but that is just how it came.) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) | |During summer's humble, here's David Leonard's grumble | |The black bear, The black bear, |blithely holds his own holds himself at leisure |beating it, up and down tossing over his ups and downs with pleasure | |Farewell, dear collar bear

Clem Cole [2025-07-19 16:46:18]: I still like to use ^Z to suspend a running program, even when I use X11. That's really the reason I haven't changed my login shell to rc, because it lacks job control. -- Hilsen Harald

Since it would appear that that is totally unnecessary in a window system, as Doug pointed out, one has to ask why?

Noel Hunt wrote in &lt;CAGfO01zaZq6r=SGQZzHhLAZSbim7hUs7vCJPa-Y4xDqBro23LA(a)mail.gmail.com&gt;: |> I still like to use ^Z to suspend a running program, even when I use |> X11. | |Since it would appear that that is totally unnecessary in a |window system, as Doug pointed out, one has to ask why? And another question would be why i have a need to add pkill -CONT tmux to my dmenu.sh, aka command PKILL_TMUX "pkill -CONT tmux" to my (currently unused) ~/.cwmrc. Ie, why use that ^Z TSTP mess when there are so many race conditions that the signal goes to the wrong program. (This is most often from within less(1)<-bash(1)<-tmux(1)<-st(1), then; and it is on Linux.) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) | |During summer's humble, here's David Leonard's grumble | |The black bear, The black bear, |blithely holds his own holds himself at leisure |beating it, up and down tossing over his ups and downs with pleasure | |Farewell, dear collar bear

[Somewhat off-topic for TUHS; please follow up at COFF] On Saturday, 19 July 2025 at 17:37:34 -0600, Warner Losh wrote: You have me curious. How many do you know? And what don't you like about them, when you clearly use Emacs? Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

On Saturday, 19 July 2025 at 19:27:40 -0600, Warner Losh wrote: You don't say which. I only know GNU Emacs. Looking at the FreeBSD Ports Collection, not even xemacs seems to have survived. Not in my experience (GNU Emacs 29.4 (build 1, amd64-portbld-freebsd13.3, GTK+ Version 3.24.43, cairo version 1.17.4). I have four displays on my server 0, and also 4 instances of Emacs: one on :0.1 and three on :0.2. You need to start them individually, of course, but that's what shells are for. Each Emacs can open windows on other displays, and that's useful if they're on other machines, but it's not the only way. Can it be that your negative experience was with another version that has since died? What you describe sounds like my pain with web browsers. Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

On Mon, Jul 21, 2025 at 02:03:38PM +1000, Greg 'groggy' Lehey wrote: Yeah, it doesn't work that way for me using GNU emacs on Debian either. Many decades ago I did force the behaviour that you describe; it involved setting EDITOR to emacsclient, and then running (server-start) in my ~/.emacs.el. This was a feature back when I was running emacs on BSD 4.3 with a Vaxstation II/RC with 2 MiB of memory (Digital had put epoxy into the backplane so you couldn't add more memory to their memory-starved inexpensive model), but now that I buy my own desktops with 64 GiB of memory, I really don't care that emacs is "eight megabytes and constantly swapping" (well, not swapping; I don't configure swap any more :-) and emacsclient is more annoying than it's worth. - Ted