Gnus development mailing list
 help / color / mirror / Atom feed
From: posting-list@mailAndnews.com (Jari Aalto+mail.emacs)
Subject: Re: Feature request: Show dormants when entering group
Date: 07 Jan 2001 16:51:13 +0200	[thread overview]
Message-ID: <wkzoh4k22h.fsf@blue.sea.net> (raw)
In-Reply-To: <m3ae95z5av.fsf@gnus-5.8.8-cvs.now.playing>

* 2001-01-05 Harry Putnam <reader@newsguy.com> list.emacs-ding
* Message-Id: <m3ae95z5av.fsf@gnus-5.8.8-cvs.now.playing>
| Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
| 
| > jari.aalto@poboxes.com (Jari Aalto+mail.emacs) writes:
| > 
| > > I use dormants for "todo" entries and not really for what they
| > > are orgiinally menat for. This means, that I always like to see
| > > the buffer generated with dormant, but in current gnus that is not
| > > possible.
| > 
| > Uhm -- the only essential difference between dormant and ticked
| > articles is that dormant articles aren't shown (unless they have
| > follow-ups).  So what don't you just tick the articles instead?
| 
| Another thing... I haven't tested it thoroughly but I think if you
| press `/ D' in a group, it will still show dormant the next time you
| enter too.  That is, press  `/ D', close the group, come back later
| and reopen it... dormant will be displayed. 

But that's a second hand solution. Pressing / will re-generate whole
buffer, imagine 200 + articles, even more....

And pressing / D in every 20 groups when I launch gnus.

I would really like Gnus to allow showing dormants in the fist
buffer creation pass. 

And this is easy to implement, if I get permission to muck the
code and make a patch.

Jari




  reply	other threads:[~2001-01-07 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 23:23 Jari Aalto+mail.emacs
2001-01-06  0:57 ` Lars Magne Ingebrigtsen
2001-01-06  4:13   ` Harry Putnam
2001-01-07 14:51     ` Jari Aalto+mail.emacs [this message]
2001-01-07 14:51   ` Jari Aalto+mail.emacs
2001-01-07 19:24     ` Kai Großjohann
2001-01-06 12:53 ` Kai Großjohann
2001-01-07 10:18 ` Paul Stevenson

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=wkzoh4k22h.fsf@blue.sea.net \
    --to=posting-list@mailandnews.com \
    /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).