From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: HaiJun Zhang Newsgroups: gmane.emacs.bugs Subject: bug#38457: 27.0.50; dabbrev-expand regression due to message change Date: Wed, 11 Dec 2019 11:24:37 +0800 Message-ID: References: <8736e3vve8.fsf@gmx.net> <8736e2coyv.fsf@mail.linkov.net> <83y2vujd0y.fsf@gnu.org> <87blspm0sm.fsf@mail.linkov.net> <837e3ckbem.fsf@gnu.org> <871rtjn0kt.fsf@mail.linkov.net> <83lfrrigj8.fsf@gnu.org> <87eexiqps5.fsf@mail.linkov.net> <83lfrphp94.fsf@gnu.org> <87wob7g2jk.fsf@mail.linkov.net> <83k177ebs0.fsf@gnu.org> <87muc27prn.fsf@mail.linkov.net> <83tv6acgq5.fsf@gnu.org> <87eexdoygh.fsf@mail.linkov.net> <83tv68c0nb.fsf@gnu.org> <83h828b0lz.fsf@gnu.org> <83eexcax6b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="5df0617b_bf72b14_422" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="151674"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 38457@debbugs.gnu.org, juri@linkov.net To: Stefan Monnier , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Dec 11 04:25:15 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 1iesch-000dCw-TC for geb-bug-gnu-emacs@m.gmane.org; Wed, 11 Dec 2019 04:25:12 +0100 Original-Received: from localhost ([::1]:38256 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iescg-0002bb-7U for geb-bug-gnu-emacs@m.gmane.org; Tue, 10 Dec 2019 22:25:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57335) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iescZ-0002b6-93 for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2019 22:25:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iescX-0007HF-Sr for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2019 22:25:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50835) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iescX-0007Gw-Of for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2019 22:25:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iescX-0002fE-KU for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2019 22:25:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: HaiJun Zhang Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 11 Dec 2019 03:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38457 X-GNU-PR-Package: emacs Original-Received: via spool by 38457-submit@debbugs.gnu.org id=B38457.157603469810229 (code B ref 38457); Wed, 11 Dec 2019 03:25:01 +0000 Original-Received: (at 38457) by debbugs.gnu.org; 11 Dec 2019 03:24:58 +0000 Original-Received: from localhost ([127.0.0.1]:56808 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iescU-0002er-7d for submit@debbugs.gnu.org; Tue, 10 Dec 2019 22:24:58 -0500 Original-Received: from mail-oln040092255093.outbound.protection.outlook.com ([40.92.255.93]:52374 helo=APC01-HK2-obe.outbound.protection.outlook.com) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iescR-0002ec-RB for 38457@debbugs.gnu.org; Tue, 10 Dec 2019 22:24:56 -0500 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iJgRIYcSuGzu6+zJa194Cf2fyNUtqVxbSjnMJ9ePLq+LsiycWgSVxWrvlg62k3lY7xtBInkA+trXabYUx6NCOiOPck2kinEZkvVrETavIsJGX/nEIrWSFFOJNgoYhM53L2zE5au0G1oLAz0iCtEP0wojhYYcz0ayxYGuhXliOVlN9HfAu3HwtpQ7x/g7mmP4GrN+RrFG+lkI2AEjVvtNBKqt1JzhjEHcvoEcXVrm4uHigYP6cwBPWzKKdctJISDrlovKdzfc+MlZ4X0RjDMk5MP+ZQ9dS56kaz3F8YuXsKChKm7RZchf0DzQ46Hnz7dVbbPFgSeSWcAf40o0orxIdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bXd7PikrLaXQjx+U9utBmos2n34yL3UEWx3po2UJYkw=; b=nTNiSBlLqKHzQ6o2yvc0bF9Mlw2EAqFi3Lx9t2G1JUiBFtqKqsI+M6lcSV3V/ukfMHIVzDrgUYEvc/N9k7jVIwfgQp7N8ZmEd9AeWrZXLFumBAFzfhL68R6ElYW3UUCZSa7gzDXVjeLSpZ/P+/+qY94/QjnEfkt+i3QmAbj04u8rfYGvI0dPo4RiI0k3QsUBfPJEPy6jTofA70tUro9koDseKMwmo0b8jkAITMRHGenCBRrwoTFvtJw4TKBM3qfq6DupeeEEEK94rSRcegQUoR5MipnpIGtATx0zyvj9X47iCrMUoFG8amkdrzqKfWHjKPFpqBrKUEg4UmqexZyNkw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=outlook.com; dmarc=pass action=none header.from=outlook.com; dkim=pass header.d=outlook.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bXd7PikrLaXQjx+U9utBmos2n34yL3UEWx3po2UJYkw=; b=q/+p21HV8pUC/bdTfRzd2VaSaro5EYZsBxZCUPlr0j/Rtjt67sC0z84Oe1u9dvaeje2p1+7JiQpiwmpxj+TAZS4tMOxLOlWPSociT452huzfjRfezJDcrfqjWyvhSLIWLgFz2VkRynYREZf/yv9h1Xz2PH6l1FvVhSwh1/RccLOTFDmvq6W5Wx2uMLvz5uzimViwQH77HI0NRY4aNcuEdHWGkk+tY+o/yGwyNOlU2rpZxdqwGhbbL4CsuKQoakxng87djIO5JHZ/uMXtOF9iHPonAu/CzgXCzSn7mli39z8R8X1hjyM/UsRNsjUaxJAQobQSFjB1X/wCMOdc3VdjGw== Original-Received: from PU1APC01FT013.eop-APC01.prod.protection.outlook.com (10.152.252.57) by PU1APC01HT097.eop-APC01.prod.protection.outlook.com (10.152.253.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.25; Wed, 11 Dec 2019 03:24:46 +0000 Original-Received: from PS1PR03MB3606.apcprd03.prod.outlook.com (10.152.252.56) by PU1APC01FT013.mail.protection.outlook.com (10.152.252.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.25 via Frontend Transport; Wed, 11 Dec 2019 03:24:46 +0000 X-IncomingTopHeaderMarker: OriginalChecksum:9A30A75E6B2B32EE9D9A0A9AE2BFF400433A8AAD1AAA03FEC6DCE3A78B4C358D; UpperCasedChecksum:9A29B6276A4358065EABA6151DA932A3EFFBB450A24FEFCE9C0908A7584C8F6E; SizeAsReceived:9252; Count:48 Original-Received: from PS1PR03MB3606.apcprd03.prod.outlook.com ([fe80::b05a:28e4:205a:d7d4]) by PS1PR03MB3606.apcprd03.prod.outlook.com ([fe80::b05a:28e4:205a:d7d4%5]) with mapi id 15.20.2538.012; Wed, 11 Dec 2019 03:24:46 +0000 In-Reply-To: <83eexcax6b.fsf@gnu.org> X-Readdle-Message-ID: 5959a137-1114-4f8f-9401-bdc5dee67522@Spark X-ClientProxiedBy: HK2PR02CA0210.apcprd02.prod.outlook.com (2603:1096:201:20::22) To PS1PR03MB3606.apcprd03.prod.outlook.com (2603:1096:803:4e::17) X-Microsoft-Original-Message-ID: <5959a137-1114-4f8f-9401-bdc5dee67522@Spark> Original-Received: from [192.168.1.103] (1.199.222.221) by HK2PR02CA0210.apcprd02.prod.outlook.com (2603:1096:201:20::22) with Microsoft SMTP Server (version=TLS1_2, cipher=) via Frontend Transport; Wed, 11 Dec 2019 03:24:45 +0000 X-Readdle-Message-ID: 5959a137-1114-4f8f-9401-bdc5dee67522@Spark X-Microsoft-Original-Message-ID: <5959a137-1114-4f8f-9401-bdc5dee67522@Spark> X-TMN: [8UTVnhdZvmWaHAdQxGiJsmrzGHUS9fDs] X-MS-PublicTrafficType: Email X-IncomingHeaderCount: 48 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-Correlation-Id: 93d66e82-aeb2-4d33-bae1-08d77de9ac2c X-MS-TrafficTypeDiagnostic: PU1APC01HT097: X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: yUmu6CjzU9hxbLc9WYu5cSjcuAbzFiz87D6eQje0eXDI/lj/YEE1Irs7K1AHeMW6G5tmHrO6emQBaIiYwyyzAnW0dF6GI8mDQHvzbjWBUXgnJzWWfvJx4mtHg8VqwdA2fufG8GGcz6uYuQCBY3F9khXPG+8xn9e7PadDiUZczkH+LvN6C2BaV3BkCJdC6jOL X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 93d66e82-aeb2-4d33-bae1-08d77de9ac2c X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Dec 2019 03:24:46.8397 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT097 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:173167 Archived-At: --5df0617b_bf72b14_422 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =E5=9C=A8 2019=E5=B9=B412=E6=9C=8811=E6=97=A5 +0800 AM1:50=EF=BC=8CEli Za= retskii =EF=BC=8C=E5=86=99=E9=81=93=EF=BC=9A > > If resize-mini-windows is nil, the result will be the same as with the > current code, which calls minibuffer-message: the message is partially > or completely invisible. > > > BTW, we should probably think about replacing =60message=60 with some= thing > > that lets the caller give more information about the intended behavio= r > > (e.g. to also solve the issue of several successive calls to message > > resulting in the user only seeing the last message). Of course, this > > would be for Emacs-28. > > Right. > Display combination of the prompt and the message is good but may be comp= lex to implement it. What about display message transiently and then restore to prompt=3F I see the doc string of minibuffer-message-timeout says: How long to display an echo-area message when the minibuffer is active. If the value is a number, it should be specified in seconds. If the value is not a number, such messages never time out. If minibuffer is active, the message will be displayed =C2=A0for a moment= (like 1s) and then disappears. If minibuffer is not active, the message will be displayed forever. I thi= nk this is simpler and also good for me. What is the problem of this behaviour=3F Is it easier to implement=3F --5df0617b_bf72b14_422 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
=E5=9C=A8 2019=E5=B9=B412=E6=9C=8811=E6= =97=A5 +0800 AM1:50=EF=BC=8CEli Zaretskii <eliz@gnu.org>=EF=BC=8C= =E5=86=99=E9=81=93=EF=BC=9A

If resize-mini-windows is nil, the result will be the same as with the
current code, which calls minibuffer-message: the message is partially
or completely invisible.

BTW, we should probabl= y think about replacing `message` with something
that lets the caller give more information about the intended behavior
(e.g. to also solve the issue of several successive calls to message
resulting in the user only seeing the last message). Of course, this
would be for Emacs-28.

Right.


Display combination of the prompt and the message is good= but may be complex to implement it.
What about display message transiently and then restore t= o prompt?

I see the doc string of minibuffer-message-timeout says:

How long to display an echo-area message when the minibuf= fer is active.
If the value is a number, it should be specified in secon= ds.
If the value is not a number, such messages never time ou= t.

If minibuffer is active, the message will be displayed &n= bsp;for a moment(like 1s) and then disappears.
If minibuffer is not active, the message will be displaye= d forever. I think this is simpler and also good for me.

What is the problem of this behaviour? Is it easier to im= plement?


--5df0617b_bf72b14_422--