Gnus development mailing list
 help / color / mirror / Atom feed
From: Masatake YAMATO <jet@gyve.org>
Cc: ding@gnus.org, mi-ew3m@imarko.dhs.org, matt@stchem.bham.ac.uk
Subject: [emacs-w3m:06593] Re: enabling evaporation of overlays
Date: Thu, 08 Apr 2004 13:17:49 +0900 (JST)	[thread overview]
Message-ID: <20040408.131749.80361414.jet@gyve.org> (raw)
In-Reply-To: <b9y1xmzdw7s.fsf@jpl.org>

Setting t to evaporate by default is rejected but RMS write 
this should be done by each application. After thinking I agree
with this. I start to discuss abut how to deal evaporate of widget's
overlay in emacs-devel.

RMS wrote in emacs-devel:
	I'd just like to add that mh-e also has this problem when displaying
	mime buttons and parts.  It was fixed by setting the overlay 'evaporate
	property to t.

	In any case it seems like a change for the better.  Previously all the
	gui-button faces would shrink to zero-length overlays and remain there,
	invisible, when the buffer contents were deleted and new contents
	inserted.  I now see that a lot of overlays accumulated after may reuses
	of the same buffer.

    It sounds like THESE overlays should be set to evaporate.
    But I think MH-E should do that.  I cc'd the MH-E maintainer.


Masatake YAMATO



      parent reply	other threads:[~2004-04-08  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b9y1xn3w0q5.fsf@jpl.org>
     [not found] ` <m3hdvxdben.fsf@zsu.sush.org>
     [not found]   ` <b9yn05obszp.fsf@jpl.org>
     [not found]     ` <20040407.205642.89144777.jet@gyve.org>
     [not found]       ` <b9ybrm455r2.fsf@jpl.org>
2004-04-08  2:44         ` [emacs-w3m:06591] " Katsumi Yamaoka
2004-04-08  3:57           ` [emacs-w3m:06592] " Masatake YAMATO
2004-04-08  4:06           ` Fwd: " Katsumi Yamaoka
2004-04-08  4:17           ` Masatake YAMATO [this message]

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=20040408.131749.80361414.jet@gyve.org \
    --to=jet@gyve.org \
    --cc=ding@gnus.org \
    --cc=emacs-w3m@namazu.org \
    --cc=matt@stchem.bham.ac.uk \
    --cc=mi-ew3m@imarko.dhs.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.
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 NNTP newsgroup(s).