From: David Kastrup <dak@gnu.org>
To: David House <dmhouse@gmail.com>
Cc: Phil Sung <psung@MIT.EDU>, emacs-devel@gnu.org
Subject: Re: guided tour suggestions
Date: Thu, 28 Jun 2007 12:25:38 +0200 [thread overview]
Message-ID: <86wsxowf31.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <18051.34134.815718.363379@gargle.gargle.HOWL> (David House's message of "Thu\, 28 Jun 2007 10\:54\:30 +0100")
David House <dmhouse@gmail.com> writes:
> Perhaps we could have a little section in the tour showing off how
> customisable Emacs is. We could say:
>
> If you want a more bare-bones Emacs, a good start might be to turn
> off some of the more prominent GUI features.
>
> [Screenshot showing Custom buffer with settings to turn off
> scrollbar, menus and toolbar, in an Emacs without those features
> activated.]
Personally, I find this irrelevant for a tour. A single sentence "All
of the graphical and other features can be customized and also turned
off if desired" is sufficient.
If we really _must_ show anything in that respect, a customize buffer
is not really convincing. Instead, the Options/Show/Hide menu would
be more appropriate.
> Every single time a different colour or font is used, you can
> customise which one to use:
>
> [Screenshot showing an Emacs with a white-on-black colour scheme
> and a non-default font.]
It is actually not much of a selling point: most people just assume
that they can configure stuff like that.
> These are just the GUI customisations. Here's a selection of the
> other things you can change:
>
> * Every single key binding in every single mode can be remapped, including
> mouse sequences.
> * You can redefine any function or command by writing Emacs Lisp.
> [... a few more things here]
>
> Because all of these options can be overwhelming, Emacs provides a powerful
> configuration interface, M-x custom:
>
> [Screenshot of the top Custom group.]
>
> http://emacswiki.org also contains a veritable library of common and
> not-so-common customisations.
>
> Or something of the sort. I think this is an important part of Emacs we should
> try to convey.
Maybe. We should not overdo this aspect. After all, one _can_ work
reasonably well with the default settings. Customizing Emacs is
something for which the desire will only come with some time of usage.
--
David Kastrup
next prev parent reply other threads:[~2007-06-28 10:25 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
2007-06-28 9:54 ` David House
2007-06-28 10:25 ` David Kastrup [this message]
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=86wsxowf31.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=dmhouse@gmail.com \
--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.