From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: clickable text in org-mode not working
Date: Tue, 13 Nov 2012 09:50:19 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
John Kitchin wrote:
> It appears that one cannot define "clickable" text in org-mode. I was
> trying to make some text in an org-file respond to different types of
> clicking. I know that links provide some functionality for this, but
> out of curiosity I wanted to see what else I could do.
> If I run the following code on a buffer in text-mode, the first four
> characters in the buffer turn blue with a white background, they turn
> a light green when the mouse is over them, and finally a message box
> pops up when I click on the characters.
> (let ((map (make-sparse-keymap)))
> (define-key map (kbd "<down-mouse-1>")
> '(lambda() (interactive) (message-box "it works!")))
> (add-text-properties 1 5 `(keymap, map
> font-lock-face (:foreground "blue"
> :background "white")
> mouse-face highlight)))
> If I switch to org-mode, the clickability and mouse highlighting go
> away. They also do not appear when I run the function in an
> Does anyone know if there is a feature in org-mode that turns this
> off, or if there is a way to get the clickability to work? Is it
> related to having links that are clickable?
I'm not sure to understand your use case -- why do you want clickable text in
the first place (other than links)?
But, did you look at `org-add-link-type' which does allow some kind of
powerful stuff (mainly for export, but can maybe be diverted from its original
I guess you also are aware of the elisp and shell links you can already put in
any Org file, as clickable "buttons"?
prev parent reply other threads:[~2012-11-13 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:42 clickable text in org-mode not working John Kitchin
2012-11-13 8:50 ` Sebastien Vauban [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
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).