From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#17272: bug#19064: bug#17272: bug#19064: 25.0.50; `message' overwrites `y-or-n-p' prompt, so user misses it Date: Wed, 13 Nov 2019 22:29:50 +0100 Message-ID: <87sgmrpir5.fsf@web.de> References: <8ea0a3fa-5169-4493-bd54-3ebe47836a35@default> <87r3i9nped.fsf@gnus.org> <87wps1m7co.fsf@web.de> <87y4chjdop.fsf@gnus.org> <87o8ys3131.fsf@gnus.org> <875zjx6hs6.fsf@mail.linkov.net> <87sgmy3x22.fsf@gnus.org> <871rugbqmy.fsf@mail.linkov.net> <87d0dxyh7z.fsf@gnus.org> <53c55db5-d623-4946-af2e-d141e7bc7acd@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="180331"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , Juri Linkov , 17272@debbugs.gnu.org, 19064@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 13 22:33:48 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1iV0Gq-000kmz-IA for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Nov 2019 22:33:48 +0100 Original-Received: from localhost ([::1]:51292 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iV0Gp-0006ja-5r for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Nov 2019 16:33:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34349) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iV0ED-000526-LB for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 16:31:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iV0EB-00010t-OJ for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 16:31:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51402) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iV0EA-00010L-PN for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 16:31:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iV0EA-0007Mj-IX for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 16:31:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Nov 2019 21:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 17272 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 17272-submit@debbugs.gnu.org id=B17272.157368060228166 (code B ref 17272); Wed, 13 Nov 2019 21:31:02 +0000 Original-Received: (at 17272) by debbugs.gnu.org; 13 Nov 2019 21:30:02 +0000 Original-Received: from localhost ([127.0.0.1]:60220 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iV0DB-0007K0-Nb for submit@debbugs.gnu.org; Wed, 13 Nov 2019 16:30:02 -0500 Original-Received: from mout.web.de ([212.227.17.11]:53965) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iV0DA-0007JL-2w; Wed, 13 Nov 2019 16:30:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1573680579; bh=54iA+6BZMPaJgbIcz7Ev7qoRSe0C8DjHzApHhOBOky4=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=ZQaYBo/XUnXy3qXMdsJxzAFXwuntlKZKkiMYu3WJqommd0LP8FzEWCmPaJG+bJNZS pIUd2v+H/f6KQX4hiIfbbzzr7p3HYg4MJeevNez5hqcZ/9EdzMuE30rRuMRyzQYdK1 MGInacYI/dshQR79wekay11VHmZO1NmCf8uxV0wg= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([94.218.222.9]) by smtp.web.de (mrweb101 [213.165.67.124]) with ESMTPSA (Nemesis) id 0LpNwf-1hzUgA2PkT-00fAmK; Wed, 13 Nov 2019 22:29:39 +0100 In-Reply-To: <53c55db5-d623-4946-af2e-d141e7bc7acd@default> (Drew Adams's message of "Tue, 12 Nov 2019 15:34:45 +0000 (UTC)") X-Provags-ID: V03:K1:LXVp1l94Qs+UrCZRsKNOA/AjNATaectwJedOx7AKz5OKkdPjNPB NQdJwlaJX2pzAVlNrG6AP/9lB94WMs12/cSHV8q42q9lNr7MsyMDwKJpufh9+H9tVhKQYvA EkXmCP+8mBvDPhtNnPM9+SBnNz44TCsROJIecKBNhuN2Y7WlPCTkYyl3CNlTqtpAWCbwAzw mrNcUIBRVxz134ojDUZHg== X-UI-Out-Filterresults: notjunk:1;V03:K0:xrPHe4OZh9k=:MwXBvPcTw2FWHSkGhNra+Y okoMhg04UHso1B6W7ia7c685hgbd6tWCULKyVBQtFi+TaRSrt1humiR9TGYhxLpel6zlafmf+ b8M9e+VGZfXSQ1zme+eQ9yKUHBnb3wqHtwo6KjwG12S3yXw5GfqszAHGkiQ9+4hN5+03CQDq0 KReZezta+6LhLjPKy6c97so1mfoOG/+8kL5VDmrWbooNJ+LMUGdePM8g4yeDquwSfoV8X5yvV KybzSa6jJ5ihKCHIrD1P6/svs4FN0OUZPs6lHfrjl48saAb4dakeTRE9JtRDYT7FcHGeJl/Qu tZeW2TYk09W+kH7ZOW4hw8NDLHygwv036RxC6tlLsrV27QpJljpwChviBexfiF3MtFKzSO3CR 85WtgZTIpvhXuvkZVopT07JpYph7w5CCtqNZpeFzCHhfXp7zTI3jA23B3tto4dIQMORtCFKoR 7Powtbw93EV5kWw31TN0IXng1Yv5D6XELEBHS8Ap6TXX30fiS9rkFW/n1DVHl3mWXbVYhOFiV 0Y0zcy3vTSiVcyoGaJ/9EOxTvtx9WeqtPKFpsFhWRFqtlniDtyHuHgBzY3Q5FcM4TJQA3Q/a4 svCaM+QZZh1ZTvbZD/DhDVn06Wr2lgYNJN5pRhWSGwVGeO0b/v76xhyemX4vGydutgzkrStiO jJfuZzjDHvRvFiRIRptOMy1dfvXlDShIa+SDm37PxaogqGC6yuLWmHknXqVKWZQfAF5gv+IyD 3rQ4wwz52wWi6GoL7vtmqDIJQCEERANWZ+H1N+3PHzYZoSSAxwl2DOEZ6M7fp2/HO5rTKM3k X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:171503 Archived-At: Drew Adams writes: > I'm sorry, but I can't follow this. I don't know > what's been changed, or why. (There are even two > bugs that are being handled here, apparently.) I understand your question as if you want to know whether there has some general magic been implemented to decide where to show messages. AFAIU the issues fixed were all special cases were a message hided some y-or-n-p prompt so that the user may have missed the prompt, or may have wondered what to do to get it back. > What I've said is that I object to an automatic > attempt to determine, when the minibuffer is > active, whether to realize the effect of `message' > or the effect of `minibuffer-message'. AFAICT only the behavior for these special situations have been made a bit more user friendly, and all other calls of message or mb-message are uneffected (is that correct, Juri?) so that third party stuff should not be affected. `y-or-n-p' has been reimplemented to use read-from-minibuffer instead of read-key, however (Juri please correct me if I'm wrong). Michael.