Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Fancy completion
Date: Tue, 31 Aug 2010 08:13:24 +0200	[thread overview]
Message-ID: <87iq2rs41n.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87lj7oedg9.fsf@topper.koldfront.dk>

On Mon, Aug 30 2010, Adam Sjøgren wrote:

> It certainly would; I have skipped using j many times, because I was too
> lazy to type nntp+blahblah before getting to the part that I cared
> about.

Did you try `gnus-group-jump-to-group-prompt'?

,----[ <f1> f gnus-group-jump-to-group RET ]
| gnus-group-jump-to-group is an interactive compiled Lisp function in
| `gnus-group.el'.
| (gnus-group-jump-to-group GROUP &optional PROMPT)
| 
| Jump to newsgroup GROUP.
| 
| If PROMPT (the prefix) is a number, use the prompt specified in
| `gnus-group-jump-to-group-prompt'.
`----

,----[ <f1> v gnus-group-jump-to-group-prompt RET ]
| gnus-group-jump-to-group-prompt is a variable defined in `gnus-group.el'.
| Its value is shown below.
| 
| Documentation:
| Default prompt for `gnus-group-jump-to-group'.
| 
| If non-nil, the value should be a string or an alist.  If it is a string,
| e.g. "nnml:", in which case `gnus-group-jump-to-group' offers "Group:
| nnml:" in the minibuffer prompt.
| 
| If it is an alist, it must consist of (NUMBER .  PROMPT) pairs, for example:
| ((1 .  "") (2 .  "nnfolder+archive:")).  The element with number 0 is
| used when no prefix argument is given to `gnus-group-jump-to-group'.
| 
| You can customize this variable.
| 
| Value: 
| ((0 "")
|  (1 "nnml+personal:")
|  (2 "nnml+news:")
|  (3 "nnml+archive:")
|  (11 "nnimap+foo:")
|  (12 "nnimap+bar:INBOX")
|  (21 "gmane."))
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  parent reply	other threads:[~2010-08-31  6:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  2:54 Lars Magne Ingebrigtsen
2010-08-30  3:07 ` Leo
2010-08-30  3:12   ` Lars Magne Ingebrigtsen
2010-08-30  3:18     ` Lars Magne Ingebrigtsen
2010-08-30  3:44     ` Leo
2010-08-30 16:25       ` Lars Magne Ingebrigtsen
2010-08-30  3:08 ` Leo
2010-08-30  8:01 ` Adam Sjøgren
2010-08-30 19:54   ` Andreas Schwab
2010-08-30 19:59     ` Adam Sjøgren
2010-08-30 20:45       ` Andreas Schwab
2010-08-31  2:07         ` Eric Abrahamsen
2010-08-31  6:13   ` Reiner Steib [this message]
2010-08-31 21:12     ` Adam Sjøgren
2010-08-31 23:19       ` Andreas Schwab
2010-08-31 23:29         ` Lars Magne Ingebrigtsen
2010-08-30 12:19 ` Julien Danjou
2010-08-30 16:26   ` Lars Magne Ingebrigtsen
2010-08-30 16:33     ` Julien Danjou
2010-08-30 16:43       ` Lars Magne Ingebrigtsen
2010-08-30 17:03         ` Leo
2010-08-30 17:16         ` Adam Sjøgren
2010-08-30 17:19           ` Lars Magne Ingebrigtsen
2010-08-30 17:21             ` Leo
2010-08-30 17:42               ` Adam Sjøgren
2010-08-30 17:38             ` Adam Sjøgren
2010-08-30 17:45               ` Leo
2010-08-30 17:53                 ` Lars Magne Ingebrigtsen
2010-08-30 18:22                 ` Adam Sjøgren

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=87iq2rs41n.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    /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).