From: "T.V Raman" <raman@google.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: NNSelect Failing
Date: Thu, 17 Dec 2020 12:59:18 -0800 [thread overview]
Message-ID: <p91wnxgup21.fsf@google.com> (raw)
In-Reply-To: <87wnxgs73v.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 17 Dec 2020 08:57:40 -0800")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1245 bytes --]
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> "T.V Raman" <raman@google.com> writes:
p.s. gnus-verbose is presently 6.
Also in what you wrote, <cite>
> Or maybe first make sure it works with `gnus-search-use-parsed-queries'
> set to nil, and plain IMAP search strings?
</cite>
What exactly did you intend to say re plain imap string?
>
>> So as an example:
>>
>> In the groups buffer,
>> If I search for
>> from: rms after: 2020/01/01
>
> If this is the exact query you're issuing, there shouldn't be spaces
> after the colons.
>
> Or maybe first make sure it works with `gnus-search-use-parsed-queries'
> set to nil, and plain IMAP search strings?
>
>> for the emacs-devel mail archive (personal gmail) using imap, emacs
>> 28.0.50 no longer returns anything; more generally, all queries report
>> a message of the form:
>>
>> Group nnselect:nnselect-p91v9d01j5e.fsf contains no messages
>
> There's an ongoing issue wherein nnselect downgrades all errors to
> warnings, and returns this result if anything goes wrong. If you turn
> gnus-verbose up a bit (I think above 3) and try again, there might be
> real errors in *Messages*.
>
>
--
Thanks,
--Raman
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2020-12-17 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 16:41 NNSelect Failing T.V Raman
2020-12-17 16:57 ` Eric Abrahamsen
2020-12-17 20:57 ` T.V Raman
2020-12-17 20:59 ` T.V Raman [this message]
2020-12-17 21:05 ` Eric Abrahamsen
2020-12-17 21:18 ` T.V Raman via Emacs development discussions.
2020-12-17 22:19 ` Eric Abrahamsen
2020-12-18 1:42 ` T.V Raman
2020-12-18 3:44 ` Eric Abrahamsen
2020-12-18 15:40 ` T.V Raman
2020-12-18 15:58 ` T.V Raman
2020-12-18 16:04 ` T.V Raman
2020-12-18 17:44 ` Eric Abrahamsen
2020-12-18 18:50 ` T.V Raman
2020-12-18 20:03 ` Eric Abrahamsen
2020-12-19 0:03 ` Andrew Cohen
2020-12-19 1:44 ` T.V Raman
2020-12-19 2:12 ` Andrew Cohen
2020-12-19 15:08 ` T.V Raman
2020-12-18 17:40 ` 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=p91wnxgup21.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).