From: Marcin Borkowski <mbork@mbork.pl>
To: Spencer Baugh <sbaugh@catern.com>, emacs-devel@gnu.org
Subject: Re: Intermediate tutorial shipped with Emacs
Date: Sat, 19 Sep 2015 21:25:21 +0200 [thread overview]
Message-ID: <87zj0iqkim.fsf@mbork.pl> (raw)
In-Reply-To: <834miqrhza.fsf@gnu.org>
On 2015-09-19, at 09:22, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Spencer Baugh <sbaugh@catern.com>
>> Date: Fri, 18 Sep 2015 22:19:41 -0400
>>
>> As an example, consider narrowing. If a user didn't already know
>> narrowing existed, they probably wouldn't even bother searching for the
>> feature; it isn't obvious how useful until you know about it. A user
>> without knowledge of narrowing would use other hacks.
>
> A very good example. Narrowing is described in the manual in a
> 58-line section. How would you go about giving the user a "taste of"
> narrowing, without essentially telling the same story in slightly
> different words? It's not trivial (but not impossible, either).
My 2 cents:
* I like the idea of having "batteries included", and the tutorial being
part of Emacs. However, aren't e.g. Sacha Chua's Emacs chats better
for that purpose, where a human being explains his particular
use-case?
* Also, along these lines: maybe such tutorials should be centered
around "scenarios", and not features? Like, take a "scenario" called
"C editing". Then you can mention narrowing, compilation mode, maybe
rgrep and a few other things. Or, take a scenario "HTML editing".
Then you can have SGML mode, TRAMP, maybe Org-mode and exporting, etc.
Also, in such tutorials it would make sense to mention ELPA packages
(and possibly MELPA, too).
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-09-19 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 2:19 Intermediate tutorial shipped with Emacs Spencer Baugh
2015-09-19 7:22 ` Eli Zaretskii
2015-09-19 8:18 ` Stephen J. Turnbull
2015-09-19 10:00 ` Rasmus
2015-09-19 12:39 ` Stephen J. Turnbull
2015-09-19 19:18 ` Marcin Borkowski
2015-09-19 16:13 ` Spencer Baugh
2015-09-19 17:42 ` Eli Zaretskii
2015-09-19 19:25 ` Marcin Borkowski [this message]
2015-10-08 22:10 ` Filipp Gunbin
[not found] <<87a8sjcfr6.fsf@earth.catern.com>
[not found] ` <<834miqrhza.fsf@gnu.org>
2015-09-19 15:57 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj0iqkim.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-devel@gnu.org \
--cc=sbaugh@catern.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.