From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Stop autowashing html
Date: Wed, 23 Oct 2013 14:20:09 -0400 [thread overview]
Message-ID: <m3eh7bluh9.fsf@carbon.jhcloos.org> (raw)
It used to be the case that setting gnus-treat-wash-html nil would
prevent automatic decoding of html parts.
Then, as announced here, that capability was deliberately disabled.
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.)
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?
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.
</vent>
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2013-10-23 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 18:20 James Cloos [this message]
2013-12-26 17:08 ` Lars 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=m3eh7bluh9.fsf@carbon.jhcloos.org \
--to=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).