unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Workshop to save M$ Windows users - help needed
Date: Mon, 04 Oct 2021 21:50:29 +0300	[thread overview]
Message-ID: <835yuc62ve.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6gtBYCS+EzyNUGttf7XfMW2sFOZ3OaJbzDWay43i9BQ4w@mail.gmail.com> (message from Eduardo Ochs on Sun, 3 Oct 2021 16:15:11 -0300)

> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Sun, 3 Oct 2021 16:15:11 -0300
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
>       http://www.gnu.org/software/emacs/emacs-paper.html
> 
> and type M-x brep we get a temporary buffer containing something like
> this,
> 
> 
> • (eepitch-shell)
> • (eepitch-kill)
> • (eepitch-shell)
>   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. An un(tg)zipper is not very important - I only
> realized this after my previous e-mail - but wget is.

I still don't think I understand.  Emacs is perfectly capable of
fetching URLs, so why would you need wget?  If you base this on wget,
you will need to cope with complexities that you had better avoided:
how to download a program, where to find it, how to install it so it's
on PATH, etc. etc.  Please believe me that arranging for a simple Lisp
command that fetches a URL and saves it to a file is orders of
magnitude simpler.



  parent reply	other threads:[~2021-10-04 18:50 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
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 [this message]
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=835yuc62ve.fsf@gnu.org \
    --to=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).