From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Recent nnir update broke search on office365
Date: Sun, 01 Feb 2015 09:40:28 +0800 [thread overview]
Message-ID: <87r3ua9zoz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <84386qhoxj.fsf@davestoy.home>
david.goldberg6@verizon.net (Dave Goldberg) writes:
> All searches come up empty since this commit (per git-bisect)
>
> 046825b09ff6e23ec7dfacd451d10985615b9793 is the first bad commit
> commit 046825b09ff6e23ec7dfacd451d10985615b9793
> Author: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Tue Jan 27 16:35:25 2015 +1100
>
> * nnir.el (nnir-run-imap): Enable non-ASCII IMAP searches.
>
> :040000 040000 5131b4d4212b134d58fdaec4481a41239a69926c
> e22212e758aa6a15e13c23ec8fb00f65bcf3a741 M lisp
>
> I should have thought to check my other server (cyrus) - I can do so
> when I get back to work next week. I'm happy to help troubleshoot but
> need guidance on what to look for.
Yeah, this probably wasn't quite ready. There are a couple of other
problems with that patch that I'm looking at now, and hopefully I'll be
able to come up with something that addresses this as well, if I can
figure out what office365 is doing for encoding. If you have any hints
in that direction, let me know! Sorry for the breakage...
E
next prev parent reply other threads:[~2015-02-01 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 16:53 Dave Goldberg
2015-02-01 1:40 ` Eric Abrahamsen [this message]
2015-02-01 6:22 ` Eric Abrahamsen
2015-02-03 11:49 ` Eric S Fraga
2015-02-03 13:01 ` Eric Abrahamsen
2015-02-03 15:57 ` e.fraga
2015-02-03 23:21 ` Dave Goldberg
2015-02-04 3:02 ` Eric Abrahamsen
2015-02-04 10:30 ` Eric S Fraga
2015-02-04 0:15 ` Katsumi Yamaoka
2015-02-04 3:30 ` Eric Abrahamsen
2015-02-04 18:28 ` Andreas Schwab
2015-02-05 1:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3ua9zoz.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).