From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: How do I interrupt attachment downloading over imap?
Date: Wed, 30 Oct 2002 11:17:32 +0100 [thread overview]
Message-ID: <84k7k06xj7.fsf@crybaby.uni-duisburg.de> (raw)
In-Reply-To: <ubs5cxtv8.fsf@axis.com>
Niklas Morberg <niklas.morberg@axis.com> writes:
> Hm. I don't have an nnimap server buffer. What should I do
> to make it appear (so that I later kan kill it and stop the
> download). Or did I misunderstand something here?
Maybe the buffer name starts with space. You have to use C-x b to
switch to it, the other ways will hide buffer names starting with space.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-30 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 9:30 Niklas Morberg
2002-10-23 13:57 ` Wes Hardaker
2002-10-23 21:11 ` Simon Josefsson
2002-10-30 7:34 ` Niklas Morberg
2002-10-30 10:17 ` Kai Großjohann [this message]
2002-10-30 10:58 ` Niklas Morberg
2002-10-30 11:20 ` Kai Großjohann
2002-10-30 12:40 ` dme
2002-10-30 14:44 ` Niklas Morberg
2002-10-23 21:09 ` Simon Josefsson
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=84k7k06xj7.fsf@crybaby.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).