From: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook
Date: Sat, 19 Aug 2006 11:58:04 -0400 [thread overview]
Message-ID: <2cd46e7f0608190858g5865c343w455700d22dbbc91a@mail.gmail.com> (raw)
In-Reply-To: <87irko92nc.fsf@furball.mit.edu>
On 8/19/06, Chong Yidong <cyd@stupidchicken.com> wrote:
> "Ken Manheimer" <ken.manheimer@gmail.com> writes:
>
> > i see now - blink-cursor-start is called by the timer, which sets
> > blink-cursor-end on the pre-command-hook, does some cursor visibility
> > business, and then reestablishes the blink-cursor-timer.
> >
> > seems to me it would be more reliable to set the blink-cursor-timer
> > before adding blink-cursor-end to the pre-command-hook!
> >
> > i just tried making this change and removing the change from
> > blink-cursor-end (by putting revised copies of both functions in my
> > emacs rc), and the problem is not happening. i would suggest going
> > with both changes - blink-cursor-end with the condition i suggested
> > adding, and blink-cursor-start looking like:
>
> Bingo --- I think that's it. Something in your customizations must be
> causing the run-with-timer call in blink-cursor-start to signal an
> error. One possibility is an invalid `blink-cursor-interval'
> variable. Since blink-cursor-start is run from an (idle) timer,
> quitting is disabled.
>
> The question is, why did this surface only with the latest Emacs
> update?
actually, it isn't necessarily the latest emacs update, though it
probably is a one within the last several weeks. i started noticing
the problem a week or so ago, but didn't have time to investigate
until yesterday. i may not have done an update for a week or more
until before i first started seeing the problem.
--
ken
ken.manheimer@gmail.com
http://myriadicity.net
next prev parent reply other threads:[~2006-08-19 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 22:30 blink-cursor-end sometimes fails and disrupts pre-command-hook Ken Manheimer
2006-08-19 15:07 ` Chong Yidong
[not found] ` <87veoo95zy.fsf@furball.mit.edu>
[not found] ` <2cd46e7f0608190731j6247e8bbr7f7f8d1ecb6ac3ce@mail.gmail.com>
[not found] ` <87r6zc9475.fsf@furball.mit.edu>
[not found] ` <2cd46e7f0608190805x70bd8715n6f1b552d57a80a5c@mail.gmail.com>
2006-08-19 15:16 ` Chong Yidong
2006-08-19 15:58 ` Ken Manheimer [this message]
2006-08-19 16:15 ` Chong Yidong
2006-08-19 16:59 ` Ken Manheimer
2006-08-21 15:36 ` Stuart D. Herring
2006-08-20 12:05 ` Richard Stallman
2006-08-20 22:49 ` Ken Manheimer
2006-08-21 7:15 ` David Kastrup
2006-08-21 11:13 ` Richard Stallman
2006-08-21 15:31 ` Ken Manheimer
2006-08-21 17:23 ` Stuart D. Herring
2006-08-22 21:12 ` Ken Manheimer
2006-08-23 14:45 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0608190858g5865c343w455700d22dbbc91a@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.