From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: 0.30 gives truncated images?
Date: 14 Sep 1998 15:36:05 +0200 [thread overview]
Message-ID: <m3sohug6ka.fsf@sparky.gnus.org> (raw)
In-Reply-To: Lee Willis's message of "14 Sep 1998 12:09:34 +0100"
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
next prev parent reply other threads:[~1998-09-14 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-14 11:09 Lee Willis
1998-09-14 13:36 ` Lars Magne Ingebrigtsen [this message]
1998-09-14 14:42 ` Lee Willis
1998-09-14 15:54 ` Lars Magne Ingebrigtsen
1998-09-14 15:02 ` Vladimir Volovich
1998-09-14 15:27 ` Lee Willis
1998-09-14 20:41 ` Paul Fisher
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=m3sohug6ka.fsf@sparky.gnus.org \
--to=larsi@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).