From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: not good proposal: "C-z " reserved for users Date: Sat, 20 Feb 2021 17:39:48 +0300 Message-ID: References: <877dna6kag.fsf@robertthorpeconsulting.com> <87ft1xurht.fsf@zoho.eu> <8735xvsm3q.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27182"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 20 15:41:08 2021 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lDTRT-0006zR-It for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 20 Feb 2021 15:41:07 +0100 Original-Received: from localhost ([::1]:39384 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lDTRS-000464-KF for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 20 Feb 2021 09:41:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lDTR6-00045W-IJ for help-gnu-emacs@gnu.org; Sat, 20 Feb 2021 09:40:44 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:46383) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lDTR3-0008PC-1c for help-gnu-emacs@gnu.org; Sat, 20 Feb 2021 09:40:44 -0500 Original-Received: from localhost ([::ffff:41.210.155.197]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E079.0000000060311F65.000049AB; Sat, 20 Feb 2021 07:40:36 -0700 Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <8735xvsm3q.fsf@zoho.eu> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:128138 Archived-At: * Emanuel Berg via Users list for the GNU Emacs text editor [2021-02-17 01:10]: > Jean Louis wrote: > > > It does not relate to suspending a job, as terminal > > multiplexers do not suspend or stop the job temporarily, > > they run the processes. Inside of them one can use job > > control [...] > > You can, but often you don't have to, because there is no need > to suspend and start processes back and forth just to get > access to the shell. Instead you just open a new tmux pane and > do whatever you intend to do, there. To get access to shell is maybe purpose for some people, I do not know. I will use that to suspend one job while doing some other job. As I said, I do not myself really consider one editor instance as something as "running job" it is more like "pending or ready" process. My side I have things that process over one day, two days. Sometimes it is sending emails. If I leave it running it is continous process, sends emails and reports with a single dot "." -- then screen becomes full of dots........... but then sometimes Internet stops working as I use mobile Internet. That is where emails go into the queue, but even if they go into Courier mail queue, the queue may be itself having some number of expiry days and all emails sent become rejected by my own physical computer serving my in my premise. Of course people use remote servers for that, but because I do not consider them reliable, rather unsafe, I keep databases safe on my off-line computers and just relay to remote servers. Jobs of that kind that run all the time need suspension, not switch to other screen. By switching to other shell, screen, tmux, one does not suspend the job, and does not suspend the activity. By killing it with proper signal the activity may be stopped. True. But that can be done in emergency and only under conditions when person does have access to different resource and especially enough time. When something goes wrong there is no time, you need Control-Z. Who did not learn using job control, does not need it. Who did learn it, uses it. I am using it frequently. Sometimes it is the only way out of some program. Public shell servers can be useful for processing of data, why not, I will use some processing on remote servers that are not mine as if there is no secret information. In other words, there are numerous situations where one to stop/suspend process, and be able to continue the process, this is totally orthogonal to switching between processes or supervising what running processes do as that is what screen/tmux do.