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: Mon, 28 Oct 2019 11:45:26 +0100 Message-ID: <87v9s9b12x.fsf@gnus.org> References: <20191026101407.GA17424@ACM> <87o8y3d4ur.fsf@gnus.org> <87mudl3l83.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="14839"; 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 Mon Oct 28 11:46:42 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 1iP2Xp-0003iG-GY for ged-emacs-devel@m.gmane.org; Mon, 28 Oct 2019 11:46:41 +0100 Original-Received: from localhost ([::1]:52458 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iP2Xo-0006fn-8X for ged-emacs-devel@m.gmane.org; Mon, 28 Oct 2019 06:46:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41050) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iP2Wl-0006do-J8 for emacs-devel@gnu.org; Mon, 28 Oct 2019 06:45:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iP2Wk-000819-7x for emacs-devel@gnu.org; Mon, 28 Oct 2019 06:45:35 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:32948) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iP2Wk-00080W-0w for emacs-devel@gnu.org; Mon, 28 Oct 2019 06:45:34 -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 1iP2Wd-00067g-AY; Mon, 28 Oct 2019 11:45:29 +0100 In-Reply-To: <87mudl3l83.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 27 Oct 2019 23:57:32 +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:241551 Archived-At: Juri Linkov writes: >> Yup. There are several bug reports on this (general) issue of >> asynchronous messages hiding queries. One suggestion has been to extend >> the echo area in these instances, showing the message (perhaps) below >> the prompt. Another is to have the prompt re-assert itself after a >> timeout, making the message disappear. > > These bug reports are fixed now when messages are displayed in the > minibuffer, but the problem still exists for the y-or-n-p prompt. So read-from-minibuffer reasserts the query if an asynchronous message hides it? Then that sounds like a good idea. On the other hand, y-or-n-p could just call read-char/event with a timeout and do the same thing. > Why y-or-n-p doesn't use normal minibuffer functions? > > It can finely use read-from-minibuffer with a keymap where > 'y' and 'n' keys are bound to minibuffer-exiting commands. > > Then history commands will be available for free, so you don't need > to re-implement minibuffer history commands with `read-char-with-history'. I think having a history for y-or-n-p doesn't sound very useful? Hitting `M-p' doesn't to get to the previous answer just sounds confusing to me. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no