From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: User interaction from multiple threads Date: Sat, 25 Aug 2018 15:11:10 -0400 Message-ID: References: <838t59j821.fsf@gnu.org> <87lg92q7ih.fsf@runbox.com> <83a7phdl7r.fsf@gnu.org> <61492e7f622303d02405bedbe65fabae@webmail.orcon.net.nz> <83pnybdaer.fsf@gnu.org> <837ekicw7i.fsf@gnu.org> <877ekiierh.fsf@himinbjorg.adminart.net> <834lflb2fj.fsf@gnu.org> <83h8jk9l41.fsf@gnu.org> <8336v2994c.fsf@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1535224311 5037 195.159.176.226 (25 Aug 2018 19:11:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 25 Aug 2018 19:11:51 +0000 (UTC) Cc: psainty@orcon.net.nz, hw@adminart.net, emacs-devel@gnu.org, emacs-devel-bounces+psainty=orcon.net.nz@gnu.org, gazally@runbox.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 25 21:11:46 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ftdyL-00018P-6J for ged-emacs-devel@m.gmane.org; Sat, 25 Aug 2018 21:11:45 +0200 Original-Received: from localhost ([::1]:46815 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fte0R-0000H8-F1 for ged-emacs-devel@m.gmane.org; Sat, 25 Aug 2018 15:13:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ftdy7-00070t-WB for emacs-devel@gnu.org; Sat, 25 Aug 2018 15:11:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ftdy6-0004Ia-JV for emacs-devel@gnu.org; Sat, 25 Aug 2018 15:11:31 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52182) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ftdxn-0003bo-75; Sat, 25 Aug 2018 15:11:11 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1ftdxm-000263-Rs; Sat, 25 Aug 2018 15:11:10 -0400 In-Reply-To: <8336v2994c.fsf@gnu.org> (message from Eli Zaretskii on Sat, 25 Aug 2018 10:51:47 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228908 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > My conclusion from the discussion is that when a thread asks for > input, it might be too late, because the prompt was already issued. In Emacs, prompts are usually output by a function whose main purpose is to ask for input. Is this no longer true? So in practice it is easy to tell what is a prompt that asks for input. > > until the thread exits? > Not until it exits, until it no longer needs to interact with the > user, for the current transaction (whatever that means). How does a thread say that it no longer needs to interact...? > I'm saying that fixing the prompt itself is a better alternative, > because we will always give the prompt more screen estate than to the > thread ID. Emacs could add the thread ID at the start of a prompt when there are multiple threads that could be asking for input, such that there is a possibility of confusion. That could avoid lengthening the prompts in the usual cases. -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)