From: Jean Louis <bugs@gnu.support>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Robert Weiner <rswgnu@gmail.com>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Org, Hyperbole, and eev
Date: Wed, 28 Sep 2022 00:16:30 +0300 [thread overview]
Message-ID: <YzNoLisbcKXZdFLI@protected.localdomain> (raw)
In-Reply-To: <CADs++6jX=-fBwNJ5P7o2xXhJDeNK2YBL+baJ5MWEFB-7HbrXoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2827 bytes --]
* Eduardo Ochs <eduardoochs@gmail.com> [2022-09-27 20:22]:
> On Tue, 27 Sept 2022 at 12:11, Jean Louis <bugs@gnu.support> wrote:
> > (...)
>
> Hi Jean Louis,
>
> > Instead of:
> >
> > > (find-evardescr 'hkey-alist)
> >
> > I would like to see visually:
> >
> > "Description of Emacs Lisp function `hkey-alist'"
>
> In cases like that there would be some key sequence that parses the
> text and the text properties around point and produces a sexp that
> goes to the target of the link when executed. Let me call that sexp
> the "back-end" of the link.
I was thinking only the display would be different while link would be
hidden. Just like Org links.
> I did play with some ways to buttonize back-end sexps, and with some
> ways to parse the text around point to generate these back-end sexps,
> but I didn't find those things much fun, and in all the cases I ended
> up finding nice ways to solve my problems with just explicit sexps,
Yes, you solved problem of hyperlinking, but not of
presentation. While Org has solved it for presentation very well.
I wish to create meta links. Today I have tried figuring out how Org
link work, but I am overwhelmed.
I like to have main source file which can be then converted to many
formats, that way is more creative.
Source file can be viewed or edited, when viewed, it would show links
as presented names. When edited, it could show source links.
But when exported, only names would be exported.
eev links I cannot export into text to be presentable or
understandable.
Right now I have working system where I can insert ⟦ (anything) ⟧ and
in representation it will be shown whatever the function returns
back. It is not a clickable link, rather automatically interpolated
link and displayed as such, but not editable directly.
I have got it working this way:
(defun hyperscope-wrap-eev (name &rest body)
(with-temp-buffer
(insert-text-button name
'action `(lambda (b) ,@body))
(buffer-string)))
Source:
⟦ (hyperscope-wrap-eev "Hyperbole DEMO file" '(find-hyperbolefile "DEMO")) ⟧
Visual representation:
Hyperbole DEMO file
Using enter on the link brings me to DEMO file, I can add mouse later.
It uses RCD Template Interpolation System for Emacs:
https://hyperscope.link/3/7/1/3/3/RCD-Template-Interpolation-System-for-Emacs.html
I could shorten it to:
⟦ (rcd-eev "Hyperbole DEMO file" '(find-hyperbolefile "DEMO")) ⟧
and I guess I could that way insert any of your links. 👀
See attached frameshot how it looks like.
Because you are generating buffers on the fly, your, mine and
Hyperbole system would benefit of visual representation of hyperlinks
just as Org does it.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
[-- Attachment #2: Screenshot-2022-09-28-00-11-30-710565620.png --]
[-- Type: image/png, Size: 99151 bytes --]
next prev parent reply other threads:[~2022-09-27 21:21 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 [this message]
2022-09-27 21:58 ` Jean Louis
2022-09-28 0:52 ` Eduardo Ochs
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=YzNoLisbcKXZdFLI@protected.localdomain \
--to=bugs@gnu.support \
--cc=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).