Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Cleaning up bogus completion buffers [was newsgroups]
Date: 20 Dec 2000 01:17:10 -0800	[thread overview]
Message-ID: <m24rzzsb8p.fsf@gnus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: ShengHuo ZHU's message of "20 Dec 2000 00:36:58 -0500"

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> > 
> > > You could browse the server to find out new groups.  
> > > 
> > > Now, I've changed the behavior of `C-k', that is, if a group is killed
> > > twice, it will no longer be in gnus-killed-list.
> > 
> > A related question:  I've had occasion to misstype an entry when
> > using `j' to jump to a group.
> > 
> > Imagine ... you type  `j' nnml:newestgroup  and you really meant
> > nnml:newergroup.
> > 
> > The result will be that a killed group with the mistaken name is
> > created at the bottom of group buffer.  Ok.. fine, you can kill it
> > again.
> > 
> > Now here's the rub.  That mistaken, twice killed group is now included
> > in completion buffers.
> 
> Now fixed.  Only for twice killed groups.

Cooool

If its not pushing my luck to far.....

Were does the contents of completion buffers get generated.
Can it be edited some how?




  reply	other threads:[~2000-12-20  9:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06  2:02 Cleaning up bogus newsgroups from newsrc.eld Jake Colman
2000-12-06  2:10 ` ShengHuo ZHU
2000-12-06 14:41   ` Jake Colman
2000-12-07 18:51     ` Paul Jarc
2000-12-20  2:59     ` ShengHuo ZHU
2000-12-20  3:40       ` Cleaning up bogus completion buffers [was newsgroups] Harry Putnam
2000-12-20  5:36         ` ShengHuo ZHU
2000-12-20  9:17           ` Harry Putnam [this message]
2000-12-20 14:14             ` ShengHuo ZHU

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=m24rzzsb8p.fsf@gnus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.com \
    --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).