unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Workshop to save M$ Windows users - help needed
Date: Mon, 04 Oct 2021 19:34:46 +0200	[thread overview]
Message-ID: <87h7dwy9qh.fsf@logand.com> (raw)
In-Reply-To: <CADs++6hDpnMCHpfA=EWtQAkjs+fC5rGJiE=nTtTyNJ0KgZMa7Q@mail.gmail.com>

On Mon 04 Oct 2021 at 00:06, Eduardo Ochs <eduardoochs@gmail.com> wrote:
> On Sun, 3 Oct 2021 at 16:44, Tomas Hlavaty <tom@logand.com> wrote:
>>
>> Emacs should be able to download the files even on Windows without
>> installing wget, e.g. this should work:
>>
>> (eww "http://www.gnu.org/software/emacs/emacs-paper.html")
>>
>> There is a variable url-cache-directory suggesting that caching can
>> happen transparently.  Maybe you could even supply your own
>> url-cache-creation-function.  Or figure out what functions you could
>> reuse to simulate wget and your caching strategy in pure Emacs more
>> closely.
>>
>> I know you want to do it manually, but why bother beginners with that?
>
>
> Hi Tomas,
>
> I've tried to implement something like what you are proposing. It
> seems that the right tool for that, at least for the simplest
> cases, is `url-retrieve-synchronously'. It is documented here:
>
>   (find-node "(url)Retrieving URLs")
>   (find-node "(url)Retrieving URLs" "url-retrieve-synchronously")
>   (find-node "(url)Dealing with HTTP documents")
>
> Straight.el uses `url-retrieve-synchronously' here:
>
>   https://github.com/raxod502/straight.el#getting-started
>
> Try this:
>
>   (find-ebuffer
>    (url-retrieve-synchronously
>     "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el"
>     'silent 'inhibit-cookies)
>    "\n\n")
>
> The "\n\n" will put the point after the response headers.
>
> I thought that it would be trivial to write a "fake wget" for
> eshell using `url-retrieve-synchronously'. The part of adding a
> new builting seems to be easy, see:
>
>   (find-node "(eshell)Built-ins" "eshell/ls")
>   (find-eshellfile "")
>   (find-eshellgrep "grep --color=auto -nH --null -e eshell/ *.el")
>
> but I couldn't get the error checking right, and at some point I
> stopped trying. Then I saw this thread,
>
>   https://lists.gnu.org/archive/html/emacs-devel/2021-03/threads.html#01359
>
> and it convinced me that using a real wget would be the right
> thing to do.
>
> I have some code for playing with url-retrieve here, if you'd
> like to try:
>
>                      http://angg.twu.net/elisp/url-retrieve-test.el
>                      http://angg.twu.net/elisp/url-retrieve-test.el.html
>   (find-wgeta-elisp "http://angg.twu.net/elisp/url-retrieve-test.el")
>
>   Cheers,
>     Eduardo Ochs
>     http://angg.twu.net/#eev

I see, url-retrieve-synchronously is a beast.  You could write something
simpler and keep track of the status.  Something like:

;;; -*- lexical-binding: t -*-

(defun url-retrieve-synchronously2 (url filename)
  (let ((b (find-file filename))
        z
        (again t))
    (cl-flet ((save (status done)
                    ;;(message "save %s %s" status done)
                    (setq z status)
                    (if done
                        (setq again nil)
                      (when status
                        (with-current-buffer b
                          (let ((coding-system-for-write 'raw-text-unix))
                            (write-region (point-min) (point-max) filename)))))))
      (with-current-buffer b
        (url-retrieve url #'save '(t)))
      (while again
        (save nil nil)
        (sleep-for 1))
      ;;(message "done")
      z)))

(url-retrieve-synchronously2 "https://logand.com" "/tmp/e2")
(url-retrieve-synchronously2 "https://logand.com1" "/tmp/e2")

This works for me (saves whole http response), returns plist and saves
the data into file on success, otherwise on failure returns nil.

Anyway, I was trying to suggest something even simpler: use eww and
customize it so that it caches the downloaded files.  This is what you
are doing in shell manually.

Or even better, bind for example M-f to ffap so that people can simply
press M-f on a url and Emacs will take them there.



  reply	other threads:[~2021-10-04 17:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  4:26 Workshop to save M$ Windows users - help needed Eduardo Ochs
2021-10-03  5:45 ` Jean Louis
2021-10-03  7:59   ` Eduardo Ochs
2021-10-03  9:35 ` Eli Zaretskii
2021-10-03 10:19   ` Eduardo Ochs
2021-10-03 10:40     ` Eli Zaretskii
2021-10-03 19:15       ` Eduardo Ochs
2021-10-03 19:44         ` Tomas Hlavaty
2021-10-04  3:06           ` Eduardo Ochs
2021-10-04 17:34             ` Tomas Hlavaty [this message]
2021-10-04 18:29               ` Tomas Hlavaty
2021-10-06  4:50                 ` Eduardo Ochs
2021-10-06  5:10                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-06 12:41                   ` Eli Zaretskii
2021-10-07 16:32                 ` Eduardo Ochs
2021-10-07 17:52                   ` Tomas Hlavaty
2021-10-04 18:50         ` Eli Zaretskii
2021-10-06  4:19           ` Eduardo Ochs
2021-10-03  9:36 ` Tomas Hlavaty

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7dwy9qh.fsf@logand.com \
    --to=tom@logand.com \
    --cc=eduardoochs@gmail.com \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).