From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: nnrss/w3m bug? (was: Updated nnrss.el back-end)
Date: Fri, 11 Apr 2003 14:12:45 -0400 [thread overview]
Message-ID: <4nwui0kin6.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87el57htgy.fsf@batman.everybody.org> (Mark A. Hershberger's message of "Sun, 16 Mar 2003 15:50:05 -0600")
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
On Sun, 16 Mar 2003, mah@everybody.org wrote:
> I've done a bit of work on the nnrss.el back-end and was wondering
> if I could get some people here to give me feedback.
I don't know if it's RSS or w3m, but loading the attached message into
a message buffer and then hitting TAB (widget-forward) locks up Gnus
and I have to hit C-g a few times to break.
Also, moving to the link with the arrows triggers the same behavior -
here, Up (w3m-previous-anchor) will lock up Gnus as well.
I've only noticed this in nnrss backends, though I see HTML links in
other messages and move to them without problems.
I'm not sure if this is a bug or my misconfiguration of Gnus, so I
didn't report this as a bug yet.
Sorry about the duplicate, I hit the wrong key by mistake and sent off
a semi-finished message. This one has the bad message attached.
Thanks
Ted
[-- Attachment #2: nnrssbug.txt --]
[-- Type: text/plain, Size: 697 bytes --]
Mime-Version: 1.0
Content-Type: text/html
Newsgroups: Linux Today
Subject: developerWorks: Metaclass Programming in Python
Date: Fri, 11 Apr 2003 13:42:16 -0400
Message-ID: <1289@Linux Today.nnrss>
"Most readers are already familiar with the concepts of
object-oriented programming: inheritance, encapsulation,
polymorphism. But the creation of objects of a given class, with
certain parents, is usually thought of as a 'just so' operation. It
turns out that a number of new programming constructs become either
easier, or possible at all, when you can customize the process of
object creation..."
<p><a href='http://linuxtoday.com/news_story.php3?ltsn=2003-04-11-004-26-OS-HL-DV'>link</a></p>
next prev parent reply other threads:[~2003-04-11 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 21:50 Updated nnrss.el back-end Mark A. Hershberger
2003-03-17 2:27 ` ShengHuo ZHU
2003-03-17 4:50 ` Mark A. Hershberger
2003-04-11 18:11 ` Ted Zlatanov
2003-04-11 18:12 ` Ted Zlatanov [this message]
2003-04-11 18:29 ` nnrss/w3m bug? Mark A. Hershberger
2003-04-11 19:39 ` Ted Zlatanov
2003-04-14 1:48 ` Mark A. Hershberger
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=4nwui0kin6.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--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).