unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jorge" <jorge+list@disroot.org>
Cc: 39359@debbugs.gnu.org
Subject: bug#39359: [patch] TUTORIAL: Be accurate about "buffer" vs "file"; capitalize Dired.  Four other trivial TUTORIAL patches
Date: Fri, 31 Jan 2020 11:29:09 +0200	[thread overview]
Message-ID: <83sgjwkm8q.fsf@gnu.org> (raw)
In-Reply-To: <79a6fd311edba2ddfbd36da083be2bd5@disroot.org> (jorge+list@disroot.org)

> Date: Thu, 30 Jan 2020 15:41:48 +0000
> From: "Jorge" <jorge+list@disroot.org>
> 
> Hello.  This trivial patch is my first patch submitted to a free
> software project (not counting wiki edits), so please do not hesitate to
> correct any mistakes (including the potential mistake of being too
> nitpicky).  Now the commit message, followed by the patch:
> 
> TUTORIAL: Be accurate about "buffer" vs "file"; capitalize Dired
> 
> - Disambiguate "buffer" vs "file" after the section that explains
>   buffers.

Thanks.

Personally, my gut feeling is that we shouldn't introduce this
complexity in the tutorial.  Users coming from other editors are used
to saying "save the file" (and the evidence is the File->Save menu
item present in many applications, including Emacs).  So "save file"
is natural, whereas "save buffer into the file it visits" is less so,
and for newbies any complication at this stage is an obstacle.  It is
no accident that buffers are described in the tutorial only after
files.  (This is yet another reason why introducing buffers before
they are described in the tutorial might be a step in the wrong
direction.)

Bottom line: I think in this case accuracy is less important than
providing an introduction to Emacs usage that is as free from
complexities as practically possible.





  reply	other threads:[~2020-01-31  9:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 15:41 bug#39359: [patch] TUTORIAL: Be accurate about "buffer" vs "file"; capitalize Dired. Four other trivial TUTORIAL patches Jorge
2020-01-31  9:29 ` Eli Zaretskii [this message]
2020-01-31 13:28 ` Jorge
2020-02-29  5:02   ` Stefan Kangas
2020-03-03 11:30     ` Jorge P. de Morais Neto
2020-04-24 10:10       ` Stefan Kangas
2020-06-07 16:20         ` Jorge P. de Morais Neto
2020-06-07 16:40           ` Eli Zaretskii
2020-06-07 18:01             ` Jorge P. de Morais Neto
2020-06-07 18:06               ` Eli Zaretskii
2020-06-07 18:24                 ` Jorge P. de Morais Neto
2020-08-09 11:47                   ` Lars Ingebrigtsen

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=83sgjwkm8q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39359@debbugs.gnu.org \
    --cc=jorge+list@disroot.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).