From: "T.V Raman" <raman@google.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: NNSelect Failing
Date: Fri, 18 Dec 2020 07:40:27 -0800 [thread overview]
Message-ID: <p91sg83t95g.fsf@google.com> (raw)
In-Reply-To: <874kkjixqi.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 17 Dec 2020 19:44:53 -0800")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1274 bytes --]
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Hi Eric, Will give it a shot, but here's why I am reluctant:
emacspeak is released code and I and quite a few users run directly from
Git@HEAD.
But not all users build their emacs every few days:-) -- so trying out
the new API risks breaking users.
> "T.V Raman" <raman@google.com> writes:
>
>> I'm going to attach my gm-nnir.el module here so you can use it in
>> testing.
>
> Turns out it was a relatively simple bug that was preventing your
> library from working, so that's already fixed.
>
> I have a larger patch underway for providing the previous behavior of
> setting `nnir-imap-default-search-key' to "gmail". But if you're using
> your own functions here, that won't have much effect on you.
>
> I know your library is working perfectly well, and email more than most
> things is a case of "if it ain't broke¡", but if you have a moment I
> encourage you to try out the new search syntax. It provides completion
> on search keys, so much of the same benefit as
> `gm-nnir-read-imap-clause', as well as "or" statements, and nice things
> like shorthands for relative dates, etc.
>
> Give it a shot!
>
> Eric
>
>
--
Thanks,
--Raman
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2020-12-18 15:40 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
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 [this message]
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=p91sg83t95g.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).