From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Mendler Newsgroups: gmane.emacs.devel Subject: Re: emacsclient in elisp Date: Thu, 20 May 2021 19:49:38 +0200 Message-ID: <186aa7ae-605d-3959-b923-ee5817c939f0@daniel-mendler.de> 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> 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="40022"; mail-complaints-to="usenet@ciao.gmane.io" Cc: bugs@gnu.support, emacs-devel@gnu.org To: Stefan Monnier , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 20 19:54:13 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 1ljms8-000AB2-Ke for ged-emacs-devel@m.gmane-mx.org; Thu, 20 May 2021 19:54:12 +0200 Original-Received: from localhost ([::1]:41258 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ljms7-0004kq-L9 for ged-emacs-devel@m.gmane-mx.org; Thu, 20 May 2021 13:54:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55076) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ljmns-0005Y9-9Y for emacs-devel@gnu.org; Thu, 20 May 2021 13:49:48 -0400 Original-Received: from server.qxqx.de ([2a01:4f8:121:346::180]:57039 helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ljmnm-0004OA-Dc; Thu, 20 May 2021 13:49:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=qxqx.de; s=mail1392553390; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=6oXZh7N8Vs8V6SZLrR2fxufUOilvqqU+ccFejPmFMtw=; b=tH8qy9prk1c1487YBHf5T7IqF3 Fc4Ob3ZtDbEJC0OX7JO3bRy+EyXaYLOFQL65pLAjTCgaScOYeOJwFLZgrIRNPkHduqzBsEnZn050H OhSPnEBTFLzurRiP148Z/chJtnhV49bfKQT+Ei6eXT9kQX65yCX7Lu+/t00Ce/yVp4to=; In-Reply-To: Content-Language: en-US Received-SPF: pass client-ip=2a01:4f8:121:346::180; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:269506 Archived-At: On 5/20/21 6:40 PM, Stefan Monnier wrote: >>> Yes, synchronously reading from stdin is supported. But it is not >>> possible to do this asynchronously, or is it? This was specifically the >>> functionality I have been looking for. >> What do you mean by that? how can Emacs read input _asynchronously_ >> when reading is inherently a synchronous operation? > > I think the problem is that in batch mode, `read-from-minibuffer` is not > only synchronous (which is fine) but it doesn't perform any async > processing, like running process filters and timers while waiting for > the input from stdin. Exactly. Reading from stdin hangs up the whole process and I would like it to handle the other process filters in the background while Emacs is waiting on stdin for input. Reading from stdin should not get a special treatment in terms of scheduling. There should be a possibility to read from stdin using a similar API as `make-network-process` with a filter and sentinel for EOF. Daniel