unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Daniel Brockman <daniel@brockman.se>
Cc: emacs-devel@gnu.org
Subject: Re: Invisibility bug: `invisible' vs `display'
Date: Tue, 13 Feb 2007 08:13:31 +0100	[thread overview]
Message-ID: <861wkucyxw.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87hctq6eyd.fsf@wigwam.brockman.se> (Daniel Brockman's message of "Tue\, 13 Feb 2007 02\:09\:30 +0100")

Daniel Brockman <daniel@brockman.se> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> Daniel Brockman <daniel@brockman.se> writes:
>>
>>> The `*' and `?' characters have `invisibile' properties
>>> with a value of `t', so I expect to see none of them.
>>>
>>> The `?' characters all have `display' properties with a
>>> value of "!" (one of them has "$" instead, for clarity).
>>> This, I believe, _should_ be irrelevant.
>>
>> The `display' text property overrides `invisible'.
>
> If that were true, then all the `?' characters should
> display as exclamation marks, but they don't, so the
> `display' text property does not override `invisible'.
>
> This still looks like a bug to me.
>
> Let me state again what I see:  The `display' property
> overrides `invisible' if and only if the previous character
> is visible.  How is this reasonable or useful in any way?

When folding stretches of code, it does not make sense to have images
in between cluster all together and stick out in spite of the
invisibility of the region.

I am not saying that the current behavior is perfect, but it would
seem you would want to replace it with something that can cause quite
a bit of trouble, and I don't think we have the time to shake out all
repercussions before the release.

-- 
David Kastrup

  reply	other threads:[~2007-02-13  7:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 19:00 Invisibility bug: `invisible' vs `display' Daniel Brockman
2007-02-12 20:39 ` Daniel Brockman
2007-02-12 23:46 ` Chong Yidong
2007-02-13  1:09   ` Daniel Brockman
2007-02-13  7:13     ` David Kastrup [this message]
2007-02-13 14:59       ` Daniel Brockman
2007-02-22  2:57         ` Daniel Brockman
2007-02-22 11:27           ` Kim F. Storm
2007-02-22 11:42             ` David Kastrup
2007-02-22 13:22               ` Daniel Brockman
2007-02-22 13:38                 ` David Kastrup
2007-02-22 14:15                   ` Daniel Brockman
2007-02-22 17:19                     ` Johan Bockgård
2007-02-22 17:37                     ` David Kastrup
2007-02-22 20:39                       ` Daniel Brockman
2007-02-22 21:00                         ` David Kastrup
2007-02-22 21:23                           ` Daniel Brockman
2007-02-22 21:51                             ` David Kastrup
2007-02-23 13:23                               ` Daniel Brockman
2007-02-22 17:08               ` Kim F. Storm

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861wkucyxw.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=daniel@brockman.se \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).