From: Eduardo Ochs <eduardoochs@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>,
Robert Weiner <rswgnu@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Org, Hyperbole, and eev
Date: Tue, 27 Sep 2022 21:52:38 -0300 [thread overview]
Message-ID: <CADs++6iem8Xc4mtL7L8qr2x=boTSP-422PpCbq6NxCyh-FOhWA@mail.gmail.com> (raw)
In-Reply-To: <YzNyCyluMvvjCw18@protected.localdomain>
On Tue, 27 Sept 2022 at 18:59, Jean Louis <bugs@gnu.support> wrote:
> (...)
What did you do to inspect an Org link?
Here's what I just tried: I created a file /tmp/foo.org containing
" [[http://a/b/][ab]]\n" - i.e., a space, a link, and a newline -
and then I marked the whole buffer and ran `M-1 M-x find-eregionpp'
on it to pretty-print the region as a string with properties, with
the flag `print-circle' turned on... see:
(find-efunction 'find-eregionpp)
http://angg.twu.net/eev-current/eev-blinks.el.html#find-eregionpp
Apparently Org divided that file into 8 subsegments, each one with
different text properties... and they mention all these keywords:
face follow-link font-lock-multiline fontified help-echo highlight
htmlize-link intangible invisible keymap mouse-2 mouse-3 mouse-face
org-find-file-at-mouse org-link org-linked-text org-open-at-mouse
rear-nonsticky
I _think_ that it should be possible to make this
⟦ (hyperscope-wrap-eev "Hyperbole DEMO file" '(find-hyperbolefile "DEMO")) ⟧
into a kind of button using only three subregions with different text
properties: a first invisible region with this,
⟦ (hyperscope-wrap-eev "
then a visible region with "button actions", with this,
Hyperbole DEMO file
and then another invisible region with:
" '(find-hyperbolefile "DEMO")) ⟧
Let me play with this idea for a bit - I'll send some code as soon as
possible!
Cheers =),
Eduardo
next prev parent reply other threads:[~2022-09-28 0:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:56 Org, Hyperbole, and eev Eduardo Ochs
2022-06-26 16:28 ` Robert Weiner
2022-06-26 17:51 ` Eduardo Ochs
2022-06-26 18:23 ` Robert Weiner
2022-06-26 19:45 ` Eduardo Ochs
2022-06-26 20:23 ` Robert Weiner
2022-06-26 23:25 ` Eduardo Ochs
2022-06-27 0:49 ` Robert Weiner
2022-06-27 3:48 ` Eduardo Ochs
2022-06-27 4:11 ` Robert Weiner
2022-06-28 4:43 ` Eduardo Ochs
2022-09-27 15:10 ` Jean Louis
2022-09-27 16:22 ` Eduardo Ochs
2022-09-27 21:16 ` Jean Louis
2022-09-27 21:58 ` Jean Louis
2022-09-28 0:52 ` Eduardo Ochs [this message]
2022-09-28 6:04 ` Jean Louis
2022-09-28 10:15 ` Eduardo Ochs
2022-09-29 9:22 ` Jean Louis
2022-10-08 0:28 ` Eduardo Ochs
2022-10-08 1:25 ` Jean Louis
2022-10-11 2:42 ` Robert Weiner
2022-10-11 4:59 ` Jean Louis
2022-09-29 9:42 ` Jean Louis
2022-09-29 11:55 ` Quiliro Ordóñez
2022-09-28 3:52 ` Ihor Radchenko
2022-09-28 9:16 ` Jean Louis
2022-09-29 4:07 ` Ihor Radchenko
2022-09-29 9:59 ` Jean Louis
2022-06-28 4:48 ` Eduardo Ochs
2022-06-28 6:26 ` Robert Weiner
2022-09-27 14:43 ` Jean Louis
2022-09-27 14:16 ` Jean Louis
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADs++6iem8Xc4mtL7L8qr2x=boTSP-422PpCbq6NxCyh-FOhWA@mail.gmail.com' \
--to=eduardoochs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rswgnu@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).