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>, Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Workshop to save M$ Windows users - help needed
Date: Sun, 03 Oct 2021 21:44:10 +0200	[thread overview]
Message-ID: <87r1d151x1.fsf@logand.com> (raw)
In-Reply-To: <CADs++6gtBYCS+EzyNUGttf7XfMW2sFOZ3OaJbzDWay43i9BQ4w@mail.gmail.com>

On Sun 03 Oct 2021 at 16:15, Eduardo Ochs <eduardoochs@gmail.com> wrote:
> On Sun, 3 Oct 2021 at 07:41, Eli Zaretskii <eliz@gnu.org> wrote:
>> Do you really need that?  The Windows Explorer can unzip files just
>> fine, and a browser or Emacs itself can be used to fetch files.
>   mkdir -p $S/http/www.gnu.org/software/emacs/
>   cd       $S/http/www.gnu.org/software/emacs/
>   wget -nc 'http://www.gnu.org/software/emacs/emacs-paper.html'
> [...]
> So several things in the workshop will be much easier if everybody has
> wget in the path.

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?



  reply	other threads:[~2021-10-03 19:44 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 [this message]
2021-10-04  3:06           ` Eduardo Ochs
2021-10-04 17:34             ` Tomas Hlavaty
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=87r1d151x1.fsf@logand.com \
    --to=tom@logand.com \
    --cc=eduardoochs@gmail.com \
    --cc=eliz@gnu.org \
    --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).