bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#3448: 23.0.93; Documentation mismatch in Message mode keybindings


From: Ryan Yeske
Subject: bug#3448: 23.0.93; Documentation mismatch in Message mode keybindings
Date: Mon, 01 Jun 2009 19:18:49 -0700

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

There are a couple inconsistencies between the documentation in 
(info "(message) Header Commands") and the actual bindings specified in
the code.

`C-c C-f C-o' is described as running both `message-goto-followup-to'
and `message-goto-from'. It is only runs the latter.

C-c C-f C-f is documented as running `message-goto-bcc', but C-c C-f C-f
runs the command `message-goto-followup-to'

C-c C-f C-w is what actually runs `message-goto-fcc', which was not
documented.

I assume the code is correct, and am including a patch to the
documentation (inline, at the end) to fix these inconsistencies.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/home/rcy/emacs/etc/DEBUG for instructions.


In GNU Emacs 23.0.93.1 (i686-pc-linux-gnu, X toolkit)
 of 2009-05-21 on freegeek
Windowing system distributor `The X.Org Foundation', version 11.0.10502000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: es_MX.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Mail

Minor modes in effect:
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
M-x m e s s a g <tab> c <tab> <M-backspace> <M-backspace> 
<tab> m a i <tab> <return> C-c C-f C-w C-c C-f C-f 
C-a C-k C-k C-n C-k C-k M-x r e p o r t - e m a c s 
- b u f <backspace> g <return>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Making completion list...
Source file `/home/rcy/emacs/lisp/view.el' newer than byte-compiled file
Parsing /home/rcy/.mailrc... done

2009-06-02  Ryan Yeske  <rcyeske@gmail.com>

        * message.texi (Header Commands): Fix descriptions to match
        keybindings.

*** message.texi.~1.13.~        2009-03-21 02:08:27.000000000 -0700
--- message.texi        2009-06-01 19:07:07.000000000 -0700
***************
*** 551,558 ****
  @findex message-goto-bcc
  Go to the @code{Bcc} header (@code{message-goto-bcc}).
  
! @item C-c C-f C-f
! @kindex C-c C-f C-f
  @findex message-goto-fcc
  Go to the @code{Fcc} header (@code{message-goto-fcc}).
  
--- 551,558 ----
  @findex message-goto-bcc
  Go to the @code{Bcc} header (@code{message-goto-bcc}).
  
! @item C-c C-f C-w
! @kindex C-c C-f C-w
  @findex message-goto-fcc
  Go to the @code{Fcc} header (@code{message-goto-fcc}).
  
***************
*** 581,588 ****
  @findex message-goto-distribution
  Go to the @code{Distribution} header (@code{message-goto-distribution}).
  
! @item C-c C-f C-o
! @kindex C-c C-f C-o
  @findex message-goto-followup-to
  Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
  
--- 581,588 ----
  @findex message-goto-distribution
  Go to the @code{Distribution} header (@code{message-goto-distribution}).
  
! @item C-c C-f C-f
! @kindex C-c C-f C-f
  @findex message-goto-followup-to
  Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
  





reply via email to

[Prev in Thread] Current Thread [Next in Thread]