From: Eduardo Ochs <eduardoochs@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Org, Hyperbole, and eev
Date: Sun, 26 Jun 2022 12:56:25 -0300 [thread overview]
Message-ID: <CADs++6j48VrYTfcs7mVdU2NBOybnZ6JzaDQcHkgTtfve1W+o8Q@mail.gmail.com> (raw)
Hi all,
this message is slightly off-topic, and a shameless plug...
Eev can do many things that Org and Hyperbole and do, but it makes
very little sense to people who can play the role of "users" well, in
the sense of people who can "use" Emacs packages without looking at
the elisp source and hacking it, i.e.: reading the source of the
package, inspecting and understanding its data structures, and
creating sexps that call the package's functions directly...
Eev still has a couple of parts whose data structures are hard to
inspect. I don't regard these parts as "real" bugs, but I do regard
them as hugely embarassing - and I have just fixed one of them:
`find-here-links', that is explained in this section of the main
tutorial,
http://angg.twu.net/eev-intros/find-eev-quick-intro.html#4.1
and in this other tutorial:
http://angg.twu.net/eev-intros/find-here-links-intro.html
The way to run `find-here-links' in debug mode is explained here,
http://angg.twu.net/eev-current/eev-hlinks.el.html
in the second part of the ";;; Commentary:" at the top - look for
"Debug mode".
As I mentioned in the other thread
https://lists.gnu.org/archive/html/emacs-orgmode/2022-06/msg00524.html
https://lists.gnu.org/archive/html/emacs-orgmode/2022-06/threads.html#00524
and in these pages,
http://angg.twu.net/2021-org-for-non-users.html
http://angg.twu.net/find-elisp-intro.html
http://angg.twu.net/eev-wconfig.html
http://angg.twu.net/hyperbole.html
I find Org and Hyperbole difficult mainly because they are
hacker-unfriendly. It _may be_ that some of the people who said that
they find Org very hard in this thread
https://lists.gnu.org/archive/html/emacs-devel/2022-06/threads.html#00186
would also benefit from a bit more of hacker-friendliness... and so it
would be great if more ideas could flow between Org, eev, and Hyperbole.
Cheers and sorry the noise =P,
Eduardo Ochs
http://angg.twu.net/#eev
next reply other threads:[~2022-06-26 15:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:56 Eduardo Ochs [this message]
2022-06-26 16:28 ` Org, Hyperbole, and eev 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
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++6j48VrYTfcs7mVdU2NBOybnZ6JzaDQcHkgTtfve1W+o8Q@mail.gmail.com \
--to=eduardoochs@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).