From: Jorge P. de Morais Neto <jorge+list@disroot.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39359@debbugs.gnu.org, stefan@marxist.se
Subject: bug#39359: [patch] TUTORIAL: Be accurate about "buffer" vs "file"; capitalize Dired. Four other trivial TUTORIAL patches
Date: Sun, 07 Jun 2020 15:01:29 -0300 [thread overview]
Message-ID: <874krmwy9y.fsf@disroot.org> (raw)
In-Reply-To: <83tuzm7rsd.fsf@gnu.org>
Em [2020-06-07 dom 19:40:50+0300], Eli Zaretskii escreveu:
>> - For consistency with C-x C-f ("Find file") and C-x C-s ("Save file"),
>> refer to C-x s as "Save some files".
>
> But that is inaccurate: "C-x C-f" indeed reads a file into a buffer,
> but "C-x C-f" saves the _buffer_ into its file. "Save file" is not
> what "C-x C-s" does, since the file is not saved anywhere.
>
> How about saying "Save some buffers to their files" instead?
You mean like this?
--8<---------------cut here---------------start------------->8---
diff --git a/etc/tutorials/TUTORIAL b/etc/tutorials/TUTORIAL
index eb3acde9c0..227c13f3e3 100644
--- a/etc/tutorials/TUTORIAL
+++ b/etc/tutorials/TUTORIAL
@@ -612,11 +612,11 @@ but it also means that you need a convenient way to save the first
file's buffer. Having to switch back to that buffer, in order to save
it with C-x C-s, would be a nuisance. So we have
- C-x s Save some buffers
+ C-x s Save some buffers to their files
-C-x s asks you about each buffer which contains changes that you have
-not saved. It asks you, for each such buffer, whether to save the
-buffer.
+C-x s asks you about each file-visiting buffer which contains changes
+that you have not saved. It asks you, for each such buffer, whether
+to save the buffer to its file.
>> Insert a line of text, then type C-x s.
It should ask you whether to save the buffer named TUTORIAL.
@@ -660,8 +660,8 @@ as by a mail handling utility.
There are many C-x commands. Here is a list of the ones you have learned:
C-x C-f Find file
- C-x C-s Save file
- C-x s Save some buffers
+ C-x C-s Save buffer to file
+ C-x s Save some buffers to their files
C-x C-b List buffers
C-x b Switch buffer
C-x C-c Quit Emacs
@@ -1081,7 +1081,7 @@ corresponding command names (such as C-x C-f beside find-file).
You can learn more about Emacs by reading its manual, either as a
printed book, or inside Emacs (use the Help menu or type C-h r).
Two features that you may like especially are completion, which saves
-typing, and dired, which simplifies file handling.
+typing, and Dired, which simplifies file handling.
Completion is a way to avoid unnecessary typing. For instance, if you
want to switch to the *Messages* buffer, you can type C-x b *M<Tab>
--8<---------------cut here---------------end--------------->8---
Best regards,
Jorge
--
- <https://jorgemorais.gitlab.io/justice-for-rms/>
- I am Brazilian. I hope my English is correct and I welcome feedback.
- Free Software Supporter: <https://www.fsf.org/free-software-supporter>
- If an email of mine arrives at your spam box, please notify me.
next prev parent reply other threads:[~2020-06-07 18:01 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
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 [this message]
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=874krmwy9y.fsf@disroot.org \
--to=jorge+list@disroot.org \
--cc=39359@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).