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: Mon, 30 May 2022 11:20:46 +0800	[thread overview]
Message-ID: <87o7zfogdt.fsf@localhost> (raw)
In-Reply-To: <CADs++6jhZabX3kGWdNhVvpQ-Tbb+B8U3kjP2Lxpz9Y_WNqVnwg@mail.gmail.com>

Eduardo Ochs <eduardoochs@gmail.com> writes:

> I think that you are underestimating how alien eev is for most people.
> Let me suppose that what you mean by your comments is this:
>   "I've spent N minutes watching this video - for N big - and I feel
>    that I've learned very little! What is the best way to learn a lot
>    of eev in M minutes, for M very small?"
> then the answer is: follow the main tutorial, that is here:
>    http://angg.twu.net/eev-intros/find-eev-quick-intro.html

To clarify, I did not expect to learn evv from the video you provided.
However, I did expect to learn things proportionally to the video
length. That way, the video efficiency is pretty low. The video itself
can certainly be improved - the problem is not with eev itself, but
rather with the way you present things.

Note that eev is not actually very alien. Knowing the concept of Org
links, eev is pretty trivial. At least the basics concepts are not hard
to grasp.

> Anyway, tomorrow I will meet with a group of three or four students
> that are interested in learning Emacs and eev. They use Windows and
> they have never used Emacs before, so we probably won't be able to do
> much of this exercise:
>   http://angg.twu.net/eev-wconfig.html#learn-org

It would be interesting to hear about the outcome and the student


  reply	other threads:[~2022-05-30  3:21 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
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 [this message]
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=87o7zfogdt.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).