emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: andre duarte bueno <bueno@lenep.uenf.br>, emacs-orgmode@gnu.org
Subject: Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org,
Date: Mon, 2 Jan 2023 02:58:45 -0300	[thread overview]
Message-ID: <CADs++6gUozQ8bMeqftY49cqyJWRwrscVHgNEjZCb89DyV9svEQ@mail.gmail.com> (raw)
In-Reply-To: <877cy673ot.fsf@localhost>

On Sun, 1 Jan 2023 at 11:02, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Eduardo Ochs <eduardoochs@gmail.com> writes:
>
> > My conclusion was that Org is much harder to learn than I thought.
> > It's easy to learn if:
> >
> >   1) you're a "user", or
> >   2) you know a lot about debugging Emacs, or
> >   3) the developers like your questions.
>
> I hope that (3) is not your experience with Org ML. If it is, I'd rather
> say "developers understand questions". At least from my perspective.
> Your approach is rather unusual for me, making it difficult to follow
> even after detailed explanations.

Hi Ihor,

(3) _is_ my experience with the Org mailing list.

What I meant by "the developers like your questions" was roughly:
"recognizing that that person deserves help, and giving him tools that
would let him solve his problems in hours instead of in months or
years".

For example, in this thread

https://lists.gnu.org/archive/html/emacs-orgmode/2021-12/msg00674.html

no one considered that if I was asking that then maybe it would be a
good idea to make `org-export-dispatch' more hackeable by beginners...

For example, someone could have said "can you try this? Copy that
function to other file, replace its lines foo and bar by the lines
plic and bletch, and use the ideas in these two blog posts to debug
and inspect its data structures"... but no, that didn't happen - I've
asked lots of technical questions here over the years and never got
detailed answers like that, only answers whose technical details _were
kept as short as possible_, and whose explanations were much closer to
"in English" than to "in Lisp".

A few days ago I added subtitles to my video about "Org for
Non-Users". The links are here,

  http://angg.twu.net/2021-org-for-non-users.html

and some people will prefer to just read this:

  http://angg.twu.net/eev-videos/2021-org-for-non-users.vtt
  http://angg.twu.net/SUBTITLES/2021-org-for-non-users.lua.html

It explains with examples how a "non-user" thinks, and it shows what I
mean by "explanations in Lisp".

  Cheers =/,
    Eduardo


  reply	other threads:[~2023-01-02  5:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 20:57 Problems with C-c C-e file.org andre duarte bueno
2022-12-18 14:55 ` Ihor Radchenko
2022-12-19 21:10   ` Export Org with Org concept -- Re: Problems with C-c C-e file.org, Jean Louis
2022-12-25 12:06     ` Ihor Radchenko
2022-12-25 15:43       ` Jean Louis
2022-12-26 10:04         ` Ihor Radchenko
2022-12-26 15:58           ` Jean Louis
2022-12-27 10:46             ` Ihor Radchenko
2022-12-31  1:08     ` Eduardo Ochs
2022-12-31  6:19       ` Jean Louis
2023-01-01 14:02       ` Ihor Radchenko
2023-01-02  5:58         ` Eduardo Ochs [this message]
2023-01-02 11:07           ` Jean Louis
2023-01-03  9:48           ` Ihor Radchenko
2023-01-03 10:01             ` Eduardo Ochs
2023-01-03 12:15               ` Max Nikulin
2023-01-03 12:36                 ` Eduardo Ochs
2023-01-05 11:07                   ` Ihor Radchenko
2023-01-05 14:41                     ` Alain.Cochard
2023-01-05 15:00                       ` Max Nikulin
2023-01-05 15:18                         ` Alain.Cochard
2023-01-05 20:37                           ` Eduardo Ochs
2023-01-05 18:50                       ` Jean Louis
2023-01-05 15:43                     ` Eduardo Ochs
2023-01-04 11:08                 ` Jean Louis
2023-01-05 11:16                   ` Ihor Radchenko
2023-01-05 19:19                     ` Jean Louis
2023-01-06  3:51                       ` Max Nikulin
2023-01-07  9:04                       ` Ihor Radchenko
2023-01-07 18:34                         ` Jean Louis
2023-01-07 19:12                         ` Jean Louis
2023-01-12 15:43                         ` Max Nikulin
2023-01-13  9:41                           ` Ihor Radchenko
2023-01-04 18:03                 ` Jean Louis
2023-01-05 11:17                   ` Ihor Radchenko
2023-01-05 19:37                     ` Jean Louis
2023-01-06  3:24                       ` Max Nikulin
2023-01-07 20:07                         ` Jean Louis
2023-01-08 16:42                           ` Max Nikulin
2023-01-07  9:09                       ` Ihor Radchenko
2023-01-04 17:51               ` Jean Louis
2023-01-04 16:53           ` Jean Louis
2022-12-20 16:56 ` Problems with C-c C-e file.org 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++6gUozQ8bMeqftY49cqyJWRwrscVHgNEjZCb89DyV9svEQ@mail.gmail.com \
    --to=eduardoochs@gmail.com \
    --cc=bueno@lenep.uenf.br \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).