From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Info mutilates user overlays.
Date: 01 Oct 2003 15:54:34 -0400 [thread overview]
Message-ID: <jwvfzicd9ix.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <200310011914.h91JEZU01874@raven.dms.auburn.edu>
> In the very concrete case at hand, I was highlighting regions with
> non-nil `help-echo' property, using overlays with background color.
> The code works for properties other than help-echo too. Again, in the
> concrete case at hand, I was doing it explicitly to check whether my
> code would work in *info* buffers. But I have used overlays
> personally for a variety of reasons, for instance, to highlight for
Please: *how* do you highlight ?
Did you create some commands similar to what is available under M-g
but using overlays, or do you add the overlay from a hook, or ...
I mean, your example using M-: (make-overlay foo bar) RET and stuff
like that, I don't really care about the interaction with info.
overlays and text-properties should basically never be added without keeping
track of them and deleting or using them later on. Kind of like drawing
in GUIs: you have to keep track of what you've drawn to potentially update
it if the window is resized, hidden, deiconified, ...
Stefan
next prev parent reply other threads:[~2003-10-01 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 2:16 Info mutilates user overlays Luc Teirlinck
2003-10-01 2:26 ` Miles Bader
2003-10-01 2:40 ` Luc Teirlinck
2003-10-01 4:00 ` Luc Teirlinck
2003-10-01 4:37 ` Miles Bader
2003-10-01 12:22 ` Stefan Monnier
2003-10-01 14:49 ` Luc Teirlinck
2003-10-01 17:33 ` Stefan Monnier
2003-10-01 18:49 ` Luc Teirlinck
2003-10-01 20:00 ` Stefan Monnier
2003-10-02 13:45 ` Richard Stallman
2003-10-01 19:14 ` Luc Teirlinck
2003-10-01 19:54 ` Stefan Monnier [this message]
2003-10-01 21:11 ` Luc Teirlinck
2003-10-01 23:18 ` Luc Teirlinck
2003-10-02 0:38 ` Miles Bader
2003-10-01 15:10 ` Luc Teirlinck
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=jwvfzicd9ix.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.