From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: M-o M-o `font-lock-fontify-block' Date: Sun, 14 Feb 2021 12:23:01 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30796"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 14 13:24:37 2021 Return-path: Envelope-to: ged-emacs-devel@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 1lBGS5-0007v9-0t for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Feb 2021 13:24:37 +0100 Original-Received: from localhost ([::1]:54764 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lBGS4-0007a6-3o for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Feb 2021 07:24:36 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38266) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lBGQg-00078k-By for emacs-devel@gnu.org; Sun, 14 Feb 2021 07:23:10 -0500 Original-Received: from colin.muc.de ([193.149.48.1]:49548 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1lBGQc-0004bJ-IJ for emacs-devel@gnu.org; Sun, 14 Feb 2021 07:23:09 -0500 Original-Received: (qmail 10559 invoked by uid 3782); 14 Feb 2021 12:23:01 -0000 Original-Received: from acm.muc.de (p2e5d5f6c.dip0.t-ipconnect.de [46.93.95.108]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 14 Feb 2021 13:23:01 +0100 Original-Received: (qmail 5978 invoked by uid 1000); 14 Feb 2021 12:23:01 -0000 Content-Disposition: inline X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, GAPPY_SUBJECT=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:264692 Archived-At: Hello, Emacs. On master, I just typed M-o M-o and instead of font-lock-fontify-block, got a window with the M-o removal message. I've been using this binding subconsciously for many years now, and it was a bit of a jolt for it not to work. I need this function for refontifying hi-lock-mode patterns which get split onto two lines by auto filling. For example I have a pattern for "bug #12345" with arbitrary whitespace, and this fairly often gets split by a linefeed. Clearly, this is a candidate for C-c for me. Typing M-x font-lock-fontify-block would be intolerable after a very short while. But, more to the point, a user accustomed to M-o M-o is going to have inordinate difficulty finding the command to bind. Two of the M-o bindings are mentioned in NEWS, to give people help. Why not all of them? Also, why must font-lock mode operating on patterns from hi-lock-mode be unable to fontify over a line-break? This is surely something it ought to be able to do. Setting font-lock-multiline to t doesn't help in this case. -- Alan Mackenzie (Nuremberg, Germany).