From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 9047@debbugs.gnu.org
Subject: bug#9047: 24.0.50; Paging in tabulated-list-mode
Date: Mon, 07 Oct 2019 05:20:57 +0200 [thread overview]
Message-ID: <874l0lckbq.fsf@gnus.org> (raw)
In-Reply-To: <874l0o7whc.fsf@gmx.de> (Michael Albinus's message of "Fri, 04 Oct 2019 10:20:31 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
>>> I am using tabulated-list-mode in debbugs-gnu.el. Due to the amount of
>>> bugs, they must be presented on several pages (buffers). There are
>>> widgets which allow navigation between those pages.
>>
>> Was this something that debbugs-gnu had in earlier years? I just get
>> the entire bug list presented to me, and it doesn't look like I have any
>> customisations in that area.
>
> In the beginning, debbugs-gnu retrieved only up to 500 bugs, and showed
> them. The user could ask for the next (up to 500) bugs afterwards, and
> so on.
>
> Today, debbugs-gnu knows how many bugs to retrieve at all. It raises
> several soap-invoke-async requests in parallel, every call limited to
> 500 bugs. The results of the calls will be merged and shown - thats what
> you see as long list.
Right; thanks.
But this does make the requested feature unnecessary in this use case,
doesn't it? I mean, it does sound like something that'd be nice to
have, but in general we don't add stuff to Emacs until we have (at
least) one concrete use case.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-07 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 8:34 bug#9047: 24.0.50; Paging in tabulated-list-mode Michael Albinus
2019-10-03 16:15 ` Lars Ingebrigtsen
2019-10-04 8:20 ` Michael Albinus
2019-10-07 3:20 ` Lars Ingebrigtsen [this message]
2019-10-07 6:55 ` Michael Albinus
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=874l0lckbq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=9047@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.