From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: jan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#41124: 26.3; highlight regexp not working properly - not updating as you type Date: Thu, 7 May 2020 19:25:04 +0100 Message-ID: References: <87sggbwt56.fsf@web.de> Reply-To: jan Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="32848"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 41124@debbugs.gnu.org To: Michael Heerdegen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 07 20:26:30 2020 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 1jWlE4-0008OT-EY for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 07 May 2020 20:26:28 +0200 Original-Received: from localhost ([::1]:39030 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jWlE1-0001Wl-Ab for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 07 May 2020 14:26:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42456) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWlDh-0001WL-Op for bug-gnu-emacs@gnu.org; Thu, 07 May 2020 14:26:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:60592) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jWlDe-0002Hu-N6 for bug-gnu-emacs@gnu.org; Thu, 07 May 2020 14:26:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jWlDe-0007pd-Jh for bug-gnu-emacs@gnu.org; Thu, 07 May 2020 14:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: jan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 07 May 2020 18:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41124 X-GNU-PR-Package: emacs X-Debbugs-Original-Cc: "jan via Bug reports for GNU Emacs, the Swiss army knife of text editors" , 41124@debbugs.gnu.org Original-Received: via spool by 41124-submit@debbugs.gnu.org id=B41124.158887591230016 (code B ref 41124); Thu, 07 May 2020 18:26:02 +0000 Original-Received: (at 41124) by debbugs.gnu.org; 7 May 2020 18:25:12 +0000 Original-Received: from localhost ([127.0.0.1]:43904 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jWlCq-0007o4-0N for submit@debbugs.gnu.org; Thu, 07 May 2020 14:25:12 -0400 Original-Received: from mail-pl1-f175.google.com ([209.85.214.175]:36319) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jWlCo-0007nb-Ob for 41124@debbugs.gnu.org; Thu, 07 May 2020 14:25:11 -0400 Original-Received: by mail-pl1-f175.google.com with SMTP id f15so2399406plr.3 for <41124@debbugs.gnu.org>; Thu, 07 May 2020 11:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+P3b1de8uULFUuGyPoc1z7eP2+uoKJxWSdhyOcUOnpo=; b=PgPTSGzStS8dY33DZjxnvHHOb3uIqEihs39wjOtH6kMfD6B/yFMBfp8/goT1zzl5eL JWzn86AwCY1h9+X0kCz1NVN3eKZeXIJSbsojoz9+JJITdB9QcXMYSAxtheRrMZCa6PLv Pb4icdazTduYlXGfksuO4Bo0BPFNH3X1zsJ9VNzuBedTj0sBjj1I71OMdpoKUlh8zNoe /IXTf7ydnnAzobi/C6PQXBSRf8tzuMbifHR+Eqn+W69W7v3CJEQ4gHDzR6PTqg1MNmne 5LzrqErNODb2dKaKzqbfUGzUhXre3vGVEdQbLA8oy15dtLLX2S/spXbAB9QkZGLomJxn v8kQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+P3b1de8uULFUuGyPoc1z7eP2+uoKJxWSdhyOcUOnpo=; b=WP/1Y1uJR2fpHcgWicxAoNnGe2yyBME1+X/2CUGgEOA9rg3LIwa9EAgawlhunWZ4MB vgGCXy3DIgojyhQRElKdTNi6CYt+9GXXKRPRizJDCnOq6IEq5OWTPr0siAobjU28XRBw GDB4VyWKSafxx768g7xrizydO92sb0Hxv3LGoj6uu+Q01TMapUItEdOEt35vrZC46kaJ AiqisZZKqa116fuxZY2+U5BUyuUePM8pGvxvFrT9H99AWUFPHxW7lDIbv9zDdUpPNxsw 1TQgZgswGhNIeuNIkSNX9UlvXRWpSYDjoQwmJKdv24mKGRAmHtgFkg5jgf54yD3D15ea iX4w== X-Gm-Message-State: AGi0Pua9Gc11TbdSIjX/qre1rap6xP6au8zS8Z9Vax+aecyzaBq110uZ kuOotDC7k7U9JGrtEIKfiBSBkFcOMqMO+3xayBk= X-Google-Smtp-Source: APiQypKQCowpZXxBh0Wu1FWbRo+FQInsuA6m6PDqFnxgNDh3aFEhaUkxdFueirdDOg4lt7KEh/YjGk2fiqXEDPRf9p4= X-Received: by 2002:a17:90a:bc4a:: with SMTP id t10mr1482734pjv.104.1588875904880; Thu, 07 May 2020 11:25:04 -0700 (PDT) Original-Received: by 2002:a17:90a:9a86:0:0:0:0 with HTTP; Thu, 7 May 2020 11:25:04 -0700 (PDT) In-Reply-To: <87sggbwt56.fsf@web.de> 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:179894 Archived-At: I don't understand this reply as I'm very much an emacs user not an emacs programmer, but "...could query the user whether he still wants to enable hi-locking using font-lock, with the risk of messing up..." - this kind of thing, letting me know I can't have what I'm asking for (or can but at a risk) would be helpful so I know I'm not going to get it. I reported this as a bug out of ignorance, some hint from emacs that it was PEBKAC[0] would have saved me wasting Eli's time. jan [0] On 07/05/2020, Michael Heerdegen wrote: > jan via "Bug reports for GNU Emacs, the Swiss army knife of text > editors" writes: > >> First ensure font-lock mode is on. Prefix arg forces it on. >> >> C-u 1 M-x font-lock-mode >> >> Minibuffer says font lock mode is enabled > > @jan: The test that hi-lock uses internally is actually > > (and font-lock-mode (font-lock-specified-p major-mode)) > > so you need an implemented font-locking in your buffer. I guess this is > intentional and has its reasons. But yes, it is surprising. > > @Eli: the docstring of `hi-lock-mode' just says: > > "In buffers where Font Lock mode is enabled, patterns are > highlighted using font lock." > > That's wrong, I think the docstring should be adapted. _Or_ > hi-lock-mode could query the user whether he still wants to enable > hi-locking using font-lock, with the risk of messing up other > highlighting that doesn't come from font-lock. > > Michael. >