From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#38457: 27.0.50; dabbrev-expand regression due to message change Date: Wed, 11 Dec 2019 18:26:26 +0200 Message-ID: <83zhfyakwd.fsf@gnu.org> 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> <835zinbkct.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="251005"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 38457@debbugs.gnu.org, monnier@iro.umontreal.ca, juri@linkov.net To: HaiJun Zhang Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Dec 11 17:28:29 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 1if4qi-00135m-0v for geb-bug-gnu-emacs@m.gmane.org; Wed, 11 Dec 2019 17:28:28 +0100 Original-Received: from localhost ([::1]:45596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1if4qb-0004MA-Ik for geb-bug-gnu-emacs@m.gmane.org; Wed, 11 Dec 2019 11:28:21 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41348) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1if4pN-0003FG-UB for bug-gnu-emacs@gnu.org; Wed, 11 Dec 2019 11:27:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1if4pM-0005gh-MV for bug-gnu-emacs@gnu.org; Wed, 11 Dec 2019 11:27:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52619) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1if4pK-0005fO-Ke for bug-gnu-emacs@gnu.org; Wed, 11 Dec 2019 11:27:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1if4pK-0005kR-EU for bug-gnu-emacs@gnu.org; Wed, 11 Dec 2019 11:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 11 Dec 2019 16:27:02 +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.157608161322081 (code B ref 38457); Wed, 11 Dec 2019 16:27:02 +0000 Original-Received: (at 38457) by debbugs.gnu.org; 11 Dec 2019 16:26:53 +0000 Original-Received: from localhost ([127.0.0.1]:58592 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1if4p8-0005jy-0i for submit@debbugs.gnu.org; Wed, 11 Dec 2019 11:26:53 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58616) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1if4p6-0005jm-UD for 38457@debbugs.gnu.org; Wed, 11 Dec 2019 11:26:49 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45014) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1if4oz-0005Kt-TD; Wed, 11 Dec 2019 11:26:42 -0500 Original-Received: from [176.228.60.248] (port=1372 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1if4ou-0002Li-PS; Wed, 11 Dec 2019 11:26:41 -0500 In-reply-to: (message from HaiJun Zhang on Wed, 11 Dec 2019 11:59:48 +0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:173184 Archived-At: > Date: Wed, 11 Dec 2019 11:59:48 +0800 > From: HaiJun Zhang > Cc: monnier@iro.umontreal.ca, 38457@debbugs.gnu.org, juri@linkov.net > > I explained in more detail how I suggested to implement thius: by > inserting the minibuffer contents before the message text. What is > complex about that? > > Because resize-mini-windows may be nil. And the message may be invisible. The current master has the same problem. In general, people who set resize-mini-windows to nil are always in danger of seeing only part of the message Emacs displays. > Another question: > When emacs displays combination of the prompt and the message, if user input something, doesn’t the > message disappears? It does disappear, and the prompt remains. Again, lime with the current master. > This is what the current code does, > > The current code doesn’t display the message transiently. It displays it forever. By "the current code" I meant the current master branch. There, the message is displayed for 2 sec, and then disappears, even if the user didn't press any key. Which is different from how 'message' behaves when there's no prompt. > User needs to press a key to > restore to the prompt. Is this a bug? No, I don't think it's a bug. If some Lisp program displays a message and doesn't follow it with a nil message, it means that Lisp program _wants_ the message to remain on display until the user dismisses it. > and the problem with that is that > some uses of 'message' don't expect the message to stay for 2 seconds, > and some expect it to stay forever. This information is not explicit > in the call to 'message', so there's no way of communicating in down > to minibuffer-message. > > Do you mean the scene “Foo…” followed by “Foo…done”? That's one scenario, yes. But it is not the only one. > I don’t think this is a problem. These are just status which are not important. And they disappears quickly > when user is busy editing. With the current master, it doesn't disappear quickly, it stays for 2 sec. > And the really important ones may put an indicator on the mode-line. What indicator? (And I don't understand why we are arguing, since you just said in another message that you liked my proposal...)