From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: emacsclient in elisp Date: Sat, 22 May 2021 10:31:47 -0400 Message-ID: References: <00ce8ae3-bb21-c58f-cd32-c196f146842b@daniel-mendler.de> <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> <83bl93kqnk.fsf@gnu.org> <53abac6a-88d6-e691-e8e5-eea602c0f295@daniel-mendler.de> <835yzbkl8c.fsf@gnu.org> <83tumukgiq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13457"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: mail@daniel-mendler.de, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 22 16:32:35 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 1lkSg6-0003LK-Uk for ged-emacs-devel@m.gmane-mx.org; Sat, 22 May 2021 16:32:34 +0200 Original-Received: from localhost ([::1]:41886 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lkSg5-000681-7M for ged-emacs-devel@m.gmane-mx.org; Sat, 22 May 2021 10:32:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39028) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkSfY-0005Sw-U0 for emacs-devel@gnu.org; Sat, 22 May 2021 10:32:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:27562) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lkSfW-0007TX-Mw; Sat, 22 May 2021 10:32:00 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 5392C4410FB; Sat, 22 May 2021 10:31:57 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id A2C5F440C08; Sat, 22 May 2021 10:31:48 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1621693908; bh=d6xB/uUN2dlMucbjnGV0yCmVaRaH9P4SH+kVtAqg3iY=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Dr73g6vXLUzT3TbmIO3EiE6qUdnlyZDowh3+wDwkNGYnq+ObRR+NoKq0JcEywGDkH vhdJc/EvsVIHhWC7kozvLx71uF87MaUyGuS++18FQ9BspgExMR6n/fkmGgPvfjT68/ EAPWtSRA2Q1qFbE+3K7qL9TQ2La86CQFehG9JThBVTj1RcPBwaZWMcXIM/59/a0MEe qXWSSLAR0nn7URekhSFOLhnJpYGjNki62jr2XFIbRKk36XySYt/pL91w6sBnYrrUgQ 5nbsOEL5F2qMHfJmxFiLSo7X67AMdxblEIzusbQHMaj9Aq1m4bGbr8R4Gs4Wp8W2J5 NlvHEljF0D4Ug== Original-Received: from alfajor (76-10-140-76.dsl.teksavvy.com [76.10.140.76]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 6DA37120376; Sat, 22 May 2021 10:31:48 -0400 (EDT) In-Reply-To: <83tumukgiq.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 May 2021 17:08:29 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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:269613 Archived-At: > So we will enter read-from-minibuffer, and read the stuff from stdin > till the first newline. How do we know what's there is for us, not > for the stdin-process? This is a question to ask the programmers who decided to use both at the same time: it'll be their responsibility to arrange for the calls to those functions to happen at the right time in the right order and for the communication protocol to be designed accordingly. I don't think there's much we can do on our side. > The scenario is that we have the process for reading from stdin, but > some function we called decides to ask the user. BTW, a plain (while ) setup we can have the same problem: if one of the functions called by decides unexpectedly to call `read-from-minibuffer`, it can wreak havoc in your communication protocol. Again, there's nothing we can do about it on our side: it's the responsibility of the programmers writing that code to make sure it doesn't happen. Stefan PS: Admittedly, using a process object will make things a bit worse, since, contrary to `read-from-minibuffer`, the programmer has no real control over the amount of data read by `accept-process-output` before it's passed to the process filter, which is why I said above that it's also a question of protocol-design to make sure that if there's data meant for `read-from-minibuffer` some mechanism in the protocol should make sure it won't be sent while Emacs is inside `accept-process-output`.