all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 464@emacsbugs.donarmstrong.com
Subject: bug#464: 23.0.60; [Regression] Implicit utf-8 no longer correctly decoded in gnus
Date: Mon, 23 Jun 2008 21:33:12 -0400	[thread overview]
Message-ID: <m37icf1us0.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <jwvabhbr7pv.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Mon, 23 Jun 2008 20:36:53 -0400")

Stefan> If you can't bisect, then can you try and provide a simple recipe?

The git logs mailed to xorg-commit AT lists.freedesktop.org and several
mails sent to the unicode list are where I most noticed this.

The xorg commit list is on gmane at gmane.comp.freedesktop.xorg.cvs,
so reading that in gnus should do it.  (Check out my recent commit
messages there.)

Hmm.  I just tested the gmane group on my webserver (debian sid,
emacs-snapshot-nox (GNU Emacs 23.0.60.1 (i486-pc-linux-gnu) of
2008-06-21 on elegiac, modified by Debian) running over ssh) and
it worked.

The bug seems to be specific to X terminals.

Seeing the above, I started the server and tried in a tty frame via
emacslcient -t.  It worked correctly when viewing a cached mail.

So nnimap may also be needed to trigger the bug????

The next time I see it in a fresh mail I'll open a tty frame and see
whether it shows up there, too.

-JimC






  reply	other threads:[~2008-06-24  1:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22  6:37 bug#464: 23.0.60; [Regression] Implicit utf-8 no longer correctly decoded in gnus James Cloos
2008-06-22 14:06 ` Stefan Monnier
2008-06-23  7:58   ` James Cloos
2008-06-24  0:36     ` Stefan Monnier
2008-06-24  1:33       ` James Cloos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-03 21:08 James Cloos
2008-07-03 21:29 James Cloos
     [not found] <m37ic2wt97.fsf@lugabout.jhcloos.org>
2010-09-30 17:36 ` Lars Magne Ingebrigtsen

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=m37icf1us0.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=464@emacsbugs.donarmstrong.com \
    --cc=monnier@iro.umontreal.ca \
    /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.