From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: what's wrong in gnus-topic-mode with nnimap?
Date: Mon, 10 Mar 2014 13:03:42 +0800 [thread overview]
Message-ID: <87zjkytzkh.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874n36ito4.fsf@126.com>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
Easior Lars <easior@126.com> writes:
>>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> >> It is annoying that this group can't be deleted by 'G+DEL'.
>
> LI> Just kill it with `C-k'. Gmail is reporting a group that doesn't exist.
> `c-k' does not take effects. In fact, this group will appear again
> after gnus restarts next time.
> LI> --
> LI> (domestic pets only, the antidote for overdose, milk.)
> LI> bloggy blog http://lars.ingebrigtsen.no/
It's possible that you're seeing something that I ran into a while
earlier. When `nnimap-get-groups' is called, to retrieve all the names
of the groups on the server, it sometimes reads the group names
incorrectly if they have characters that confuse the call to `read'. Try
edebugging nnimap-get-groups and stepping through it until the response
comes back from the LIST command, then look at the buffer and see what's
there. It's possible a group name is being read incorrectly.
It's also just possible that gnus is somehow barfing on the imaginary
"[Gmail]" group that gmail likes to make. But I was able to visit the
server's group list from the *Server* buffer and just kill the group
there, as Lars mentioned.
If it's really mis-reading the group name, you can try fooling with the
local patch I use, which is ugly and probably highly dangerous for
reasons I haven't thought of, but at least Works For Me:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-server-fix.patch --]
[-- Type: text/x-diff, Size: 762 bytes --]
1 file changed, 6 insertions(+), 1 deletion(-)
lisp/nnimap.el | 7 ++++++-
Modified lisp/nnimap.el
diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 1730bd4..4e07495 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -1230,7 +1230,12 @@ If LIMIT, first try to limit the search to the N last articles."
(while (search-forward "* LIST " nil t)
(let ((flags (read (current-buffer)))
(separator (read (current-buffer)))
- (group (read (current-buffer))))
+ (group (buffer-substring-no-properties
+ (progn (skip-chars-forward " \"")
+ (point))
+ (progn (move-end-of-line 1)
+ (skip-chars-backward " \"
")
+ (point)))))
(unless (member '%NoSelect flags)
(push (utf7-decode (if (stringp group)
group
prev parent reply other threads:[~2014-03-10 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 3:27 Easior Lars
2014-03-09 15:33 ` Lars Ingebrigtsen
2014-03-10 4:06 ` Easior Lars
2014-03-10 5:03 ` Eric Abrahamsen [this message]
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=87zjkytzkh.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).