From: "jake" <jake@mgap.ru>
To: <notmuch@notmuchmail.org>
Subject: Possible bug with notmuch search & --limit --offset
Date: Thu, 26 Apr 2012 16:56:06 +0100 [thread overview]
Message-ID: <000301cd23c5$174d6510$45e82f30$@mgap.ru> (raw)
Hello,
I'm finding that when I use the --limit option with the output=files and
offset=N that the returned list of files is of variable length.
For instance when:
notmuch search --output=files --offset=6 --limit=2 steve
it returns
/var/spool/mail/virtual/archive/sl/.Sent/cur/1335243985.M765351P23366V000000
0000000801I0000000000820E9C_5.archive,S=275069:2,S
/var/spool/mail/virtual/archive/sl/.Sent/cur/1335243986.M749883P23366V000000
0000000801I0000000000820E9D_6.archive,S=275069:2,S
/var/spool/mail/virtual/archive/sl/.Sent/cur/1335243987.M926961P23366V000000
0000000801I0000000000820EA0_9.archive,S=111888:2,S
/var/spool/mail/virtual/archive/sl/.Sent/cur/1335243988.M718230P23366V000000
0000000801I0000000000820EA1_10.archive,S=111888:2,S
Which is two more results than required. If I choose different offset values
then the number of returned results will vary too.
If I issue:
notmuch search --offset=6 --limit=2 steve
It returns two results as expected, if I change the output type to anything
other than files (summary/threads/messages/tags) then the correctly limited
list is returned. So it only seems to happen with the files output type.
Both json and text format types exhibit the same behaviour.
Am I using this correctly ? I expect only two results to be returned but
being new to notmuch gives me doubts that what I am doing may be incorrect.
My apologies if the mailing list is not the place for this sort of report,
please direct me to a more appropriate place.
Many Thanks
Jake
next reply other threads:[~2012-04-26 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 15:56 jake [this message]
2012-04-26 16:18 ` Possible bug with notmuch search & --limit --offset Mark Walters
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000301cd23c5$174d6510$45e82f30$@mgap.ru' \
--to=jake@mgap.ru \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.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).