From: phillip.lord@russet.org.uk (Phillip Lord)
To: Jay Walker <jwalker@conserviscorp.com>
Cc: Nicolas Petton <nicolas@petton.fr>, 24040@debbugs.gnu.org
Subject: bug#24040: download instructions incomplete
Date: Sun, 24 Jul 2016 16:53:36 +0100 [thread overview]
Message-ID: <87a8h7yqv3.fsf@russet.org.uk> (raw)
In-Reply-To: <CAByNYzEG_6-JNZZG-wxdZ8qScr=WqUX=vQtv3LePLfwreqJhLw@mail.gmail.com> (Jay Walker's message of "Wed, 20 Jul 2016 20:57:21 +0000")
I entirely agree with this. Combined with the single multiple-top-level
zip file, the windows download is not obvious. And using Emacs without
having msys installed is a limited experience because it misses lots of
DLLs that it needs.
The README with the pre-test binaries really sucks als (my fault). This
situation could be improved significantly.
Phil
Jay Walker <jwalker@conserviscorp.com> writes:
> Yes, thank you so much for your help! Ok, so I am assuming to be completely
> new at Emacs. Based on the Windows Download instructions, but also OSX, I
> can´t really tell what to do. Following what the website says, it appears I
> can either download a zip file from a mirror, or get MSYS2 in order to
> download it that way. It seemed that MSYS2 was a better approach because
> downloading it gives me a bunch of files I have no idea what to do with. So
> once I have gotten MSYS2 (a link would be helpful!), I enter the command
> and see that it has downloaded. But what's next? Perhaps it would be useful
> to have a link to the next steps to getting emacs running. I type in
> ´emacs´ and it is unrecognized. Do you feel me on what I am getting at?
> Thanks for your patience and attentiveness!
> Jay
>
> On Wed, Jul 20, 2016 at 3:42 PM Nicolas Petton <nicolas@petton.fr> wrote:
>
>> Jay Walker <jwalker@conserviscorp.com> writes:
>>
>> Hi Jay,
>>
>> > I followed your download instructions and found they are so lacking,
>> please
>> > update!
>>
>> Which download instructions are you talking about? Was it the
>> instructions for Windows installation found on the Emacs website?
>>
>> Nico
>>
next prev parent reply other threads:[~2016-07-24 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 15:56 bug#24040: download instructions incomplete Jay Walker
2016-07-20 20:42 ` Nicolas Petton
2016-07-20 20:57 ` Jay Walker
2016-07-20 22:18 ` Nicolas Petton
2016-07-21 1:17 ` Óscar Fuentes
2016-07-21 12:57 ` Jay Walker
2016-07-21 14:24 ` Eli Zaretskii
2016-07-24 15:53 ` Phillip Lord [this message]
2016-07-25 13:15 ` Jay Walker
2016-07-26 16:10 ` Eli Zaretskii
2016-07-26 16:40 ` Nicolas Petton
2016-07-24 15:30 ` Nicolas Petton
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=87a8h7yqv3.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=24040@debbugs.gnu.org \
--cc=jwalker@conserviscorp.com \
--cc=nicolas@petton.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).