unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: Daniel Brockman <daniel@brockman.se>, emacs-devel@gnu.org
Subject: Re: Invisibility bug: `invisible' vs `display'
Date: Thu, 22 Feb 2007 12:42:12 +0100	[thread overview]
Message-ID: <863b4yxvu3.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <m37iuaxwje.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Thu\, 22 Feb 2007 12\:27\:01 +0100")

storm@cua.dk (Kim F. Storm) writes:

> Daniel Brockman <daniel@brockman.se> writes:
>
>> 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.
>
> That is clearly a bug.
>
>> This patch fixes the problem for me.
>
> Thank you.
>
> Mixing invisible and display properties -- with the desire to actually
> get the effects of the display property looks very obscure to me, and
> cannot image that any code is actually relying on such functionality.
>
> I think the change is safe, so I installed it.

Sigh.  If you use preview-latex on material where _some_ of it is made
invisible using TeX-fold-mode, the desired outcome will be to get the
display, and get it once only.

I can't vouch for the patch being either a step in the right or wrong
direction.

But I'd clearly like to see fewer "I think it should work and can't
imagine anybody actually using it, anyway" patches at this point in
the game.

If we don't have the time or resources of assessing the ramifications
of a patch, there is really little incentive to not rather try them
out in the course of version 22.2.

-- 
David Kastrup

  reply	other threads:[~2007-02-22 11:42 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
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 [this message]
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=863b4yxvu3.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=daniel@brockman.se \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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).