On Fri, 20 Dec 2024 at 09:16, Jean Louis <[email protected]> wrote: > > * Eduardo Ochs <[email protected]> [2024-12-20 10:55]: > > Here is another way to run the mini-tutorial on edebug: > > (find-wget-elisp "http://anggtwu.net/elisp/edebug-2024.el";) > > if: wget can’t download: http://anggtwu.net/elisp/edebug-2024.el > > And I think that function `find-wget-elisp' should first give to user > some notice, like `(message "Doing wget %s" url)' as there was some > time before I got the error. > > It is good for you to know, if there is CPU running something like it > was case in my side, wget may fail for some reasons of timeouts. And > if there is heavy traffic, wget may also fail. > > If user can see first the notice, then user may understand better what > is going on, instead of being in the blocked Emacs for some seconds. > > Jean Louis
Hi Jean! Try this? (find-wget-elisp "http://anggtwu.net/elisp/2024-find-wget.el";) Cheers, thanks in advance, etc =), Eduardo
