From: Lars Ingebrigtsen <larsi@gnus.org>
To: James Cloos <cloos@jhcloos.com>
Cc: ding@gnus.org
Subject: Re: Stop autowashing html
Date: Thu, 26 Dec 2013 18:08:56 +0100 [thread overview]
Message-ID: <87eh4zedzr.fsf@building.gnus.org> (raw)
In-Reply-To: <m3eh7bluh9.fsf@carbon.jhcloos.org> (James Cloos's message of "Wed, 23 Oct 2013 14:20:09 -0400")
James Cloos <cloos@jhcloos.com> writes:
> I often get hit by messages with html which shr is unable to decode in
> reasonable time or space. (Yesterday, one took more than a 20 minutes
> and a Gig of VM -- bringing the emacs process over 2G -- before I
> returned to the workstation, saw what was happening, and hit C-g.)
That sounds like an infloop bug in shr. A couple of those have been
fixed lately.
> Is there any chance of fixing that change? Manual washing with Wh is
> vastly better than the current situation.
>
> Or will I have to maintain a local fork?
`C-u g' will show you the raw article.
> Another fairly recent annoyance is the insistence of adding the sent and
> archive groups to the current *Group* view every time an outgoing is
> started. I set them at a high level to keep them *out* of the current
> group view. It never helps the UI and only ever leads to annoyance.
> I certainly *never* want to leave the last group in a view and end up
> in the drafts group just because I happened to reply along the way.
Yeah, I'm not sure that's a good change. I'm not sure why this was
done -- anybody remember?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2013-12-26 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 18:20 James Cloos
2013-12-26 17:08 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh4zedzr.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=cloos@jhcloos.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).