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.devel Subject: Re: Async processes to be persistent even after exiting Emacs Date: Fri, 23 Apr 2021 00:03:31 +0300 Message-ID: References: <20210422200141.2hyv2crygvhac5zd@E15-2016.optimum.net> 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="14551"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.6 (2021-03-06) Cc: Emacs-Devel List To: Boruch Baum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 22 23:09:45 2021 Return-path: Envelope-to: ged-emacs-devel@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 1lZga0-0003dj-3e for ged-emacs-devel@m.gmane-mx.org; Thu, 22 Apr 2021 23:09:44 +0200 Original-Received: from localhost ([::1]:60104 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lZgZz-00039C-6g for ged-emacs-devel@m.gmane-mx.org; Thu, 22 Apr 2021 17:09:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48644) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZgZK-0002hv-Ee for emacs-devel@gnu.org; Thu, 22 Apr 2021 17:09:02 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:46373) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZgZH-0007kT-8a for emacs-devel@gnu.org; Thu, 22 Apr 2021 17:09:01 -0400 Original-Received: from localhost ([::ffff:41.202.241.57]) (AUTH: PLAIN securesender, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000002BECD.000000006081E5E4.00001B9B; Thu, 22 Apr 2021 14:08:48 -0700 Mail-Followup-To: Boruch Baum , Emacs-Devel List Content-Disposition: inline In-Reply-To: <20210422200141.2hyv2crygvhac5zd@E15-2016.optimum.net> 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: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:268291 Archived-At: * Boruch Baum [2021-04-22 23:16]: > The standard built-in method that Emacs uses to spawn an asynchronous > processes doesn't enable those processes to survive the killing of their > process buffers, and certainly not to survive exiting emacs. That is useful. I am launching software through Emacs and often those programs should persist. It would be good to have some prefix or similar command to make it persist. As a side note, not quite relate, but could be, some software I cannot launch with M-! but it works with M-& -- example is rox and retext. It is very unclear why is this happening, do you maybe know a reason? For example this below does not work with `retext' editor neither M-! retext works, but M-& retext does work. (defun rcd-edit-with-external-editor () (interactive) (let* ((buffer (current-buffer)) (text (buffer-substring-no-properties (point-min) (point-max))) (mode major-mode) (file (concat (or (getenv "TMPDIR") "/tmp/") "temp-file"))) (string-to-file-force text file) (shell-command (format "retext %s" file)) (erase-buffer) (insert (file-to-string file)) (goto-char 0))) If I use other GUI editor it does work. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns Sign an open letter in support of Richard M. Stallman https://stallmansupport.org/ https://rms-support-letter.github.io/