[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Blink cursor changes, possible W32 breakage.
From: |
Lars Magne Ingebrigtsen |
Subject: |
Re: Blink cursor changes, possible W32 breakage. |
Date: |
Tue, 16 Jul 2013 20:02:44 +0200 |
User-agent: |
Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
>> Just a heads up, I changed blink cursor in two ways, one is that it
>> stops blinking after blinking
>> blink-cursor-blinks number of times (10 by default), as inspired by
>> gnome-terminal. Also, timers are stopped when no blinking occurs.
>
> Why do we want that? Is there a way to get previous behavior?
Set that variable to 0. I'm not quite sure what the point is, though.
Perhaps it makes sense on low-power devices? To avoid screen updates?
I think the variable should default to 0.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
- 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.,
Lars Magne Ingebrigtsen <=
- 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