From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Strange use of (run-with-timer 0 nil #'foo args) in do-after-load-evaluation Date: Tue, 29 Oct 2019 00:19:02 +0200 Organization: LINKOV.NET Message-ID: <87ftjctsx5.fsf@mail.linkov.net> References: <20191026101407.GA17424@ACM> <87o8y3d4ur.fsf@gnus.org> <87mudl3l83.fsf@mail.linkov.net> <87v9s9b12x.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="252004"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: Alan Mackenzie , Stefan Monnier , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 29 00:07:22 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 1iPE6Z-0013Nr-F9 for ged-emacs-devel@m.gmane.org; Tue, 29 Oct 2019 00:07:19 +0100 Original-Received: from localhost ([::1]:45174 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPE6Y-0007uD-79 for ged-emacs-devel@m.gmane.org; Mon, 28 Oct 2019 19:07:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54870) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPE3H-0004W4-AU for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:03:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPE0S-0000tp-TR for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:01:01 -0400 Original-Received: from bird.elm.relay.mailchannels.net ([23.83.212.17]:64860) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iPE0S-0000t1-IE for emacs-devel@gnu.org; Mon, 28 Oct 2019 19:01:00 -0400 X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 084C114113A; Mon, 28 Oct 2019 23:00:58 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a29.g.dreamhost.com (100-96-85-194.trex.outbound.svc.cluster.local [100.96.85.194]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 92DD51411D5; Mon, 28 Oct 2019 23:00:57 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a29.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Mon, 28 Oct 2019 23:00:57 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Befitting-Attack: 37a6474c6380c797_1572303657834_1058558192 X-MC-Loop-Signature: 1572303657834:2721132958 X-MC-Ingress-Time: 1572303657834 Original-Received: from pdx1-sub0-mail-a29.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a29.g.dreamhost.com (Postfix) with ESMTP id 0315598F8E; Mon, 28 Oct 2019 16:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=linkov.net; bh=7HO+vEMnRD2wz4cbc5L6uJaMhWs=; b= O42FOt3lMUhVXO5hWE04c3I9Vrjs2SWl96rKgdpQ76bEyBTWfbvzmjUl3Ad5/epC XrCxpRYDKs1Q+Pd5Jtsq6vI3x9xt/ItkJNHmUUYv3g6CbnvMx/PZwfvPQAVWYPqL Z3VRtYrLs4d1DSNOls35MiishaBwk/OfmS8E6/T/97k= Original-Received: from mail.jurta.org (m91-129-101-77.cust.tele2.ee [91.129.101.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a29.g.dreamhost.com (Postfix) with ESMTPSA id AF3FF995C7; Mon, 28 Oct 2019 16:00:52 -0700 (PDT) X-DH-BACKEND: pdx1-sub0-mail-a29 In-Reply-To: <87v9s9b12x.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 28 Oct 2019 11:45:26 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.212.17 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:241565 Archived-At: >> 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? An asynchronous message doesn't hide the minibuffer. It's displayed at the end of the minibuffer text. >> 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. Please try the example I sent earlier. It feels quite naturally typing 'M-p RET' to repeat a previous y/n answer.