Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: New prefix
Date: 21 Sep 1997 05:09:02 +0200	[thread overview]
Message-ID: <m27mcbl5wx.fsf@proletcult.slip.ifi.uio.no> (raw)

Ok; so I want to add a new prefix.  We already have the normal prefix
-- `C-u' and friends, but in some cases we need an additional prefix.

For instance, the `L' command(s) use the numerical prefix to say how
much to lower the score, and that works fine.  But there are
additional common modifications to the behavior of those commands that
would be nice to have.  For instance, if would be nice if I could tap
a prefix key to make the score command result with a score entry in
"all.SCORE" instead of the current score file.

The machanism has to be somewhat general.  I'm thinking along the
lines of `M-C-u b COMMAND' would give COMMAND the symbolic `b' prefix,
which COMMAND is fit to interpret is it chooses, just as the case is
with the numerical prefix.  I'll be adding a new macro to make these
easy to deal with, and things'll look somewhat like this:

(defun gnus-some-function (&optional arg syms)
  (gnus-interactive "P\nG")
  (let ((prefix-p (memq 'a syms)))
    ... ))

"G" would give a list of symbolic prefixes, and "g" would give one;
the first.

In the former case, the user could say `M-C-u a M-C-u b COMMAND'
to give COMMAND both the `a' and `b' prefixes.

Not all that many commands would need these symbolic prefixes, but a
few commands scream out for something like this.  For instance,
`M-C-u a S o m' to forward something with complete headers.

Reactions?  Good?  Bad?  Use some other prefix key?  What?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Magne Ingebrigtsen


             reply	other threads:[~1997-09-21  3:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-21  3:09 Lars Magne Ingebrigtsen [this message]
1997-09-21 13:10 ` Per Abrahamsen
1997-09-21 16:33   ` 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=m27mcbl5wx.fsf@proletcult.slip.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).