From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: mime/w3/html/images/agent support
Date: 18 Sep 1998 12:28:00 -0500 [thread overview]
Message-ID: <86ogsd8h5r.fsf@kramer-fast.bp.aventail.com> (raw)
In-Reply-To: Wes Hardaker's message of "18 Sep 1998 09:03:11 -700"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
> (and if that doesn't indicate a complex issue...)
>
> Ok, (ha ha ha, solve this one Lars):
>
> I finally got a text/html message (I was going to try and generate one to
> mail myself figuring this issue would pop up, but I realized as I started
> the composition process that since dropping TM I could no longer *write*
> mime messages... (unless I missed something)).
You can use the TM composition stuff without using the reading hooks.
Somehow - I can't remember off the top of my head, it's been a while.
> Anyway, I figured this would happen: you get a text/html part that is
> displayed with w3 (which is, simply *way* too cool) but it trys to
> download the images. This is a problem when you're in off-line agent
> mode (like I was) and it brought by my ISDN connection (not a big deal,
> but it shouldn't and would fail under many hand-dialed modem cases).
> Anyway, is there anyway to put w3 into an off-line mode telling it to
> only look in its cache (if it has one, its been a while since I've looked
> into it) that could be dependent on the plugged/unplugged status of gnus?
You could do:
(let ((url-standalone-mode (not gnus-plugged)))
(do-w3-stuff-here))
-Bill P.
next prev parent reply other threads:[~1998-09-18 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-18 16:03 Wes Hardaker
1998-09-18 17:28 ` William M. Perry [this message]
1998-09-18 17:41 ` Wes Hardaker
1998-09-18 17:46 ` William M. Perry
1998-09-18 18:04 ` Wes Hardaker
1998-09-19 20:51 ` 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=86ogsd8h5r.fsf@kramer-fast.bp.aventail.com \
--to=wmperry@aventail.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).