From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10334@debbugs.gnu.org
Subject: bug#10334: 24.0.92; Doc fix
Date: Tue, 20 Dec 2011 23:09:50 +0200 [thread overview]
Message-ID: <83d3bjymox.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0h_1aJHq-9o7_-o5UeG7H3Pu-UekoEZgWD2316k1sBzxw@mail.gmail.com>
> Date: Tue, 20 Dec 2011 19:56:37 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
>
> Here's a documentation patch:
Thanks.
> One reason to create a new buffer is to use it for making temporary
> -notes. If you try to save it, Emacs asks for the file name to use.
> -The default value of the variable @code{major-mode} determines the new
> -buffer's major mode; the default value is Fundamental mode. @xref{Major
> -Modes}.
> +notes. The default value of the variable @code{major-mode} determines
> +the new buffer's major mode; the default value is Fundamental mode.
> +@xref{Major Modes}. If you try to save it, Emacs asks for the file
> +name to use, and the major mode is then re-established, based on that
> +file name.
This change makes the text harder to understand. Previously, it was
clear that "it" in "If you try to save it" referred to the new buffer,
because that sentence directly followed the one which talked about
creating a new buffer. By moving "If you try to save it", you made
"it" ambiguous: now it's unclear what it refers to; it could be the
major mode, for example.
Here's what I think is a better version:
One reason to create a new buffer is to use it for making temporary
notes. If you try to save it, Emacs asks for the file name to use.
The default value of the variable @code{major-mode} determines the
new buffer's major mode; the default value is Fundamental mode
(@pxref{Major Modes}). However, the file name you give when saving
the buffer may cause Emacs to change the buffer's major mode as
appropriate for that file name.
next prev parent reply other threads:[~2011-12-20 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH8Pv0jFg+O+7tDR3FfSK6skO0gr-AAo1tUkDUEASuncZwJqeA@mail.gmail.com>
2011-12-20 18:56 ` bug#10334: 24.0.92; Doc fix Dani Moncayo
2011-12-20 20:27 ` Dani Moncayo
2011-12-20 21:09 ` Eli Zaretskii [this message]
2011-12-21 7:22 ` Dani Moncayo
2012-01-08 12:12 ` Dani Moncayo
2012-01-27 8:20 ` Chong Yidong
2012-01-27 9:40 ` Dani Moncayo
2012-02-23 20:35 ` Dani Moncayo
2012-02-25 3:49 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d3bjymox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10334@debbugs.gnu.org \
--cc=dmoncayo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.