Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Masatake YAMATO <jet@gyve.org>,
	mi-ew3m@imarko.dhs.org, matt@stchem.bham.ac.uk,
	emacs-w3m@namazu.org
Subject: [emacs-w3m:06591] enabling evaporation of overlays
Date: Thu, 08 Apr 2004 11:44:55 +0900	[thread overview]
Message-ID: <b9y1xmzdw7s.fsf@jpl.org> (raw)
In-Reply-To: <b9ybrm455r2.fsf@jpl.org>

Hi,

This message is continued from the following thread:

http://thread.gmane.org/n05yv0h3.fsf@ID-23066.news.dfncis.de

>>>>> In [emacs-w3m : No.06589] Katsumi Yamaoka wrote:

> I also got a report from Hiroshi Fujishima yesterday that there
> is a problem in Gnus.  When a user types the `t' key in the
> summary buffer, mouse-face spreads over the whole article header.
> It is required that the value for gnus-treat-buttonize-head is
> `head' (which is the default).  I haven't investigated it yet,
> though.

The problem arises since it is the middle of the development of
overlay functions in the Emacs CVS head.  It can be fixed by the
following code:

(eval-after-load "gnus"
  '(progn
     (defun gnus-make-overlay (&rest args) "\
Run `make-overlay' and enable the `evaporate' property on overlay."
       (let ((overlay (apply 'make-overlay args)))
	 (overlay-put overlay 'evaporate t)
	 overlay))
     (require 'byte-comp)
     (byte-compile 'gnus-make-overlay)))

It is useful that all overlays made by Gnus will be vanished
when `erase-buffer' is performed.  However, currently I don't
want to install it to Gnus CVS.  Because it doesn't affect
overlays made for widget buttons and we are unable to abolish
the gnus-kill-all-overlays function.  Furthermore, I heard
Masatake YAMATO is planning to enable evaporation of all
overlays by default.  All problems will be solved if it is
realized.

Regards,
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



       reply	other threads:[~2004-04-08  2:44 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         ` Katsumi Yamaoka [this message]
2004-04-08  3:57           ` [emacs-w3m:06592] " Masatake YAMATO
2004-04-08  4:06           ` Fwd: " Katsumi Yamaoka
2004-04-08  4:17           ` [emacs-w3m:06593] " Masatake YAMATO

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=b9y1xmzdw7s.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=emacs-w3m@namazu.org \
    --cc=jet@gyve.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).