emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Eev-wconfig.el etc etc, or: "Exercise: Learn Org!"
Date: Fri, 27 May 2022 22:30:48 +0800	[thread overview]
Message-ID: <87h75b59pj.fsf@localhost> (raw)
In-Reply-To: <CADs++6g_z1K0ng+-Mp=_gxVRhOCk8=Abu43t5WRaDB2vc9Wztg@mail.gmail.com>

Eduardo Ochs <eduardoochs@gmail.com> writes:

> I made a video that is mainly for people who are new to Emacs and who
> are using M$ Windows, and it ends with an exercise that is roughly
> this: "...now download a .zip file with Rainer Koenig's videos from
> <http://angg.twu.net/eev-wconfig.html#learn-org>, unpack it somewhere,
> and use eev to create an index of the video that you've watched, with
> pointers to the parts that you will need to re-watch many times"...

You are discussing too many things at once in one video.

What is the main point you want to explain in the video? How to
download, watch, and annotate a series of videos? If so, you only talk
about it in the last minutes of the presentation.

Also, do you expect people new to emacs understand all the
(commmand args) staff?

I still fail to understand what is the advantage of eev compared to Org
or Hyperbole (which also provides context-free actionable links).
You argue that Org is a "black box", but your code is also a black box
in a sense that one needs to read the "wconfig" files (AFAIU). How is it
different compared to Org written in Elisp following the usual
documentation conventions described in the Elisp manual?

I recommend recording a much shorted video demonstrating a singe task
you perform using eev. No need to side track explaining Elisp syntax. No
need to show troubleshooting. No need to show things users "are not
supposed to understand". No need to show initial configuration with all
possible caveats.


  reply	other threads:[~2022-05-27 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 15:52 Eev-wconfig.el etc etc, or: "Exercise: Learn Org!" Eduardo Ochs
2022-05-27 14:30 ` Ihor Radchenko [this message]
2022-05-27 22:36   ` Eduardo Ochs
2022-05-28  4:53     ` Ihor Radchenko
2022-05-28  7:06       ` Eduardo Ochs
2022-05-30  3:20         ` Ihor Radchenko
2022-05-30  5:47           ` Eduardo Ochs

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:

  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=87h75b59pj.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=eduardoochs@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).