unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Eli Zaretskii <eliz@gnu.org>
Subject: bug#2023: marked as done (23.0.60; rmail-redecode-body is not  available)
Date: Sat, 31 Jan 2009 15:05:04 +0000	[thread overview]
Message-ID: <handler.2023.D2023.123341373929779.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: ud4ecu6ai.fsf@gnu.org

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]


Your message dated Sat, 31 Jan 2009 16:55:26 +0200
with message-id <ud4e3zfs1.fsf@gnu.org>
and subject line Re: bug#2023: 23.0.60; rmail-redecode-body is not available
has caused the Emacs bug report #2023,
regarding 23.0.60; rmail-redecode-body is not available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
2023: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2023
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 5451 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; rmail-redecode-body is not available
Date: Sat, 24 Jan 2009 16:28:53 +0200
Message-ID: <ud4ecu6ai.fsf@gnu.org>


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's no rmail-redecode-body function in the new Rmail (after the
mbox merge).  This command is very important functionality, both for
when Emacs decodes the message incorrectly (e.g., due to absent or bad
MIME headers in the message), and when a multi-part message is decoded
by hand.

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
d:/gnu/emacs/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2009-01-24 on HOME-C4E4A596F7
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'

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: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1255
  default-enable-multibyte-characters: t

Major mode: RMAIL

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:
<return> <return> <up> <up> <up> <up> SPC SPC <down> 
<M-left> SPC SPC <down> <M-left> SPC SPC <down> <down> 
T h e SPC l a s t SPC c o m m a n d SPC a u t o m a 
t i c a l l y SPC s a v e s SPC t h e SPC R m a i l 
SPC i n b o x SPC ( a s SPC i t SPC s h o u l d ) , 
SPC b u t SPC t h e SPC b u f f e r SPC i s SPC m a 
r k e d SPC m o d i f i e d SPC a f t e r SPC s a c 
e <backspace> <backspace> <backspace> <backspace> t 
h e SPC s a v e SPC <backspace> . <C-left> <C-left> 
<C-left> <C-left> <C-left> <C-left> <C-right> SPC n 
e v e r t h e l e s s M-q <help-echo> <help-echo> <help-echo> 
<down-mouse-1> <mouse-1> <help-echo> C-x o <C-home> 
<down> <down> <down> <down> <down> C-SPC <next> <down> 
<down> <down> <down> <down> <down> <down> <down> <next> 
<next> <next> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> M-w <down-mouse-1> <drag-mouse-1> <help-echo> 
<C-home> <down> <right> <right> <right> <right> C-SPC 
<down> <left> <left> <left> <left> <left> <down> C-e 
<right> M-w <help-echo> <down-mouse-1> <mouse-1> <help-echo> 
C-x C-x C-x 0 <down> <down> <up> C-SPC <down> M-w C-x 
b m a <tab> <return> M-x r e d e c o d e - b o d y 
<return> C-g C-h f r e d e <backspace> <backspace> 
<backspace> m a i l - r e d e c o d e - b o d y <return> 
<return> C-g M-x <up> <return>

Recent messages:
37 new messages read
Auto-saving...done
Mark set [2 times]
Saved text from "  emacs -Q
  C-u M-x rmail FOO RET
  C-u"
Mark set [2 times]
exchange-point-and-mark: No mark set in this buffer
Mark set
Auto-saving...done
Quit [2 times]



[-- Attachment #3: Type: message/rfc822, Size: 1854 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: 2023-done@emacsbugs.donarmstrong.com
Cc: cyd@stupidchicken.com
Subject: Re: bug#2023: 23.0.60; rmail-redecode-body is not available
Date: Sat, 31 Jan 2009 16:55:26 +0200
Message-ID: <ud4e3zfs1.fsf@gnu.org>

> Date: Sat, 31 Jan 2009 12:14:28 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 2023@emacsbugs.donarmstrong.com
> 
> I suggest to leave this bug open until the other bugs related to
> encoding/decoding (#2015, #2017, and #2018) are fixed, and then
> revisit this one.

With bug #2018 fixed, I can now confirm that rmail-redecode-body does
its job correctly.  Thanks.


      reply	other threads:[~2009-01-31 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ud4e3zfs1.fsf@gnu.org>
2009-01-24 14:28 ` bug#2023: 23.0.60; rmail-redecode-body is not available Eli Zaretskii
2009-01-31 15:05   ` Emacs bug Tracking System [this message]

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=handler.2023.D2023.123341373929779.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=eliz@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).