From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#13752: Suggestions regarding the minibuffer Date: Mon, 31 May 2021 23:13:03 +0300 Message-ID: <87v96ylmew.fsf@linkov.net> References: <87zgwbidqs.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13786"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: E Sabof , 13752@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 31 22:31:16 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lnoZA-0003UJ-B4 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 31 May 2021 22:31:16 +0200 Original-Received: from localhost ([::1]:36626 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lnoZ9-0004zr-Cm for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 31 May 2021 16:31:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57812) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lnoYw-0004zZ-Sj for bug-gnu-emacs@gnu.org; Mon, 31 May 2021 16:31:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51653) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lnoYw-0005xm-LZ for bug-gnu-emacs@gnu.org; Mon, 31 May 2021 16:31:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lnoYw-0006wA-Hn for bug-gnu-emacs@gnu.org; Mon, 31 May 2021 16:31:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 31 May 2021 20:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13752 X-GNU-PR-Package: emacs Original-Received: via spool by 13752-submit@debbugs.gnu.org id=B13752.162249306126659 (code B ref 13752); Mon, 31 May 2021 20:31:02 +0000 Original-Received: (at 13752) by debbugs.gnu.org; 31 May 2021 20:31:01 +0000 Original-Received: from localhost ([127.0.0.1]:34965 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lnoYv-0006vv-Eo for submit@debbugs.gnu.org; Mon, 31 May 2021 16:31:01 -0400 Original-Received: from relay7-d.mail.gandi.net ([217.70.183.200]:38363) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lnoYt-0006ve-BJ for 13752@debbugs.gnu.org; Mon, 31 May 2021 16:31:00 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 331C620002; Mon, 31 May 2021 20:30:50 +0000 (UTC) In-Reply-To: <87zgwbidqs.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 31 May 2021 09:06:19 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:207727 Archived-At: >> 1. Would it be possible to add a property to error symbols that would prevent the error >> message from appearing in the mini-buffer? I see little utility in messages such a "End >> of buffer", "Beginning of buffer" and "Text read-only". It could be seen as >> implementation logic leaking into UI. > > Hm. I thought that the introduction of `set-message-function' would > allow users to filter messages like this, but > > (setq set-message-function (lambda (string) > 'no)) > > only seems to inhibit messages from `message', not from `signal'? I'm > having some difficulty tracing the logic here... Anybody know whether > this is by design? This looks like a new feature request :-) If this can't be implemented using the existing signal-hook-function or signaling-function, maybe then a new set-signal-function could be added?