[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cursor doesn't show through transparent images in emacs 22, unlike e

From: Richard Stallman
Subject: Re: cursor doesn't show through transparent images in emacs 22, unlike emacs 21
Date: Sat, 09 Sep 2006 16:45:38 -0400

    The present setting results in almost all cases in a recognizable
    cursor position (images with border 0 are possible only come Emacs

Are you saying that the problem of failing to show the cursor
only applies when the border is 0, and that that is a new feature?

In that case, let's limit my recommendations to the case when the
border is 0.  We can give :mask a different default, or make the lack
of :mask an error, only when border is 0.

      I have experienced that: trust me,
    this default _is_ worse, much much worse than the existing one.

That makes no sense at all.  The current default (in the case with
border 0) is not to show the cursor at all.  (If I'm mistaken, please
explain.)  If we change it to heuristic-mask, then usually it would
show the cursor.  That is better than not showing the cursor.

If you want me to believe this is worse, you'll have to demonstrate it
with clear explanation, not emotional upset.

    preview-latex had to go to quite disadvantageous techniques to avoid
    large-scale flashing in Emacs 21.  You'd reintroduce it.

Would you please show the justification for that claim?x

    I think it would be a mistake to abuse :mask just in order to get the
    cursor to display in a useful way.

There is no "abuse" in changing the default.

      In particular since it would mean
    that customizing the cursor type would have no effect on images, 

Why do you think it would mean that?

    > 3. If #2 is too complex to do now, maybe we should make it an error to
    >    fail to specify :mask on an image on a character in the buffer.
    >    That is simple.

    It will also break wagonloads of existing code.

I doubt it.  You've said border 0 is a new feature, so there can't
be so much existing code that uses it.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]