Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: A T does not work in nnml ...
Date: Sat, 06 Nov 2010 15:18:34 -0400	[thread overview]
Message-ID: <87mxpmz2et.fsf@andy.bu.edu> (raw)
In-Reply-To: <8762wa71qq.fsf@dod.no>

>>>>> "Steinar" == Steinar Bang <sb@dod.no> writes:

    Steinar> Here's the stack trace from C-g on when it's stuck on `A T'
    Steinar> from the nnir buffer after searching gmane.discuss for
    Steinar> "gwene":

    Steinar> Debugger entered--Lisp error: (quit)
    Steinar> quoted-printable-decode-string("Sj=C3=B8gren")
    Steinar> byte-code("\302\303\bA@\"\203.


This is hard to understand. As you have no doubt guessed, I can't
reproduce the problem. The string "Sj=C3=B8gren" is the quoted-printable
representation of Adam Sjøgren's last name. But this article is already
in the buffer right after the search for "gwene". If the
quoted-printable stuff gets decoded correctly, then why should it be any
different the next time around?

Can you edebug the function quoted-printable-decode-string and send me
the backtrace when the function is called right after the search, and
then again after the function is called following "A T"?

Thanks,
andy






  reply	other threads:[~2010-11-06 19:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02  9:45 Ulf Stegemann
2010-11-02 14:50 ` Andrew Cohen
2010-11-02 15:35   ` Ulf Stegemann
2010-11-02 15:38     ` Andrew Cohen
2010-11-02 19:45   ` Lars Magne Ingebrigtsen
2010-11-03 23:49     ` Andrew Cohen
2010-11-04  1:29       ` Andrew Cohen
2010-11-04 15:38         ` Andrew Cohen
2010-11-04 20:31           ` Steinar Bang
2010-11-05 18:15             ` Andrew Cohen
2010-11-05 20:25               ` Steinar Bang
2010-11-05 23:40                 ` Andrew Cohen
2010-11-06  8:15                   ` Steinar Bang
2010-11-06  8:29                     ` Steinar Bang
2010-11-06 11:36                       ` Andrew Cohen
2010-11-06 17:32                         ` Steinar Bang
2010-11-04 20:39           ` Lars Magne Ingebrigtsen
2010-11-06 15:55   ` Andrew Cohen
2010-11-06 18:20     ` Steinar Bang
2010-11-06 19:18       ` Andrew Cohen [this message]
2010-11-06 21:13         ` Steinar Bang
2010-11-07  0:35           ` Andrew Cohen
2010-11-07  6:13             ` Steinar Bang
2010-11-07  6:54               ` Steinar Bang
2010-11-07 13:09                 ` Andrew Cohen
2010-11-07 15:09                   ` Steinar Bang
2010-11-07 16:17                     ` Steinar Bang
2010-11-07 17:15                       ` Andrew Cohen
2010-11-07 18:23                         ` Steinar Bang
2010-11-07 18:33                           ` Steinar Bang
2010-11-07 18:56                             ` Steinar Bang
2010-11-14 16:46                               ` A T hangs forever in gmane nntp (Was: A T does not work in nnml ...) Steinar Bang
2010-11-14 17:59                                 ` A T hangs forever in gmane nnir (Was: A T hangs forever in gmane nntp) Steinar Bang
2010-11-14 20:25                                   ` A T hangs forever in gmane nnir Steinar Bang
2010-11-15 20:23                                     ` Steinar Bang
2010-11-08  8:08     ` A T does not work in nnml Ulf Stegemann

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=87mxpmz2et.fsf@andy.bu.edu \
    --to=cohen@andy.bu.edu \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).