unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: jan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41124@debbugs.gnu.org
Subject: bug#41124: 26.3; highlight regexp not working properly - not updating as you type
Date: Thu, 7 May 2020 16:36:02 +0100	[thread overview]
Message-ID: <CADJx9LdJmRQdp9517uKi2B1_EGD4=buoQ3SEoHyk3_1qto4T+w@mail.gmail.com> (raw)
In-Reply-To: <83lfm3kfgb.fsf@gnu.org>

Hi,
I don't know much about modes, I'm an emacs user rather than an emacs
programmer. So yep, it was fundamental. I'll do some reading on modes
tonight.

But FWIW I found this originally happening in another mode where I was
trying to identify large chunks easily.
So while this is surely my mistake also, to reproduce, I dragged a.txt
file from a git repo into emacs (again, windows - started with emacs
-Q to be sure)

It said 'git-master' in the status bar.

M-x describe-mode gives

Enabled minor modes: Auto-Composition Auto-Compression Auto-Encryption
Blink-Cursor Diff-Auto-Refine Electric-Indent File-Name-Shadow
Font-Lock Global-Eldoc Global-Font-Lock Line-Number Menu-Bar
Mouse-Wheel Tool-Bar Tooltip Transient-Mark

I can reproduce my 'wrong' behaviour in this text file. I wasn't expecting that.

So FYI and this is surely just my misunderstanding, sorry for messing
you around.

jan



On 07/05/2020, Eli Zaretskii <eliz@gnu.org> wrote:
> [Please keep the bug address on the CC list; use Reply All.]
>
>> From: jan <rtm443x@googlemail.com>
>> Date: Thu, 7 May 2020 14:39:28 +0100
>>
>> Tried it in windows with -Q
>> Works as expected in *scratch*, but create another buffer (C-x b asdf)
>> and it does not.
>
> That other buffer is in Fundamental mode, right?  Font-lock does
> nothing in Fundamental mode.
>





  reply	other threads:[~2020-05-07 15:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 11:32 bug#41124: 26.3; highlight regexp not working properly - not updating as you type jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <handler.41124.B.158885115315161.ack@debbugs.gnu.org>
2020-05-07 11:39   ` bug#41124: Acknowledgement (26.3; highlight regexp not working properly - not updating as you type) jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 12:57     ` bug#41124: 26.3; highlight regexp not working properly - not updating as you type Eli Zaretskii
2020-05-07 12:55 ` Eli Zaretskii
     [not found]   ` <CADJx9LfmRc+CoiVmzb_sa=mgQSwTxPbjNPYPEr9ss+heeebN_g@mail.gmail.com>
2020-05-07 14:05     ` Eli Zaretskii
2020-05-07 15:36       ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-05-07 16:54         ` Eli Zaretskii
2020-05-07 17:32           ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 17:58             ` Eli Zaretskii
2020-05-07 17:29 ` Michael Heerdegen
2020-05-07 17:58   ` Eli Zaretskii
2020-05-07 23:12     ` Michael Heerdegen
2020-05-08 14:27       ` Eli Zaretskii
2022-03-23 12:40         ` Lars Ingebrigtsen
2020-05-07 18:25   ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 18:42     ` Eli Zaretskii
2020-05-07 23:20     ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADJx9LdJmRQdp9517uKi2B1_EGD4=buoQ3SEoHyk3_1qto4T+w@mail.gmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=41124@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rtm443x@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).