From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacsclient in elisp Date: Sat, 22 May 2021 13:29:35 +0300 Message-ID: <83bl93kqnk.fsf@gnu.org> References: <00ce8ae3-bb21-c58f-cd32-c196f146842b@daniel-mendler.de> <6fed43bb-d880-bcd5-6f6f-004b6182e539@daniel-mendler.de> <83pmxlo2z0.fsf@gnu.org> <922437d2-74ca-a7aa-cd1d-060f31d383e6@daniel-mendler.de> <83o8d5o0od.fsf@gnu.org> <186aa7ae-605d-3959-b923-ee5817c939f0@daniel-mendler.de> <83mtspnseg.fsf@gnu.org> <837djsobhw.fsf@gnu.org> <83cztkm8hu.fsf@gnu.org> <831ra0lyrb.fsf@gnu.org> <83y2c7l2l9.fsf@gnu.org> <7fba8daf-a3f0-88a0-dcd4-4b9bae033dbb@daniel-mendler.de> <83cztjkr4m.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22302"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: mail@daniel-mendler.de, monnier@iro.umontreal.ca Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 22 12:30:33 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 1lkOts-0005ai-Da for ged-emacs-devel@m.gmane-mx.org; Sat, 22 May 2021 12:30:32 +0200 Original-Received: from localhost ([::1]:46670 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lkOtr-00071T-DB for ged-emacs-devel@m.gmane-mx.org; Sat, 22 May 2021 06:30:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkOt1-00066v-El for emacs-devel@gnu.org; Sat, 22 May 2021 06:29:40 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56842) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lkOt0-0006eU-GQ; Sat, 22 May 2021 06:29:38 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3193 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkOsx-0005CJ-TO; Sat, 22 May 2021 06:29:38 -0400 In-Reply-To: <83cztjkr4m.fsf@gnu.org> (message from Eli Zaretskii on Sat, 22 May 2021 13:19:21 +0300) 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:269606 Archived-At: > Date: Sat, 22 May 2021 13:19:21 +0300 > From: Eli Zaretskii > Cc: monnier@iro.umontreal.ca, bugs@gnu.support, emacs-devel@gnu.org > > > For my use case this would not be harsh. A running Emacs will explicitly > > opt-in to use the special make-stdio-process to read from stdin. This > > special process will only be used by external worker Emacsen controlled > > from the main Emacs. In that scenario the data flowing over stdin-stdout > > is tightly controlled (IPC protocol). There hopefully won't be spurious > > read-from-minibuffer calls. > > The last assumption is questionable I mean in general, not for the single use case you described.