From: Ralf Angeli <angeli@iwi.uni-sb.de>
Subject: Re: [reveal-mode] Hiding short expressions
Date: Tue, 06 Jul 2004 21:34:55 +0200 [thread overview]
Message-ID: <cceurr$gk3$1@sea.gmane.org> (raw)
In-Reply-To: 40EAF881.8050404@yahoo.com
* Kevin Rodgers (2004-07-06) writes:
> Ralf Angeli wrote:
> > * Stefan (2004-07-03) writes:
> >>Indeed, I think it should be decided on an overlay basis rather
> >>than for the whole buffer. But I don't like forcing an
> >>indirection through `category', so I'd just do (overlay-get ol
> >>'reveal-close) which also obeys the `category' prop if present.
> >
> > This would be fine with me. I'd use the symbol 'reveal-on-cursor-out,
> > though.
>
> Emacs generally uses the term point instead of cursor, e.g. the
> point-entered and point-left text properties. So how about
> reveal-point-left or reveal-when-point-left?
One remark: If I am the only one who requested/needed such a feature,
please don't bother anymore.
While I was working with reveal.el I found that I cannot use the
'invisible property of overlays which has to be set with reveal.el.
If there are invisible overlays, `move-to-column' will not look at the
content covered by the overlay but at the overlay itself. Now when
you fill a paragraph with short overlays covering some longer text
passages and delete the overlays afterwards, there will most likely be
overfull lines. Therefore I cannot use reveal.el in its totality
anyway and I am not in need of it testing for a special property
anymore.
--
Ralf
next prev parent reply other threads:[~2004-07-06 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 21:05 [reveal-mode] Hiding short expressions Ralf Angeli
2004-07-02 21:37 ` Stefan
2004-07-03 12:07 ` Ralf Angeli
2004-07-03 17:01 ` Stefan
2004-07-03 18:03 ` Ralf Angeli
2004-07-03 18:56 ` Stefan
2004-07-03 19:26 ` Ralf Angeli
2004-07-06 19:07 ` Kevin Rodgers
2004-07-06 19:34 ` Ralf Angeli [this message]
2004-07-06 19:56 ` David Kastrup
2004-07-07 13:32 ` Stefan
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='cceurr$gk3$1@sea.gmane.org' \
--to=angeli@iwi.uni-sb.de \
/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.