From: Lee Willis <lee@gbdirect.co.uk>
Subject: Bug/feature with pgnus 0.40
Date: 28 Oct 1998 14:33:29 +0000 [thread overview]
Message-ID: <lz67d4rc1y.fsf@landlord.gbdirect.co.uk> (raw)
With pgnus 0.40 under Emacs 20.3 I get the following behaviour.
I receive a message with two text/plain parts (Parts 1 and 3.) and an
image/jpeg part (Part 2). So I hit 2 b to view the image part which is
displayed externally using xv. All very well except that my article
buffer has changed so that the button for this part is now at the top,
meaning I can no longer see the text of the first text part without
hitting either g to redisplay the article or C-x o'ing and moving up.
IMHO It'd would be nicer if the article buffer didn't move *if* the MIME
part is handled externally ie not inline.
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next reply other threads:[~1998-10-28 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-28 14:33 Lee Willis [this message]
1998-10-29 11:06 ` 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=lz67d4rc1y.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).