* [pgnus v0.66] Recursive MIME problem
@ 1999-01-04 0:04 Jack Twilley
1999-01-04 9:25 ` Kai.Grossjohann
1999-01-11 1:03 ` Lars Magne Ingebrigtsen
0 siblings, 2 replies; 4+ messages in thread
From: Jack Twilley @ 1999-01-04 0:04 UTC (permalink / raw)
Someone forwarded me a message that had a JPG in it.
The message I got had something like this in it:
[2. message/rfc822]...
So I put my point on it and hit 'e'.
Up came 'Viewing with mm-view-message', and the message came up in a
*mm* buffer. I then went down to the message that looked like this:
[2. foo.jpg --- image/jpeg; foo.jpg]...
Put my point on it and hit 'e'.
I get the following traceback:
Signaling: (error "Command invoked outside of a Gnus article buffer")
signal(error ("Command invoked outside of a Gnus article buffer"))
error("Command invoked outside of a Gnus article buffer")
gnus-article-check-buffer()
gnus-mime-externalize-part()
* call-interactively(gnus-mime-externalize-part)
This kinda sucks. Either message/rfc822's should be expanded into
article buffers (or inlined), or mm buffers should allow these
commands.
Whee. :-) Thanks for the rant.
Jack.
(how can I look at dirty pictures if you don't fix this?)
.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [pgnus v0.66] Recursive MIME problem
1999-01-04 0:04 [pgnus v0.66] Recursive MIME problem Jack Twilley
@ 1999-01-04 9:25 ` Kai.Grossjohann
1999-01-04 18:59 ` Jack Twilley
1999-01-11 1:03 ` Lars Magne Ingebrigtsen
1 sibling, 1 reply; 4+ messages in thread
From: Kai.Grossjohann @ 1999-01-04 9:25 UTC (permalink / raw)
Jack Twilley <jmt+usenet@nycap.rr.com> writes:
> (how can I look at dirty pictures if you don't fix this?)
You can type C-d on such a message, then easily look at the pictures
in there.
kai
--
Just because I'm paranoid doesn't mean they're not out there to get me!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [pgnus v0.66] Recursive MIME problem
1999-01-04 9:25 ` Kai.Grossjohann
@ 1999-01-04 18:59 ` Jack Twilley
0 siblings, 0 replies; 4+ messages in thread
From: Jack Twilley @ 1999-01-04 18:59 UTC (permalink / raw)
>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Jack> (how can I look at dirty pictures if you don't fix this?)
Kai> You can type C-d on such a message, then easily look at the
Kai> pictures in there.
Doh. I never thought of it as a digest. That works beautifully
recursively. Thanks.
I still think it's a bug that the other way doesn't work.
Thanks!
Jack.
(happy picture boy)
.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [pgnus v0.66] Recursive MIME problem
1999-01-04 0:04 [pgnus v0.66] Recursive MIME problem Jack Twilley
1999-01-04 9:25 ` Kai.Grossjohann
@ 1999-01-11 1:03 ` Lars Magne Ingebrigtsen
1 sibling, 0 replies; 4+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-01-11 1:03 UTC (permalink / raw)
Jack Twilley <jmt+usenet@nycap.rr.com> writes:
> This kinda sucks. Either message/rfc822's should be expanded into
> article buffers (or inlined), or mm buffers should allow these
> commands.
Er. Yes. The problem is that the Gnus article buffers really are,
er, nothing. They need a summary buffer to function. So perhaps a
summary buffer should be created as well... or perhaps Gnus should
make it possible for proper article buffers to exists without summary
buffers. Hm. I think the latter would be nicest, but I don't know
how much work that would be, really...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-01-11 1:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-01-04 0:04 [pgnus v0.66] Recursive MIME problem Jack Twilley
1999-01-04 9:25 ` Kai.Grossjohann
1999-01-04 18:59 ` Jack Twilley
1999-01-11 1:03 ` Lars Magne Ingebrigtsen
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).