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: Introducing thread-safe Tramp Date: Sat, 28 Jul 2018 12:57:36 +0300 Message-ID: <83effnr8bz.fsf@gnu.org> References: <8736wa9c5s.fsf@gmx.de> <87wotkn6do.fsf@gmx.de> <874lgn8x6l.fsf@gmx.de> <87wotgpj8s.fsf@gmx.de> <87o9espiqf.fsf@gmx.de> <83va90qt1x.fsf@gnu.org> <87pnz7iv2y.fsf@gmx.de> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1532771755 15427 195.159.176.226 (28 Jul 2018 09:55:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 28 Jul 2018 09:55:55 +0000 (UTC) Cc: yurivkhan@gmail.com, dgutov@yandex.ru, drew.adams@oracle.com, emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 28 11:55:51 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 1fjLx1-0003uI-11 for ged-emacs-devel@m.gmane.org; Sat, 28 Jul 2018 11:55:51 +0200 Original-Received: from localhost ([::1]:44512 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjLz5-0004s2-Ts for ged-emacs-devel@m.gmane.org; Sat, 28 Jul 2018 05:57:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40790) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjLyu-0004rg-TW for emacs-devel@gnu.org; Sat, 28 Jul 2018 05:57:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjLyr-0007Ap-Sn for emacs-devel@gnu.org; Sat, 28 Jul 2018 05:57:48 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:50280) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjLyh-0006zu-Nr; Sat, 28 Jul 2018 05:57:35 -0400 Original-Received: from [176.228.60.248] (port=2681 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fjLyh-0008QE-0i; Sat, 28 Jul 2018 05:57:35 -0400 In-reply-to: <87pnz7iv2y.fsf@gmx.de> (message from Michael Albinus on Sat, 28 Jul 2018 11:11:01 +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:227914 Archived-At: > From: Michael Albinus > Cc: Yuri Khan , emacs-devel@gnu.org, drew.adams@oracle.com, dgutov@yandex.ru > Date: Sat, 28 Jul 2018 11:11:01 +0200 > > Eli Zaretskii writes: > > >> It might be useful to give a subtle indication that the asynchronous > >> command finished, maybe by displaying a message in the echo > >> area. > > > > Not in the echo area, on the mode line. The echo area is too > > ephemeral. > > Some years ago, I've proposed an extension to the progress reporter for > the modeline, > . > Maybe we shall reanimate the proposal? Maybe so, but that's largely unrelated: the issue at hand here is how to indicate the progress/completion of an async file visiting command, with or without an infrastructure that makes such reporting easier or nicer. I think.