* message.texi (Buffer Entry): New section.

diff --git a/texi/ChangeLog b/texi/ChangeLog
index 6583f0b..51aa573 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,7 @@
+2000-12-28 20:04:26  Lars Magne Ingebrigtsen  <larsi@gnus.org>
+
+       * message.texi (Buffer Entry): New section.
+
 2000-12-22  Christopher Splinter  <chris@splinter.inka.de>
 
        * gnus.texi (Group Parameters): Add documentation for the `banner'

diff --git a/texi/message.texi b/texi/message.texi
index 02b3a00..0399a1e 100644 (file)
--- a/texi/message.texi
+++ b/texi/message.texi
@@ -319,6 +319,7 @@ will be removed before popping up the buffer.  The default is
 @chapter Commands
 
 @menu
+* Buffer Entry::        Commands after entering a Message buffer.
 * Header Commands::     Commands for moving to headers.
 * Movement::            Moving around in message buffers.
 * Insertion::           Inserting things into message buffers.
@@ -330,6 +331,21 @@ will be removed before popping up the buffer.  The default is
 @end menu
 
 
+@node Buffer Entry
+@section Buffer Entry
+@cindex undo
+@kindex C-_
+
+You most often end up in a Message buffer when responding to some other
+message of some sort.  Message does lots of handling of quoted text, and
+may remove signatures, reformat the text, or the like---depending on
+which used settings you're using.  Message usually gets things right,
+but sometimes it stumbles.  To help the user unwind these stumblings,
+Message sets the undo boundary before each major automatic action it
+takes.  If you press the undo key (usually located at @kbd{C-_}) a few
+times, you will get back the un-edited message you're responding to.
+
+
 @node Header Commands
 @section Header Commands