From: Dan Christensen <jdc@uwo.ca>
To: info-gnus-english@gnu.org
Subject: Re: Any way to click article buttons without leaving the summary buffer?
Date: Thu, 06 Jan 2011 09:52:27 -0500 [thread overview]
Message-ID: <87lj2yxexg.fsf@uwo.ca> (raw)
In-Reply-To: <8762u33780.fsf@nzebook.haselwarter.org>
Philipp Haselwarter <philipp.haselwarter@gmx.de> writes:
> On Tue, 04 Jan 2011 09:25:46 -0500, Dan Christensen <jdc@uwo.ca> said:
>
> DC> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>>> Sounds nice. Perhaps TAB in the summary buffer should highlight the
>>> links successively? And then RET could "click the link".
>
> DC> Isn't that essentially what TAB already does? (But not just for
> DC> links; it includes any widget; which I think is the right thing to
> DC> do.)
> DC>
> DC> | <tab> runs the command gnus-summary-widget-forward, which is an
> DC> | interactive compiled Lisp function in `gnus-sum.el'.
>
> It would just be nice to be able to do that from the summary buffer.
It *does* do that in the summary buffer. Note that the command is
called gnus-summary-widget-forward, and is defined in gnus-sum.el.
This may be a recent change. Until a month or two ago, TAB used to
process-mark articles for me, but now it does the above. I'm using
git gnus.
Dan
next prev parent reply other threads:[~2011-01-06 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 23:14 Sean McAfee
2011-01-02 7:13 ` Lars Magne Ingebrigtsen
2011-01-04 0:57 ` Sean McAfee
2011-01-04 1:10 ` Lars Magne Ingebrigtsen
2011-01-04 14:25 ` Dan Christensen
2011-01-05 11:44 ` Philipp Haselwarter
2011-01-06 14:52 ` Dan Christensen [this message]
2011-01-04 22:05 ` Peter Münster
[not found] ` <mailman.1.1294151194.4785.info-gnus-english@gnu.org>
2011-01-11 19:55 ` Lars Magne Ingebrigtsen
2011-01-02 12:17 ` Sean Sieger
2011-01-02 12:27 ` Sean Sieger
2011-01-02 14:35 ` Peter Münster
2011-01-04 9:27 ` Peter Münster
[not found] ` <mailman.4.1293971110.4418.info-gnus-english@gnu.org>
2011-01-04 0:39 ` Sean McAfee
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=87lj2yxexg.fsf@uwo.ca \
--to=jdc@uwo.ca \
--cc=info-gnus-english@gnu.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).