unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: 10334@debbugs.gnu.org
Subject: bug#10334: 24.0.92; Doc fix
Date: Thu, 23 Feb 2012 21:35:36 +0100	[thread overview]
Message-ID: <CAH8Pv0j9aF_-tGXDDBjXUosbBCQwr3V_1wOaTAFu0Tv84KKKow@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0i-ybpveZxXKUeq7Sg=4d_XC7Q2xyMsHdoTAPTUCwy8eg@mail.gmail.com>

>> Thanks, I've committed the various fixed you pointed out in this thread
>> to the trunk.
>
> Thanks Chong.  But I wonder why you didn't mention anything about the
> major-mode re-setting that may take place after you save the new
> buffer to a file.

Ping.

I think that the explanation about the new buffer's major mode would
be more complete if we mention that the major mode may change when the
buffer is saved to a file.

For example:

=== modified file 'doc/emacs/buffers.texi'
--- doc/emacs/buffers.texi      2012-02-09 06:43:23 +0000
+++ doc/emacs/buffers.texi      2012-02-23 20:28:35 +0000
@@ -106,7 +106,9 @@
 determines the new buffer's major mode; the default value is
 Fundamental mode.  @xref{Major Modes}.  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.
+it, Emacs asks for the file name to use, and the buffer's major mode
+is re-established taking that file name into account (@pxref{Choosing
+Modes}).

 @kindex C-x @key{LEFT}
 @kindex C-x @key{RIGHT}




-- 
Dani Moncayo





  reply	other threads:[~2012-02-23 20:35 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
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 [this message]
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

  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=CAH8Pv0j9aF_-tGXDDBjXUosbBCQwr3V_1wOaTAFu0Tv84KKKow@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=10334@debbugs.gnu.org \
    --cc=cyd@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).