unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: rms@gnu.org, mlang@delysid.org, emacs-devel@gnu.org
Subject: Re: German tutorial fix
Date: Thu, 16 May 2002 15:52:14 +0300	[thread overview]
Message-ID: <3277-Thu16May2002155214+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <vafznz08jk5.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE)

> From: Kai.Grossjohann@CS.Uni-Dortmund.DE
> Date: Thu, 16 May 2002 12:37:46 +0200
> 
> I only meant: WIBNI the tutorial explained <home> and <end>?  Maybe
> it could list the `cursor block' equivalents wherever applicable.  So
> <left> could be mentioned as an alternative to C-b, M-<left> and
> C-<left> as an alternative to M-b, and so on.
> 
> Hm.  Maybe these are all obvious these days and need not be
> mentioned?  I vaguely recall this has been discussed before but I
> don't remember the outcome.

IMHO, the tutorial needs to be reworked, now that basic cursor motion
is no longer a mystery for novices.  So the "BASIC CURSOR CONTROL"
section should be a lot shorter than it is now.  It should just tell
that cursor motion keys ``work as usual'', and show the keyboard
equivalents of the editing keys (C-n for <down>, C-f for <right>,
etc.), telling the new users they are advised to learn them because
those keys allow for faster typing.

This should significantly reduce the 150 lines we devote to something
everybody knows nowadays.  We could then add to the tutorial stuff
that is important, but isn't there, without risking to bloat the file
too much.  Some ideas for things to add:

  - Options menu and Customize
  - Frames
  - Region and the mark
  - Command history in the minibuffer
  - M-x compile and M-x grep

  reply	other threads:[~2002-05-16 12:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14 13:07 German tutorial fix Mario Lang
2002-05-14 15:05 ` Kai Großjohann
2002-05-16  7:22   ` Richard Stallman
2002-05-16 10:37     ` Kai Großjohann
2002-05-16 12:52       ` Eli Zaretskii [this message]
2002-05-16 14:10         ` Andreas Fuchs
2002-05-16 15:37           ` Eli Zaretskii
2002-05-17 19:28         ` Richard Stallman
2002-05-18  0:44           ` Francesco Potorti`
2002-05-18  2:00             ` Miles Bader
2002-05-18  7:17               ` Andreas Fuchs
2002-05-18 11:59               ` Francesco Potorti`
2002-05-18 12:12                 ` Miles Bader
2002-05-18 12:55                   ` Eli Zaretskii
2002-05-18 13:11                     ` Andreas Fuchs
2002-05-19  4:56                       ` Eli Zaretskii
2002-05-19  5:30                       ` Richard Stallman
2002-05-18 20:36                     ` Kim F. Storm
2002-05-20 22:58                   ` Francesco Potorti`
2002-05-19  5:30                 ` Richard Stallman
2002-05-19 12:54                   ` Alex Schroeder
2002-05-19 13:30                     ` Miles Bader
2002-05-19 14:47                       ` Stefan Monnier
2002-05-19 15:26                       ` Alex Schroeder
2002-05-19 16:10                         ` Miles Bader
2002-05-20 10:47                           ` Alex Schroeder
2002-05-23 19:45                         ` Robert J. Chassell
2002-05-23 23:45                           ` Alex Schroeder
2002-05-20 14:48                       ` Richard Stallman
2002-05-18 14:18               ` Alex Schroeder
2002-05-18  6:44             ` Eli Zaretskii
2002-05-19 19:44             ` Robert J. Chassell
2002-05-20 14:40               ` Mario Lang
2002-05-20 21:13                 ` Colin Walters
2002-05-17 19:28       ` Richard Stallman
2002-05-15  0:13 ` Werner LEMBERG
2002-05-15  4:41   ` Eli Zaretskii

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=3277-Thu16May2002155214+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=mlang@delysid.org \
    --cc=rms@gnu.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 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).