unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Andreas Schwab <schwab@suse.de>,
	Nikolaus Rath <nikolaus@rath.org>,
	21057@debbugs.gnu.org
Subject: bug#21057: [PATCH] nnimap.el: add support for IMAP namespaces
Date: Sun, 22 Jul 2018 23:00:56 -0700	[thread overview]
Message-ID: <87in56h4o7.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m336wbqtwf.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 22 Jul 2018 15:31:12 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Nikolaus Rath <nikolaus@rath.org> writes:
>
>> Updated patches attached (and rebased onto current master).
>
> Sorry for the delays; I've now applied your patches to Emacs master.

This raises an error for me when Gnus starts.

`nnimap-retrieve-group-data-early' calls `nnimap-group-to-imap', which
does:

(substring nnimap-namespace 0 -1)

`nnimap-namespace' is nil, so an error is raised.

What's supposed to happen?

Eric





  reply	other threads:[~2018-07-23  6:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87si8qjhca.fsf@vostro.rath.org>
2017-01-26 19:40 ` bug#21057: [PATCH] nnimap.el: add support for IMAP namespaces Lars Ingebrigtsen
2017-09-05 15:18 ` Nikolaus Rath
2017-09-05 15:26   ` Nikolaus Rath
2017-09-05 15:36     ` Andreas Schwab
2017-09-07 16:01       ` Nikolaus Rath
2017-09-13 17:30         ` Lars Ingebrigtsen
2017-09-17  8:16           ` Nikolaus Rath
2017-12-06 14:25             ` Nikolaus Rath
2017-12-27 21:10             ` Lars Ingebrigtsen
2018-05-31 11:38               ` Nikolaus Rath
2018-07-03  7:40                 ` Nikolaus Rath
2018-07-07  9:12                   ` Eli Zaretskii
2018-07-17 19:43                     ` Nikolaus Rath
2018-07-20  9:43                       ` Eli Zaretskii
2018-07-20 19:16                         ` Nikolaus Rath
2018-07-20 19:50                           ` Eli Zaretskii
2018-07-22 13:31                 ` Lars Ingebrigtsen
2018-07-23  6:00                   ` Eric Abrahamsen [this message]
2018-07-23  7:03                     ` Lars Ingebrigtsen
2018-07-23  7:22                       ` Nikolaus Rath
2018-07-23  7:39                         ` Lars Ingebrigtsen
2018-07-23  8:58                           ` Nikolaus Rath
2018-07-23  9:00                             ` Lars Ingebrigtsen
2018-07-23  9:01                             ` Lars Ingebrigtsen
2018-07-23  9:53                               ` Nikolaus Rath
2018-07-23 11:28                                 ` Robert Pluim
2018-07-23 18:00                                   ` Nikolaus Rath
2018-07-27  7:54                                     ` Nikolaus Rath
2018-08-05  9:54                                       ` Nikolaus Rath
2018-08-11  7:49                                         ` Eli Zaretskii
2018-07-23 16:47                                 ` Eric Abrahamsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87in56h4o7.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=21057@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=nikolaus@rath.org \
    --cc=schwab@suse.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).