Eev and Hyperbole

1. 2019 and 2020

Long story short: after my presentation on eev at the EmacsConf2019 in april/2019 the author of Hyperbole sent this to me as an "issue" on github; I moved the discussion to the Hyperbole mailing list, and started to work on a kind of bridge between eev and Hyperbole.

My e-scripts on Hyperbole are here.
Links to my messages on the mailing list: 2019-04, 2020-09.

After this thread in the mailing list I decided that I was burnt out. I sent this message to the thread on github issues, and bye-bye Hyperbole.

2. 2022

In june/2022 I said in the Org mailing list (here and here) that after trying Hyperbole for some time - and failing miserably - I ended up with the impression that Hyperbole is meant to be "used", not to be "hacked". Then the author of Hyperbole joined the Org mailing list, and we discussed Hyperbole versus eev in this other thread. I saved copies of my best messages in my hyperbole.e:

524 1) I failed miserably, 2) to be used, not hacked
738 A debugging mode for find-here-links
742 several similar examples close to one another
750 let me propose three tasks
757 helping people with the "non-abstract parts" (see also this)
801 what happens when we type M-RET
802 about tests in comments

3. 2024

In 2024 I saw - after many chats on the #emacs IRC channel - that my frustration with Hyperbole had many technical points that were worth discussing in public. Long story short, in sep/2020 rsw told me this:

I really, really recommend that you try to use Hyperbole without initially mixing it with eev, as I think you will find that Hyperbole already contains much of what you need to simplify eev and tie it to a broader Emacs ecosystem.

and my long answer is here (and here); his original e-mail is here.

eternal-hate