Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: nnml groups showing up with '*' at startup
Date: Tue, 24 Nov 2015 19:40:57 +0900	[thread overview]
Message-ID: <b4mpoyz4r46.fsf@jpl.org> (raw)
In-Reply-To: <b4mlh9oxgp0.fsf@jpl.org>

On Tue, 24 Nov 2015 11:40:59 +0900, Katsumi Yamaoka wrote:
>> --- a/lisp/nnml.el
>> +++ b/lisp/nnml.el
>> -(deffoo nnml-retrieve-groups (groups &optional server)
>> -  (when nnml-get-new-mail
>> -    (if (nnmail-get-new-mail-per-group)
[...]

> Removing this made Gnus work as before, too.  So far I don't
> know why/how it does wrong,

As for at least a non-ASCII group name like "nnml:テスト" I found
the cause of the problem.

・Gnus uses an encoded group name of the unibyte version to access
  that group.  By default utf-8 is used for encoding, i.e.:
  "nnml:テスト" -> "nnml:\343\203\206\343\202\271\343\203\210"
・`nnml-retrieve-groups' inserts an encoded group name to the
  `nntp-server-buffer', in which the multibyteness is turned on.
・`gnus-groups-to-gnus-format' reads it using `read'.  Because
  the multibyteness is turned on, the result will be a symbol of
  the multibyte version, and the active info will be created in
  `gnus-active-hashtb' with a multibyte group name.  That cannot
  be accessed by Gnus.

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.

> but I think we should remove it if
> it is nonessential and nonurgent.  The function has already been
> in the emacs-25 branch (for releasing Emacs 25.1).

> WDYT Michael?

--- gnus-start.el~	2015-10-01 01:52:23.531908800 +0000
+++ gnus-start.el	2015-11-24 10:38:38.449503300 +0000
@@ -2256,8 +2256,10 @@
 		    (skip-chars-forward " \t")
 		    (insert prefix)
 		    (goto-char opoint)
-		    (set (let ((obarray hashtb)) (read cur))
-			 (cons min max)))
+		    (gnus-sethash
+		     (string-as-unibyte (symbol-name (read cur)))
+		     (cons min max)
+		     hashtb))
 		(error (and group (symbolp group) (set group nil))))
 	      (forward-line 1)))
 	(let (min max group)



  reply	other threads:[~2015-11-24 10:40 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 [this message]
2015-11-24 20:48         ` Peter Münster
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=b4mpoyz4r46.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).