From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: New summary part commands?
Date: Mon, 17 Feb 2003 14:39:05 +0100 [thread overview]
Message-ID: <84of5bvxfq.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
I've added a MIME/Multipart submenu in the summary buffers, but I'm
afraid a number of commands there are less useful than they could
be. In particular, the *-part commands require a prefix arg, I
think. Users using the menu bar will probably surprised by this.
Idea: Change the commands to read the part number from the minibuffer
if no prefix arg is provided.
Idea: For each command, make a (dynamic) submenu that lists the parts.
What do you think? Other ideas?
--
A turnip curses Elvis
next reply other threads:[~2003-02-17 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 13:39 Kai Großjohann [this message]
2003-02-19 18:12 ` Reiner Steib
2003-02-19 19:07 ` Kai Großjohann
2003-02-19 20:20 ` Should gnus-summary-repair-multipart modify files on disk? (was: New summary part commands?) Reiner Steib
2003-02-20 11:53 ` Should gnus-summary-repair-multipart modify files on disk? Kai Großjohann
2003-02-19 20:43 ` New summary part commands? Reiner Steib
2003-02-20 10:27 ` Kai Großjohann
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=84of5bvxfq.fsf@lucy.is.informatik.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).