From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Strange use of (run-with-timer 0 nil #'foo args) in do-after-load-evaluation Date: Wed, 30 Oct 2019 00:58:19 +0100 Message-ID: <87d0efxfxg.fsf@gnus.org> References: <20191026101407.GA17424@ACM> <87o8y3d4ur.fsf@gnus.org> <87mudl3l83.fsf@mail.linkov.net> <87v9s9b12x.fsf@gnus.org> <87ftjctsx5.fsf@mail.linkov.net> <87k18n233r.fsf@gnus.org> <87pnifcdzd.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="30602"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Alan Mackenzie , Stefan Monnier , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 30 00:59:25 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPbOX-0007s1-4w for ged-emacs-devel@m.gmane.org; Wed, 30 Oct 2019 00:59:25 +0100 Original-Received: from localhost ([::1]:35284 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPbOV-00041v-K7 for ged-emacs-devel@m.gmane.org; Tue, 29 Oct 2019 19:59:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58350) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPbNc-00040Z-6P for emacs-devel@gnu.org; Tue, 29 Oct 2019 19:58:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPbNb-0005au-4Y for emacs-devel@gnu.org; Tue, 29 Oct 2019 19:58:28 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:40724) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iPbNa-0005Yu-Tq for emacs-devel@gnu.org; Tue, 29 Oct 2019 19:58:27 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPbNU-00049x-J1; Wed, 30 Oct 2019 00:58:23 +0100 In-Reply-To: <87pnifcdzd.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 30 Oct 2019 01:45:58 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 80.91.231.51 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241613 Archived-At: Juri Linkov writes: > 'message' can be easily replaced with 'minibuffer-message', > then it doesn't obscure the minibuffer: > > (progn > (run-at-time 2 nil (lambda () (minibuffer-message "foo"))) > (read-from-minibuffer "Yes? ")) Oh, nice. I guess whenever we're displaying things from an async context, we should be using minibuffer-message? > Whereas it obscures the prompt in y-or-n-p: > > (progn > (run-at-time 2 nil (lambda () (minibuffer-message "foo"))) > (y-or-n-p "Yes? ")) Then I'm all for your suggestion to rewrite y-or-n-p with read-from-minibuffer... but without a history. (And yes-or-no-p too, somehow, I guess.) (Or fix both of those functions to work the same with respect to minibuffer-message.) -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no