From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: mime/w3/html/images/agent support
Date: 18 Sep 1998 09:03:11 -700 [thread overview]
Message-ID: <x767elwgqo.fsf@des.castles.com> (raw)
(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)).
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?
To make matters worse (and I know this is a known .30 problem) the
URL buttons didn't work. To make things *much* worse (and this
problem is unknown), I did that connection for no reason, as the gifs
appeared *blank* in my buffer. Doesn't make any sense, since I used
netscape to verify the gif still existed on the web...
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next reply other threads:[~1998-09-18 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-18 16:03 Wes Hardaker [this message]
1998-09-18 17:28 ` William M. Perry
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=x767elwgqo.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
/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).