all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: How to *properly* set up Emacs on Windows?
Date: Thu, 10 Feb 2022 23:37:55 +0100	[thread overview]
Message-ID: <87r18amjp8.fsf@telefonica.net> (raw)
In-Reply-To: 874k565pup.fsf@fastmail.fm

Joost Kremers <joostkremers@fastmail.fm> writes:

>>> (The
>>> Windows binaries that were anounced on emacs-devel the other day
>>> appear to be MSYS2 binaries?
>>
>> I don't think so.
>
> I think I saw it mentioned somewhere that they were built with MSYS2. But I
> understand now that it's possible to build MinGW binaries with MSYS2, so that
> doesn't mean anything.

Correct. Actually, MSYS2 was created for building MinGW projects which
*build system* require a POSIX environment (autoconf, for instance). The
build products themselves do not depend on MSYS2 (unless you explicitly
use a toolchain that creates MSYS2 executables instead of the MinGW
toolchain, something only the MSYS2 maintainers usually do.)

> Gotcha. I've now added C:\Program Files\Git\cmd\bin to Path, though,
> because it seems magit needs it. (That may be a bug, but that's a
> topic for another forum.)

Magit will be fine without the directory of git.exe on PATH if you set
magit-git-executable to "C:/Program Files/Git/cmd/bin/git.exe"

> Thanks for your help, I have a much better idea of what I'm doing now.

You're welcome.




  reply	other threads:[~2022-02-10 22:37 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
2022-02-09 13:19     ` Óscar Fuentes
2022-02-10 21:58       ` Joost Kremers
2022-02-10 22:37         ` Óscar Fuentes [this message]
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=87r18amjp8.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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.
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.