From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Porting from XEmacs to Emacs: event-glyph-extent
Date: Mon, 02 Aug 2004 19:17:42 GMT [thread overview]
Message-ID: <jwvd62973nn.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.2345.1091368467.1960.help-gnu-emacs@gnu.org
> > (defun zeta-marker-activate (e)
> > (interactive "e")
> > (let ((m (event-glyph-extent e)) act)
> > (if (and m (setq act (extent-property m 'zeta-marker-action)))
> > (funcall act m)
> > (mouse-set-point e))))
> > "event-glyph-extent" seems to be problematic, at least my attempts to
> > emulate this in GNU Emacs (with constructs like "overlays-at
> > (event-start e)") failed. Is this non-trivial or do I just missing
> > something obvious?
I think that using something like (overlays-at (posn-point (event-start e)))
should be workable. It's probably easier to just put a `keymap'
property on the overlay, tho (same thing for XEmacs).
Stefan
prev parent reply other threads:[~2004-08-02 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 20:07 Porting from XEmacs to Emacs: event-glyph-extent Achim D. Brucker
2004-08-01 13:47 ` Kai Grossjohann
[not found] ` <mailman.2345.1091368467.1960.help-gnu-emacs@gnu.org>
2004-08-02 19:17 ` Stefan Monnier [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
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=jwvd62973nn.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).