emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 27 Sep 2022 18:10:25 +0300	[thread overview]
Message-ID: <YzMSYSnELX52p0KF@protected.localdomain> (raw)
In-Reply-To: <CADs++6i5Ejv9URXmuPSQRgPrDz7mLrHB3gJwznzCKdHW37hSvQ@mail.gmail.com>

* Eduardo Ochs <eduardoochs@gmail.com> [2022-06-28 09:54]:
> with hyperbole-mode active... my notes are here - for the sake of
> completeness; I don't expect them to be readable -
> 
>   (code-c-d "hyperbole" "~/.emacs.d/elpa/hyperbole-8.0.0/")
>   (require 'hyperbole)
>   (hyperbole-mode 0)
>   (find-hyperbolefile "DEMO")
>   (find-hyperbolefile "DEMO" "Action Key is {M-RET}")

I like that link above. Though I would like to see it a "Action Key is
{M-RET}" so is there a way or some general font lock package that can
make links similar like in Org mode but for all kinds of links, so
that links is hidden and name shown?

I would need that. This is great link:

(find-hyperbolefile "DEMO" "Action Key is {M-RET}")

But would not be better to have something like:

"Hyperbole's __action key is M-RET__ so try it out" without the actual
link there?

I tend towards interpolation, so that links like ⟦ (link 123) ⟧ are
just numbers, but shown as their names as the number is related to
name in the database.

Do you have way to go for something like that?

>   (find-efunction 'action-key-internal)
>   (find-efunction 'hkey-execute)
>   (find-efunction 'hkey-execute "hkey-alist")
>   (find-evardescr 'hkey-alist)

The way how you have listed it above is insightful. I get the
instructions and I get the point. It is way of teaching.

It can be done by any means, Org, eev, Hyperbole. Though one so
important part is missing, the presentation of links. It is cryptic.

Instead of:

>   (find-evardescr 'hkey-alist)

I would like to see visually:

"Description of Emacs Lisp function `hkey-alist'"

What is really good is accessibility, I can click M-e or M-k to go
back, great. That is power. Similarly in Hyperbole, it is M-RET.

>   (find-eppp       hkey-alist)
>   (find-eppp       hkey-alist "(hbut:at-p)")
>   (find-evariable 'hkey-alist)
>   (find-evariable 'hkey-alist "If on a Hyperbole button")
>   (find-evariable 'hkey-alist "If on a Hyperbole button" "(hbut:at-p)")
>   (find-efunction 'hbut:at-p)

There must be some way of quickly generating above links, do you have
such?

Let us say you are in buffer A, you go to Emacs Lisp file at line 134, and
you just press there a key, and link is inserted in buffer A, leading
to Emacs Lisp file at line 134, you have that?

>     (eek "2*<down> C-e <left>")
>     (eek   "<down> C-e <left> M-RET")
>     <insert "foo">

Now you got it. I was following 90%

> Anyway, we are clearly using different notions of simplicity - see:
> 
>   https://lists.gnu.org/archive/html/hyperbole-users/2020-09/msg00013.html
> 
> and I find it enviable that you can have that kind of complexity under
> the hood and still have lots of users that agree that Hyperbole is
> "simple"...

It is because users do not care what is under the hood...

But now we have various information management systems, and I would
like to get general Org-like presentation for any kind of links.

Does such package exist already? Do we really need to make it new for
each package?

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/


  reply	other threads:[~2022-09-27 16:48 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 [this message]
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
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=YzMSYSnELX52p0KF@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).