0.30 gives truncated images?

0.30 gives truncated images?

[Lee Willis]

Well firstly I love pgnus so far, it's so nice not to have to resend
myself messages and start pine to catch them :)  The only
problems/suggestions I have now are

a)When compiling ...

While compiling base64-decode in file /home/lee/lib/emacs/site-lisp/pgnus/pgnus-0.30/lisp/base64.el:
** function base64-decode used to take 0+ arguments, now takes 1

b) Would it be possible/nice to have the size of an attachment shown in
it's button and/or the comment associated with an attachment shown in a
button.

c) When displaying images (via xv) I always get a message saying that
the file is truncated and I'm missing around a line and a half of pixels
off the bottom of the images ... :(

d) When should external viewers/players (Whatever ..) quit. In other
words I view a message with an attached gif which is automatically
displayed, but if I quit the summary buffer without reading another
message xv hangs around until I read another message, could
gnus-summary-exit possibly kill the viewer?

Other than that it's all working bootifully :)

Cheers,
Lee.
-- 
Lee Willis
GBDirect Ltd, 27 Park Drive, Heaton, Bradford, UK, BD9 4DS
Tel: +44 (0)1274 772277

Re: 0.30 gives truncated images?

[Lars Magne Ingebrigtsen]

Lee Willis <lee@gbdirect.co.uk> writes:

> While compiling base64-decode in file /home/lee/lib/emacs/site-lisp/pgnus/pgnus-0.30/lisp/base64.el:
> ** function base64-decode used to take 0+ arguments, now takes 1

Hm.  Possibly fixed in 0.31.

> b) Would it be possible/nice to have the size of an attachment shown in
> it's button and/or the comment associated with an attachment shown in a
> button.

I've now added a %l spec to gnus-mime-button-line-format.

> c) When displaying images (via xv) I always get a message saying that
> the file is truncated and I'm missing around a line and a half of pixels
> off the bottom of the images ... :(

I don't get this...  Are you sure that the articles aren't missing the 
bottom half?  :-)

> d) When should external viewers/players (Whatever ..) quit. In other
> words I view a message with an attached gif which is automatically
> displayed, but if I quit the summary buffer without reading another
> message xv hangs around until I read another message, could
> gnus-summary-exit possibly kill the viewer?

Yes, that is what is supposed to happen, and what happens when I try
it.  Are the xv's always not killed, or just sometimes?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: 0.30 gives truncated images?

[Lee Willis]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Lee Willis <lee@gbdirect.co.uk> writes:
> 
> > c) When displaying images (via xv) I always get a message saying that
> > the file is truncated and I'm missing around a line and a half of pixels
> > off the bottom of the images ... :(
> 
> I don't get this...  Are you sure that the articles aren't missing the 
> bottom half?  :-)

Well I know the original images aren't. I did theorize that perhaps pine
wasn't encoding them properly so I tried sending stuff from (Yuck)
Netscrape and short of the fact that I'm stillr ecovering from the
experience that didn't work either :(  Anything else you'd like me to
check ?

> Yes, that is what is supposed to happen, and what happens when I try
> it.  Are the xv's always not killed, or just sometimes?

As far as I can tell they always hang around until I read another
message, but I'll do some more research ...

[5 minutes later (Ain't nndraft grand!)]

Well it appears that they do always hang around. In fact I can quit gnus
and then restart it (Without killing the parent emacs) and the xv(s)
still hang around :(

On the image truncation front, I've just tried sending myself two images
that had given me problems before and this time one of the images is
fine, the other has problems similar to before ... Would you like me to
send you the images to see how they are for you?

Cheers,
Lee.
-- 
Lee Willis
GBDirect Ltd, 27 Park Drive, Heaton, Bradford, UK, BD9 4DS
Tel: +44 (0)1274 772277

Re: 0.30 gives truncated images?

[Vladimir Volovich]

"LMI" == Lars Magne Ingebrigtsen writes:

 LMI> Yes, that is what is supposed to happen, and what happens when I
 LMI> try it.  Are the xv's always not killed, or just sometimes?

They seem to be killed (for me; i use xv to display x-faces) when i
change the article, but when i leave the summary buffer (q) and go to
the group buffer, xv's remain unkilled.

	Best regards, -- Vladimir.

Re: 0.30 gives truncated images?

[Lee Willis]

Vladimir Volovich <vvv@vvv.vsu.ru> writes:

> "LMI" == Lars Magne Ingebrigtsen writes:
> 
>  LMI> Yes, that is what is supposed to happen, and what happens when I
>  LMI> try it.  Are the xv's always not killed, or just sometimes?
> 
> They seem to be killed (for me; i use xv to display x-faces) when i
> change the article, but when i leave the summary buffer (q) and go to
> the group buffer, xv's remain unkilled.

Oh yeah, my xface's remain unkilled as well but I don't really mind that
that much since they're so small and 99.9% of the time are guaranteed
not to be obstructed any of my desktop, 200x200 GIFs on the other hand
...

Lee.
-- 
Lee Willis
GBDirect Ltd, 27 Park Drive, Heaton, Bradford, UK, BD9 4DS
Tel: +44 (0)1274 772277

Re: 0.30 gives truncated images?

[Lars Magne Ingebrigtsen]

Lee Willis <lee@gbdirect.co.uk> writes:

> As far as I can tell they always hang around until I read another
> message, but I'll do some more research ...

Yup.  Fix in Pterodactyl Gnus v0.31.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: 0.30 gives truncated images?

[Paul Fisher]

Lee Willis <lee@gbdirect.co.uk> writes:

> c) When displaying images (via xv) I always get a message saying
> that the file is truncated and I'm missing around a line and a half
> of pixels off the bottom of the images ... :(

multipart MIME messages were improperly decoded with pgnus < 0.31.
The last line of any encoded part was ignored.  So for text/plain,
usually the last sentence or so would be truncated... For images, I
assume this type of behavior would occur.

pgnus 0.31 should fix your problems.

-- 
Paul Fisher * rao@gnu.org
.