all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Phil Sung <psung@MIT.EDU>
Cc: emacs-devel@gnu.org
Subject: Re: guided tour suggestions
Date: Thu, 28 Jun 2007 09:20:43 +0200	[thread overview]
Message-ID: <86tzssy27o.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <874pksef39.fsf@phil.mit.edu> (Phil Sung's message of "Thu\, 28 Jun 2007 03\:02\:50 -0400")

Phil Sung <psung@MIT.EDU> writes:

> David Kastrup <dak@gnu.org> writes:
>> Would it be possible to make the screenshots with emacs -Q so that people see
>> what they get out of the box ... ?
>
> Good idea.
>
>> The guided tour ... shows an Emacs a) compiled without a modern
>> toolkit (Gtk+, Windows or Mac) b) without menus c) without toolbars
>> d) without scrollbars (for heaven's sake!) e) without font
>> diversity. The only thing hinting at fonts is a man-page f) without
>> file dialogs g) without tooltips h) without any non-ASCII character
>
> When I get a chance, I will make some screenshots with the default
> UI setup, and with more complex formatting/characters.

Very much appreciated.  One of the problems with promoting Emacs
nowadays are users who tried it 10 years ago and were not getting
along with it.  Dispelling their (and their audience's) preconceptions
is easier with more graphical material.

I am aware that one of the most frequent customizations is turning off
the toolbar in order to maximize screen estate and minimize clutter.
For a live showoff of the skills of an experienced user, this might be
somewhat feasible.  But as soon as we are getting into (live or
off-line) tutorial reign, it becomes a much better idea to show off
and use the menus: that way, people have a chance of _following_ what
you are doing, and maybe even of doing it by themselves.  And they
have the cues for trying it by themselves and remembering the moves
when they are alone.  That the work style of a long-time user is a
different one is not that important.

Thanks for caring,

-- 
David Kastrup

  reply	other threads:[~2007-06-28  7:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 18:03 guided tour suggestions Karl Berry
2007-05-03 20:34 ` Phil Sung
2007-06-02 20:52   ` Chong Yidong
2007-06-02 21:04     ` David Kastrup
2007-06-02 22:08     ` Drew Adams
2007-06-03  8:23       ` Mathias Dahl
2007-06-03 15:32       ` David House
2007-06-11 20:01     ` Phil Sung
2007-06-11 20:19       ` Drew Adams
2007-06-27  1:16         ` Phil Sung
2007-06-27  4:28           ` Drew Adams
2007-06-27  5:45           ` David Kastrup
2007-06-27  6:04             ` Nick Roberts
2007-06-27  7:37               ` David Kastrup
2007-06-28  7:02             ` Phil Sung
2007-06-28  7:20               ` David Kastrup [this message]
2007-06-28  9:54                 ` David House
2007-06-28 10:25                   ` David Kastrup
2007-08-09  7:15                 ` Phil Sung
2007-08-09  7:36                   ` David Kastrup
2007-08-13  8:09                     ` Phil Sung
2007-06-28  8:20               ` Nick Roberts
2007-06-28  8:36                 ` David Kastrup
2007-06-29 16:41               ` Juri Linkov
2007-06-30  1:16               ` Nick Roberts
2007-06-30 10:03                 ` David House
2007-07-22 10:59                   ` Dieter Wilhelm
2007-05-03 22:30 ` David Koppelman
2007-05-03 22:41   ` Daniel Brockman
2007-05-04  5:09 ` Dieter Wilhelm
2007-05-04  7:32   ` Eli Zaretskii
2007-05-05 14:39 ` Randal L. Schwartz

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=86tzssy27o.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=psung@MIT.EDU \
    /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.