Re: Default value of next-error-highlight is too small

[Eli Zaretskii]

> From: "Drew Adams" <address@hidden>
> Date: Sat, 16 Sep 2006 21:01:12 -0700
> 
> On my system, with emacs -Q, if you are already looking at the position that
> is highlighted (!), and you continue to look at it while you click the grep
> link in the *grep* buffer, it is in fact possible, sometimes, to notice a
> very brief flash.

Does that mean that most of the time the highlighting is totally
invisible?  Or is the flash just too short, but visible?  These are
two different things, and your frequent use of intentionally
exaggerated metaphors doesn't help me understand whether ``invisible''
means that the highlight is actually not displayed on your system
sometimes.

In other words, I'm trying to figure out whether there's some bug
here.  If you care about this issue, please help me understand what is
involved.

> Even with the target buffer already open, and already open to the same
> target location (e.g. click the same grep line twice in a row), and even
> when I am looking straight at the target position, to see if it will flash,
> it is usually impossible to detect any flash at all. Perhaps that is due to
> the time for Emacs to move the focus to the other frame; I don't know.

What ``other frame''?  We _are_ talking about "emacs -Q", are we?  In
"emacs -Q", "M-x grep" pops up a window, not a frame.

> I hope by now I've made it clear that the flash is really imperceptible with
> emacs -Q, at least on my Windows XP box (which is a pretty fast machine with
> a gig of memory) when pop-up-frames = t.

But "emacs -Q" doesn't have pop-up-frames set to t.  Is the problem
related to this setting, or do you see the same sometimes-invisible
flash even with the default value of pop-up-frames?  If these two are
related, perhaps setting pop-up-frames to t should modify the default
of next-error-highlight.

> I don't know why you're so obstinent, Eli.

I'm no more obstinate than you are, Drew.  Richard asked me for my
opinion; if you hadn't decided to take that as an opportunity to
reiterate yours, we won't be having this prolonged and frustrating
discussion.

> Do what you want. Go ahead and configure the Emacs defaults to your
> personal preferences.

The current default wasn't set by me, I just happen to like it.