From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Message queue for Emacs? Date: Sun, 23 Apr 2017 14:21:17 -0700 Message-ID: <87inlu6cs2.fsf@ericabrahamsen.net> References: <87vapv9fyf.fsf@jane> <87pog26gz7.fsf@ericabrahamsen.net> <801751ec-b79a-4d11-90e0-b86b2dae6da0@default> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1492982549 14931 195.159.176.226 (23 Apr 2017 21:22:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Apr 2017 21:22:29 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Apr 23 23:22:25 2017 Return-path: Envelope-to: geh-help-gnu-emacs@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 1d2Oxc-0003m4-B6 for geh-help-gnu-emacs@m.gmane.org; Sun, 23 Apr 2017 23:22:24 +0200 Original-Received: from localhost ([::1]:40634 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2Oxi-0002Yh-2B for geh-help-gnu-emacs@m.gmane.org; Sun, 23 Apr 2017 17:22:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2Ox4-0002Ya-Kk for help-gnu-emacs@gnu.org; Sun, 23 Apr 2017 17:21:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d2Ox1-0005EZ-Fx for help-gnu-emacs@gnu.org; Sun, 23 Apr 2017 17:21:50 -0400 Original-Received: from [195.159.176.226] (port=44786 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d2Ox1-0005EO-9N for help-gnu-emacs@gnu.org; Sun, 23 Apr 2017 17:21:47 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d2Owt-0002rz-As for help-gnu-emacs@gnu.org; Sun, 23 Apr 2017 23:21:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 42 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:UZC2S4jJvrm4c0AznVJ+W3PewdE= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:112867 Archived-At: Drew Adams writes: >> >> a lot of Emacs commands send a (message "...") for a user in the echo >> >> area. Now imagine a command that sends more than of them (not unlikely >> >> e.g. if there are a few hooks, each printing a message). Of course, >> >> only the last one is then visible. Is there any way for the next >> >> message to be printed with some delay, so that the previous one is >> >> still visible, say, for a second or two? >> >> >> >> I know about C-h e (view-echo-area-messages), but this is not what I'm >> >> after. >> > >> > See `sit-for' and `sleep-for'. >> >> The disadvantage of that is that it would be blocking. > > Not `sit-for'. > >> It could be >> interesting if Emacs just piled up messages and displayed them one per >> second, without blocking whatever comes next. > > (message "A") (sit-for 1.0) (message "B") (sit-for 1.0) ... > (message "Z") No kidding! I never knew that -- I guess I've never tried to use it. >> If whatever comes next waits for user input in the minibuffer, >> hitting any key would cancel/flush the rest of the queue. > > Again, `sit-for' does that, and regardless of whether input is > to the minibuffer. Any user event cancels and flushes. > >> I can imagine all kinds of things going wrong, but it could be fun. > > It's unclear just what the OP is asking for (or why). Beat me, too. My guess was that he wanted this to be the default behavior for message. But I really don't know. Thanks for the tip, Eric