From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Li'l Feature Wish
Date: 27 Jul 1996 19:12:44 +0200 [thread overview]
Message-ID: <x691c5vcvn.fsf@eyesore.no> (raw)
In-Reply-To: Hallvard B Furuseth's message of Wed, 24 Jul 1996 19:02:26 +0200 (MET DST)
Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
> a) You didn't like a key to set threading from the *group* buffer -- is
> that because you'd have to duplicate a lot of *summar* things in the
> *group* buffer? If so, generalize: "K S keys" will execute "keys" on
> behalf of the next summary buffer to be entered (or it will be saved
> and executed *when* the next summary buffer is entered). K A -- for
> the next *article* buffer. K G -- for the "next" *group* buffer:-)
This is a very interesting idea... Hm. However, the `t' command in
the summary buffer regenerates the summary buffer, so `K S t' & `RET'
would enter the group, toggle threading, generate the summary buffer
and generate the summary buffer. Which isn't really a win. :-)
> b) A key (and possibly a per-group flag) to enter a group without
> threading, scoring and filling the summmary buffer.
`M-RET' bypasses all scoring, highlighting and stuff and should allow
as quick as possible summary buffer generation.
> Maybe it'd just show a single "article" named "get summary".
> Then we could set threading/scoring flags from the summary buffer
> and *then* push SPC to generate the summary.
That's a possibility. Hm, yes. Well, we don't even need that; we
could just have a general "(re)generate summary" command. Yes, I
think I like this one; I'll add it to the Red Gnus todo list.
> c) The same, but you don't enter the summary - you get the *article*
> buffer *without* summary. Then you can read news without a summary
> buffer, or you can do stuff on behalf of the group, and enter (thus
> generating) a summary.
That would require a total rewrite of Gnus, which might be a bit
excessive considering the gains to be had. :-)
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-07-27 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-04 9:03 Kai Grossjohann
1996-07-05 1:15 ` Lars Magne Ingebrigtsen
1996-07-05 17:02 ` Kai Grossjohann
1996-07-14 16:32 ` Lars Magne Ingebrigtsen
1996-07-15 16:55 ` Hallvard B Furuseth
1996-07-16 22:51 ` Lars Magne Ingebrigtsen
1996-07-24 17:02 ` Hallvard B Furuseth
1996-07-27 17:12 ` Lars Magne Ingebrigtsen [this message]
1996-07-17 6:30 ` Kai Grossjohann
1996-08-28 6:41 ` 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=x691c5vcvn.fsf@eyesore.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).