From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Joel J. Adamson" <adamsonj@email.unc.edu>,
4960@emacsbugs.donarmstrong.com
Cc: "Jason A. Spiro" <jasonspiro4@gmail.com>
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 15:08:34 +0100 [thread overview]
Message-ID: <e01d8a50911190608t7579b7fbqdbc0b86039072731@mail.gmail.com> (raw)
In-Reply-To: <16352.1258637742@chondestes.bio.unc.edu>
On Thu, Nov 19, 2009 at 2:35 PM, Joel J. Adamson <adamsonj@email.unc.edu> wrote:
>>>>>> "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.
You might be showing Emacs to someone. Since it is at least on some
systems easy to install you could use the tour to decide if you want
to use Emacs for what you currently want to do. It may also give you
inspirations for new ways to use Emacs.
prev parent reply other threads:[~2009-11-19 14:08 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
2009-11-19 14:08 ` Lennart Borgman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50911190608t7579b7fbqdbc0b86039072731@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=4960@emacsbugs.donarmstrong.com \
--cc=adamsonj@email.unc.edu \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).