all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Joel J. Adamson" <adamsonj@email.unc.edu>
To: "Jason A. Spiro" <jasonspiro4@gmail.com>
Cc: Emacs Bugs <bug-gnu-emacs@gnu.org>
Subject: bug#4960: 23.1.50; Please provide access to the tour on the Help menu; preferably ship it also
Date: Thu, 19 Nov 2009 08:35:42 -0500	[thread overview]
Message-ID: <16352.1258637742@chondestes.bio.unc.edu> (raw)
In-Reply-To: <c241693f0911181915n2b264865l2f957043d93ee337@mail.gmail.com>

>>>>> "Jason" == Jason A Spiro <jasonspiro4@gmail.com> writes:

    > Hi, Please provide access to the Emacs guided tour on the Emacs'
    > Help menu.  Preferably as the first item on the menu, since it is
    > more useful than the tutorial.

The tour shows features of Emacs, the tutorial shows you how to use the
basic editing commands.  How is one "more useful" than the other?  I
agree that the tour is more useful if you're deciding whether to use
Emacs, but if you've already installed Emacs, you need to know how to
use it in order to get at those features.

Joel
-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280






  parent reply	other threads:[~2009-11-19 13:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  3:15 bug#4960: 23.1.50; Please provide access to the tour on the Help menu; preferably ship it also Jason A. Spiro
2009-11-19  8:03 ` Glenn Morris
2009-11-19 12:27   ` Lennart Borgman
2009-11-19 13:34     ` Joel J. Adamson
2009-11-19 14:06       ` Lennart Borgman
2009-11-20  9:32     ` Juri Linkov
2009-11-20 10:53       ` Kevin Rodgers
2009-11-20 11:14         ` Juri Linkov
2009-11-20 12:06       ` Lennart Borgman
2020-04-28 17:28       ` Stefan Kangas
2020-05-12 14:58         ` Stefan Kangas
2009-11-19 13:35 ` Joel J. Adamson [this message]
2009-11-19 14:08   ` Lennart Borgman

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=16352.1258637742@chondestes.bio.unc.edu \
    --to=adamsonj@email.unc.edu \
    --cc=4960@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=jasonspiro4@gmail.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.