emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#18856: closed (24.4; *grep* output buffer not gett


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#18856: closed (24.4; *grep* output buffer not getting fontified when jit-lock-defer-time is used)
Date: Sat, 01 Nov 2014 14:25:02 +0000

Your message dated Sat, 01 Nov 2014 16:24:27 +0200
with message-id <address@hidden>
and subject line Re: bug#18856: 24.4; *grep* output buffer not getting 
fontified when jit-lock-defer-time       is used
has caused the debbugs.gnu.org bug report #18856,
regarding 24.4; *grep* output buffer not getting fontified when 
jit-lock-defer-time is used
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18856: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18856
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.4; *grep* output buffer not getting fontified when jit-lock-defer-time is used Date: Mon, 27 Oct 2014 20:33:48 +0100
Recipe:

* emacs -Q

* M-x set-variable RET jit-lock-defer-time RET 0.05 RET

* Call M-x rgrep and search for some string in some directory

You should be able to see that the *grep* buffer capturing grep's output
is not getting fontified until you hit a key. I would expect that it
gets fontified automatically when new output arrives.

Note that the same problem happens for other buffers which capture
process output, like compilation buffers.

-David



--- End Message ---
--- Begin Message --- Subject: Re: bug#18856: 24.4; *grep* output buffer not getting fontified when jit-lock-defer-time is used Date: Sat, 01 Nov 2014 16:24:27 +0200
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden
> Date: Wed, 29 Oct 2014 18:23:50 -0400
> 
> >  #define READABLE_EVENTS_FILTER_EVENTS              (1 << 1)
> >  #define READABLE_EVENTS_IGNORE_SQUEEZABLES (1 << 2)
> > +#define READABLE_EVENTS_IGNORE_BUFFER_SWITCH       (1 << 3)
> 
> I think we should not need a new such setting, and can simply use
> READABLE_EVENTS_FILTER_EVENTS (i.e. handle BUFFER_SWITCH_EVENT like we
> handle FOCUS_IN, and I'm surprised there aren't more in that set of "not
> really input" events).

I made the requested change in keyboard.c, and committed both parts,
with the compile.el part on the emacs-24 branch.

Closing.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]