From: Harry Putnam <reader@newsguy.com>
Subject: edit a w3 rendered message
Date: 11 Nov 1999 22:08:00 -0800 [thread overview]
Message-ID: <m37ljoi6nz.fsf@satellite.local.lan> (raw)
I get messages occasionally that contain an HTML index of some *.jpg
files along with the attached *.jpg's
Its a mavica (sony) digital camera that writes in dos format to a
floppy. The HTML is stupidly formatted in all caps (the file names
too) making it useless on unix/machines. Example:
[...]
<P><A HREF="MVC-001F.JPG">MVC-001F.JPG</A> 1999 4 15 10:32:04 AM
<P><A HREF="MVC-002F.JPG">MVC-002F.JPG</A> 1999 4 15 10:52:06 AM
[...]
Because of this sillyness the links are useless unless they are edited
to look like the files they point to (ie .jpg).
I can save the jpeg files and rewrite the HTML with sed, of course but
would rather handle it right in the gnus buffer. However any attempts
to edit give the message:
"fontifiying article* buffer too big."
If one presses "C-g" at this point, you get a buffer that allows
editing but cannot be saved. Giving the message:
"Wrong type argument: window-configuration-p, nil"
Is it even possible to edit an HTML message once w3 has rendered it,
using 'gnus-summary-edit-article' function?
next reply other threads:[~1999-11-12 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 6:08 Harry Putnam [this message]
1999-11-15 20:47 ` Lars Magne Ingebrigtsen
1999-11-22 4:38 ` Harry Putnam
1999-12-01 19:08 ` 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=m37ljoi6nz.fsf@satellite.local.lan \
--to=reader@newsguy.com \
/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).