From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: gnus-diary key binding request
Date: Sat, 09 Apr 2005 18:45:19 +0200 [thread overview]
Message-ID: <v964yv99wg.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87sm20owa8.fsf@denkblock.local>
On Sat, Apr 09 2005, Elias Oltmanns wrote:
> wouldn't it be sensible to have gnus-article-edit bound to a key in an
> nndiary group?
Isn't `e' (gnus-summary-edit-article) sufficient?
,----[ `C-h k e' ]
| e runs the command gnus-summary-edit-article
| which is an interactive compiled Lisp function in `gnus-sum'.
| It is bound to e, B w, <menu-bar> <Article> <Copy,
| move,... (Backend)> <Edit article>.
| (gnus-summary-edit-article &optional arg)
|
| Edit the current article.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-04-09 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 14:32 Elias Oltmanns
2005-04-09 16:45 ` Reiner Steib [this message]
2005-04-09 18:48 ` Elias Oltmanns
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=v964yv99wg.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).