Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: physiculus <physiculus@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: physiculus <physiculus@gmail.com>,  info-gnus-english@gnu.org
Subject: Re: nnir with notmuch gives error; sort: Wrong type argument: number-or-marker-p, nil
Date: Sat, 14 Mar 2020 08:54:41 +0100	[thread overview]
Message-ID: <87o8sz8j7i.fsf@googlemail.com> (raw)
In-Reply-To: <878sk4hyux.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 13 Mar 2020 11:51:50 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

Hello,
i cut the output for readability. 

How do i edebug the function?
I don't know this...

Regards
Poul

> physiculus <physiculus@gmail.com> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>> Hello,
>>
>> here is the output from the debugger.
>> I dont know, what it mean, but i think you do :-)
>
> Not quite :) There seem to be nil values in the list of found articles
> returned by the notmuch search backend.
>
> Are you able to trigger the error with a search that returns fewer
> results? In your previous message, the output of the notmuch CLI command
> only contains seven results, but the elisp backtrace shows it trying to
> fetch headers for more than 50 articles. Are those the exact same
> searches?
>
> Can you edebug the function `nnir-retrieve-headers', start the search
> again, and when the edebugger starts hit "e", then "(setq abg
> nnir-artlist)", then in a followup to this message paste the value of
> the `abg' variable?
>
> Eric

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

      reply	other threads:[~2020-03-14  7:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 18:27 physiculus
2020-03-12 19:09 ` Eric Abrahamsen
2020-03-13  9:46   ` physiculus
2020-03-13 17:04     ` xuqi
2020-03-14  7:52       ` physiculus
2020-03-14 11:30         ` xuqi
2020-03-14 15:31           ` physiculus
2020-03-14 16:11             ` Eric Abrahamsen
2020-03-14 16:23               ` physiculus
2020-03-14 16:47                 ` Eric Abrahamsen
2020-03-15 11:45                   ` physiculus
2020-03-15 18:50                     ` xuqi
2020-03-16 18:42                       ` physiculus
2020-03-16 19:42                         ` Eric Abrahamsen
2020-03-17  8:50                           ` physiculus
2020-03-17 14:22                             ` physiculus
2020-03-18  1:27                               ` xuqi
2020-03-18 18:02                                 ` physiculus
2020-03-19 22:56                                   ` Eric Abrahamsen
2020-03-25 19:05                           ` nnir with notmuch gives error; Possible solution! physiculus
2020-03-25 19:19                             ` Eric Abrahamsen
2020-03-26 19:16                               ` Helmut Waitzmann
2020-03-15 22:09                     ` nnir with notmuch gives error; sort: Wrong type argument: number-or-marker-p, nil Eric Abrahamsen
2020-03-13 18:51     ` Eric Abrahamsen
2020-03-14  7:54       ` physiculus [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=87o8sz8j7i.fsf@googlemail.com \
    --to=physiculus@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.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).