From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Joost <joostkremers@fastmail.fm>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to *properly* set up Emacs on Windows?
Date: Wed, 09 Feb 2022 12:22:01 +0100 [thread overview]
Message-ID: <86a6f0s2sm.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <329e100c-bdc0-4dd3-9f8b-64af1b4cc90e@www.fastmail.com> (Joost's message of "Wed, 09 Feb 2022 09:48:09 +0100")
Joost <joostkremers@fastmail.fm> writes:
> Is there an Emacs 28 pretest available that will work with this? (The
> Windows binaries that were anounced on emacs-devel the other day
> appear to be MSYS2 binaries? And `pacman -Ss emacs` doesn't return any
> Emacs 28 packages.)
Please check
http://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/
These Windows binaries were build with MSYS2 but don't need MSYS to run.
Please read nt/README{.W64} and nt/INSTALL{.W64} for further
information.
> I've been using Git Bash (alongside eshell) as my shell of
> choice. Would the MinGW-x64 shell provided by MSYS2 be a better
> choice? Or doesn't it really matter?
As far as I understand, Git Bash is based on MSYS2. (I'm now using
exclusively the MSYS2 shell, instead of the Git Bash shell..:-))
Dieter
--
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany
next prev parent reply other threads:[~2022-02-09 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 17:06 How to *properly* set up Emacs on Windows? Joost
2022-02-08 18:52 ` Eli Zaretskii
2022-02-09 8:14 ` Joost
2022-02-09 14:04 ` Eli Zaretskii
2022-02-10 21:05 ` Joost Kremers
2022-02-08 20:02 ` Óscar Fuentes
2022-02-09 8:48 ` Joost
2022-02-09 11:22 ` H. Dieter Wilhelm [this message]
2022-02-09 13:19 ` Óscar Fuentes
2022-02-10 21:58 ` Joost Kremers
2022-02-10 22:37 ` Óscar Fuentes
2022-02-11 9:30 ` Joost
2022-02-11 7:00 ` Eli Zaretskii
2022-02-09 12:28 ` Arash Esbati
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a6f0s2sm.fsf@duenenhof-wilhelm.de \
--to=dieter@duenenhof-wilhelm.de \
--cc=help-gnu-emacs@gnu.org \
--cc=joostkremers@fastmail.fm \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.