[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Blink cursor changes, possible W32 breakage.
From: |
martin rudalics |
Subject: |
Re: Blink cursor changes, possible W32 breakage. |
Date: |
Sun, 21 Jul 2013 11:20:30 +0200 |
> ... they're not activated unless the user asks for
> it explicitly.
`jit-lock-context-timer' is activated here though I never asked for it
"explicitly".
> Also jit-lock-stealth used to be enabled by default but
> was disabled because too many people found it problematic, so only those
> people who don't care about high/excessive background CPU usage will
> have it enabled.
I'm too silly to understand: Don't we talk about the case where Emacs
remains idle? Shouldn't these timers trigger once only after that
happened?
martin
- Re: Blink cursor changes, possible W32 breakage., (continued)
- Re: Blink cursor changes, possible W32 breakage., Lars Magne Ingebrigtsen, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/21
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/21
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/21
- Re: Blink cursor changes, possible W32 breakage.,
martin rudalics <=
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/21