From: Yuri Khan <yuri.v.khan@gmail.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Emacs developers <emacs-devel@gnu.org>,
Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Why does the tutorial talk about C-n/C-p etc?
Date: Fri, 11 Mar 2016 17:38:49 +0600 [thread overview]
Message-ID: <CAP_d_8XBP2tPE4BRCbMScvOJHmbnP-tjeUqhT8vWAmp9hCV2eQ@mail.gmail.com> (raw)
In-Reply-To: <m21t7hdzvc.fsf@fgunbin.local>
On Fri, Mar 11, 2016 at 5:21 PM, Filipp Gunbin <fgunbin@fastmail.fm> wrote:
>> L235: If you are using a graphical display, such as X or MS-Windows,
>> there should be a tall rectangular area called a scroll bar on one
>> side of the Emacs window.
>>
>> If you are using a graphical display? I mean, of course, you are using a
>> graphical display?
>
> What's wrong with this? A user may be in text console.
There’s nothing wrong with mentioning that Emacs *can also* function
in a text console, with several major restrictions (namely, the
keyboard input has an additional indirection layer, and the sets of
fonts and colors are severely reduced). But it is reasonable to assume
and encourage that a novice user will try the GUI version first.
Also, pretty much all potential new users (i.e. the target audience of
the tutorial) already know what a scrollbar is.
next prev parent reply other threads:[~2016-03-11 11:38 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 15:38 Why does the tutorial talk about C-n/C-p etc? Lars Magne Ingebrigtsen
2016-03-09 15:50 ` jpff
2016-03-09 15:50 ` Oleh Krehel
2016-03-09 16:03 ` Kaushal Modi
2016-03-09 18:25 ` Yuri Khan
2016-03-10 20:28 ` Alexey Veretennikov
2016-03-09 16:48 ` Drew Adams
2016-03-09 18:26 ` Yuri Khan
2016-03-09 19:05 ` Clément Pit--Claudel
2016-03-09 19:07 ` Drew Adams
2016-03-09 19:21 ` Clément Pit--Claudel
2016-03-10 5:48 ` Tom
2016-03-09 16:12 ` Phillip Lord
2016-03-09 16:39 ` Eli Zaretskii
2016-03-09 17:11 ` Marcin Borkowski
2016-03-09 20:22 ` John Wiegley
2016-03-09 21:32 ` Tim Cross
2016-03-09 21:42 ` John Wiegley
2016-03-10 0:30 ` Evgeny Panasyuk
2016-03-10 5:54 ` Tom
2016-03-10 7:12 ` Eli Zaretskii
2016-03-10 12:49 ` Evgeny Panasyuk
2016-03-10 21:22 ` Richard Stallman
2016-03-10 21:39 ` Clément Pit--Claudel
2016-03-10 22:06 ` Evgeny Panasyuk
2016-03-12 1:53 ` Richard Stallman
2016-03-10 6:46 ` Richard Stallman
2016-03-10 9:58 ` Phillip Lord
2016-03-10 10:26 ` Eli Zaretskii
2016-03-10 14:45 ` Stefan Monnier
2016-03-10 15:07 ` Phillip Lord
2016-03-10 15:42 ` Eli Zaretskii
2016-03-10 15:48 ` Marcin Borkowski
2016-03-10 16:16 ` Eli Zaretskii
2016-03-10 17:47 ` Marcin Borkowski
2016-03-11 11:21 ` Filipp Gunbin
2016-03-11 11:38 ` Yuri Khan [this message]
2016-03-11 14:40 ` Eli Zaretskii
2016-03-11 16:57 ` Phillip Lord
2016-03-11 17:34 ` Marcin Borkowski
2016-03-11 18:11 ` Eli Zaretskii
2016-03-11 22:00 ` Phillip Lord
2016-03-12 6:51 ` Eli Zaretskii
2016-03-12 7:17 ` Marcin Borkowski
2016-03-12 23:30 ` Phillip Lord
2016-03-12 23:26 ` Phillip Lord
2016-03-12 1:52 ` Richard Stallman
2016-03-10 23:26 ` John Wiegley
2016-03-11 2:10 ` Clément Pit--Claudel
2016-03-11 8:01 ` Dani Moncayo
2016-03-13 10:54 ` H. Dieter Wilhelm
2016-03-13 17:09 ` Stefan Monnier
2016-03-11 16:45 ` Phillip Lord
2016-03-12 19:25 ` Richard Stallman
2016-03-12 20:09 ` Eli Zaretskii
2016-03-13 11:36 ` Tom
2016-03-13 16:36 ` Eli Zaretskii
2016-03-13 17:08 ` Stefan Monnier
2016-03-13 17:27 ` Eli Zaretskii
2016-03-13 18:41 ` Clément Pit--Claudel
2016-03-13 19:03 ` Eli Zaretskii
2016-03-13 19:14 ` Clément Pit--Claudel
2016-03-13 20:27 ` Marcin Borkowski
2016-03-14 12:16 ` Richard Stallman
2016-03-14 14:14 ` Clément Pit--Claudel
2016-03-15 15:19 ` Richard Stallman
2016-03-13 19:46 ` Phillip Lord
2016-03-13 20:15 ` Clément Pit--Claudel
2016-03-14 12:15 ` Richard Stallman
2016-03-14 12:15 ` Richard Stallman
2016-03-14 16:33 ` Eli Zaretskii
2016-03-12 21:34 ` John Wiegley
2016-03-12 23:33 ` Phillip Lord
2016-03-12 1:50 ` Richard Stallman
2016-03-12 19:14 ` Chad Brown
2016-03-12 21:05 ` Evgeny Panasyuk
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=CAP_d_8XBP2tPE4BRCbMScvOJHmbnP-tjeUqhT8vWAmp9hCV2eQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=phillip.lord@russet.org.uk \
/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).