Gnus development mailing list
 help / color / mirror / Atom feed
From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: nnml groups showing up with '*' at startup
Date: Tue, 24 Nov 2015 21:48:39 +0100	[thread overview]
Message-ID: <87wpt79l94.fsf@free.fr> (raw)
In-Reply-To: <b4mpoyz4r46.fsf@jpl.org>

On Tue, Nov 24 2015, Katsumi Yamaoka wrote:

> A quick hack is attached below, although I don't want to install
> it because it will probably damage Gnus' speed.  Moreover, it
> won't be a fix to Peter's and Adam's problems; both don't seem to
> mention groups of non-ASCII names.

My problem is a very minor one: after a while, the tab-completion works,
it seems, that there is a list of group-names used by
gnus-group-completing-read that is not complete at start-up time, but
later groups are added to this list. After some uptime, it works...

But I agree: sometimes, there are issues with non-ASCII names (but I
don't remember what exactly...)

-- 
           Peter




  reply	other threads:[~2015-11-24 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 12:22 Adam Sjøgren
2015-11-22 19:08 ` Peter Münster
2015-11-22 19:18   ` Adam Sjøgren
2015-11-23  7:46 ` Michael Sperber
2015-11-23 18:02   ` Adam Sjøgren
2015-11-24  2:40     ` Katsumi Yamaoka
2015-11-24 10:40       ` Katsumi Yamaoka
2015-11-24 20:48         ` Peter Münster [this message]
2015-11-25  2:44           ` Katsumi Yamaoka
2015-11-25  8:02             ` Adam Sjøgren
2015-11-25  8:19               ` Katsumi Yamaoka
2015-11-25 10:08                 ` Adam Sjøgren
2015-12-02 22:02           ` groups with non-ASCII names (was: nnml groups showing up with '*' at startup) Peter Münster
2015-12-03  2:01             ` groups with non-ASCII names Katsumi Yamaoka
2015-12-03  8:13               ` Peter Münster
2015-11-29 12:12       ` nnml groups showing up with '*' at startup Michael Sperber

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=87wpt79l94.fsf@free.fr \
    --to=pmlists@free.fr \
    --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).