Maxim Cournoyer <maxim.courno...@gmail.com> writes: > Hi!
Hi Maxim, >> Hi, I am trying now to troubleshoot some of the emacs-guix bugs I had >> reported, but got hung up on something else: It seems that none of the >> gnus bug searching functions from emacs-debbugs are working for me. If >> I know the bug number already, I can run debbugs-gnu-bugs, and that >> works fine. But if I try debbugs-gnu-guix-search or debbugs-gnu-search >> I cannot get any results. I can get to the result buffer with >> debbugs-gnu-show-last-result, but there is nothing there. Are those >> functions working fine for everybody else? >> >> Right now I'm running GNU Emacs 30.0.92 (build 2, x86_64-pc-linux-gnu, >> GTK+ Version 3.24.41, cairo version 1.18.0) of 2024-10-29 with the >> emacs-debugs-0.41 from Guix. I tried using Emacs 29.4 but results seem >> to be the same. Likewise with emacs -q. The recent version in GNU ELPA is debbugs 0.42. > It seems to work for me. M-x debbugs-gnu-guix-search RET python-team, > then M-x debbugs-gnu-show-last-result (that seems to be a new thing -- I > guess I'll check the customizations to revert to show directly the > results): Since debbugs 0.41, bug reports are retrieved asynchronously. debbugs-gnu-show-last-result switches to the result buffer (you get a meesage, when bug retrieval has finished). If you don't like it, set debbugs-gnu-use-threads to nil. See (info "(debbugs-ug) Retrieving Bugs") Best regards, Michael.
