[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Blink cursor changes, possible W32 breakage.
From: |
Stefan Monnier |
Subject: |
Re: Blink cursor changes, possible W32 breakage. |
Date: |
Tue, 16 Jul 2013 18:05:23 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
>> I'm not quite sure what the point is, though. Perhaps it makes
>> sense on low-power devices? To avoid screen updates?
Not just screen updates¸ but waking up the Emacs process, which changes
the CPU's power mode, etc...
>> I think the variable should default to 0.
> To keep previous behavior by default, yes.
I don't see the point of a 0 default value. Most applications with
a blinking cursor try to stop blinking after a while, since "low power
devices" is now the norm more than the exception.
Stefan
- Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Juanma Barranquero, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Lars Magne Ingebrigtsen, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Óscar Fuentes, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Miles Bader, 2013/07/16
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Lars Magne Ingebrigtsen, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Miles Bader, 2013/07/17