all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@catern.com>
Cc: stephen@xemacs.org, emacs-devel@gnu.org
Subject: Re: Intermediate tutorial shipped with Emacs
Date: Sat, 19 Sep 2015 20:42:22 +0300	[thread overview]
Message-ID: <83oagypapt.fsf@gnu.org> (raw)
In-Reply-To: <87wpvmbd5m.fsf@earth.catern.com>

> From: Spencer Baugh <sbaugh@catern.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 19 Sep 2015 12:13:25 -0400
> 
> Still, I think it is important that new users be able to quickly get a
> broad sense of the categories of features available in Emacs. Perhaps a
> node that links to all these tutorials, and describes the subject area
> of each of them in a paragraph or two of text?

I think this is impractical.  Emacs has so many different categories
of features in so many completely unrelated fields of application,
that it'd be a challenge to organize such a list in any way that
allows a user to quickly find the categories she might be interested
in.  Keep in mind that just explaining what is included in a category
might take a non-trivial amount of text.

> That is kind of like the Emacs manual's top node

Exactly!  So we already have that material in place.

> but perhaps more helpful for discovering new features, since it
> could be more descriptive than the single-line summaries, and also
> have less material to search through by virtue of grouping some
> features together.

Beware: "more descriptive" might also mean "too long".
Discoverability is hampered by having to wade through too long
descriptions of the stuff to be discovered.

For those reasons, I suggest a bottom-up approach: first let's have a
few of such tutorials, and then let's think how to help users discover
them.  As long as the number of tutorials is small, just their list is
good enough, IMO.  So we can postpone a more serious "guide to
tutorials" when we have enough of them to necessitate such a guide.



  reply	other threads:[~2015-09-19 17:42 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 [this message]
2015-09-19 19:25   ` Marcin Borkowski
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=83oagypapt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sbaugh@catern.com \
    --cc=stephen@xemacs.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 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.