From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: User interaction from multiple threads Date: Sun, 26 Aug 2018 17:43:07 +0300 Message-ID: <83va7x5guc.fsf@gnu.org> 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> <83bm9q6x7v.fsf@gnu.org> <874lfi863s.fsf@himinbjorg.adminart.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1535295344 8020 195.159.176.226 (26 Aug 2018 14:55:44 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 26 Aug 2018 14:55:44 +0000 (UTC) Cc: psainty@orcon.net.nz, gazally@runbox.com, rms@gnu.org, emacs-devel-bounces+psainty=orcon.net.nz@gnu.org, emacs-devel@gnu.org To: hw Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 26 16:55:39 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 1ftwS2-0001zq-A8 for ged-emacs-devel@m.gmane.org; Sun, 26 Aug 2018 16:55:39 +0200 Original-Received: from localhost ([::1]:49367 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ftwU8-0006va-M3 for ged-emacs-devel@m.gmane.org; Sun, 26 Aug 2018 10:57:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41941) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ftwTH-0006Ma-N3 for emacs-devel@gnu.org; Sun, 26 Aug 2018 10:56:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ftwGI-000735-4N for emacs-devel@gnu.org; Sun, 26 Aug 2018 10:43:30 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41858) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ftwGB-00070N-C9; Sun, 26 Aug 2018 10:43:23 -0400 Original-Received: from [176.228.60.248] (port=3257 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ftwG4-0000dG-RK; Sun, 26 Aug 2018 10:43:17 -0400 In-reply-to: <874lfi863s.fsf@himinbjorg.adminart.net> (message from hw on Sun, 26 Aug 2018 14:52:41 +0200) 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:228931 Archived-At: > From: hw > Cc: rms@gnu.org, psainty@orcon.net.nz, emacs-devel@gnu.org, emacs-devel-bounces+psainty=orcon.net.nz@gnu.org, gazally@runbox.com > Date: Sun, 26 Aug 2018 14:52:41 +0200 > > > I don't see how this would solve the problem, since thread IDs will > > always be quite short. > > I don´t understand this. I thought requests for input would be queued > in such a way that the users can look at the queue when ever they see > fit, and the information in the queue along with the prompts would make > it obvious to the users what each request is about. > > Wouldn't that be much better than having requests for input and the > threads that created them fight over the mini-buffer and interrupt the > user once they can hijack the mini-buffer? You need to catch up with the discussion ;-) We all but agreed that threads should not "fight" one another. Still, when Emacs decides that a certain thread is granted access to the minibuffer and can interact with the user, how will the user know which of the N threads asks them the question, and for what purpose? The correct answer could well depend on that. As a trivial example, consider 2 threads, one copying files, the other removing files. How do you know whether to confirm or not when the prompt says just "FOO (y or n)?"