From: jdc@chow.mat.jhu.edu (Dan Christensen)
Subject: Re: jump and select
Date: Sun, 01 Mar 1998 12:01:28 -0500 [thread overview]
Message-ID: <x7vhtyjqfr.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Mar 1998 13:57:25 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> jdc@chow.mat.jhu.edu (Dan Christensen) writes:
>
> > The following patch adds an optional argument to
> > gnus-group-jump-to-group which asks it to select the group it is
> > jumping to. So if the user types `C-u j', he or she will be
> > prompted for a group-name which will then be selected.
>
> I don't really think this is something that will be used much. `j
> GROUP RET RET' is faster than `C-u j GROUP RET'.
Actually, I bind this functionality to the `J' key. And what turns
out to be quite handy is to have this available in the Summary buffer
as well. (To make binding easier, the implementation I gave should be
changed so that there is a function gnus-group-select-a-group, instead
of mixing it into gnus-group-jump-to-group. See below.)
Since Gnus is designed for reading groups, I thought that a keystroke
devoted to selecting a group whose name is supplied by the user would
be useful. But if you don't like it, I'll just put it in my .gnus.
Dan
(defun gnus-group-select-a-group (group &optional all)
"Select newsgroup GROUP.
Interactively, query for group name with completion.
No article is selected automatically.
If ALL is non-nil, already read articles become readable.
If ALL is a number, fetch this number of articles."
(interactive
(list (completing-read
"Group: " gnus-active-hashtb nil
(gnus-read-active-file-p)
nil
'gnus-group-history)
current-prefix-arg))
(when (equal group "")
(error "Empty group name"))
(gnus-group-read-group all t group))
prev parent reply other threads:[~1998-03-01 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-28 21:19 Dan Christensen
1998-03-01 12:57 ` Lars Magne Ingebrigtsen
1998-03-01 17:01 ` Dan Christensen [this message]
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=x7vhtyjqfr.fsf@chow.mat.jhu.edu \
--to=jdc@chow.mat.jhu.edu \
/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).