unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.g0@libero.it>
To: emacs-devel@gnu.org
Subject: Re: Avoid duplicate emacs.exe / emacs-$version.exe
Date: Sun, 29 Mar 2020 19:01:50 +0200 (CEST)	[thread overview]
Message-ID: <1985099315.1630555.1585501310037@mail1.libero.it> (raw)

Eli Zaretskii wrote:

> I've just fixed that on master;

Now my build on Windows via MSYS2 creates an hardlink instead then s symlink. Notice that MSYS2 by default does not enable symlink so the using 'ln -s ...' really copies the file. So I enabled Windows native symlink with  

rem To activate windows native symlinks uncomment next line
set MSYS=winsymlinks:nativestrict

in /msys2_shell.cmd

(maybe W10 needs also the developpers mode). In this way my builds had 

  1 mar 13.55 emacs-27.0.90.exe
  1 mar 14.01 emacs.exe -> emacs-27.0.90.exe


What do I have to do to get back to the way I used to be? I don't want to delete the hardlink and add the symlink manually.

BTW, why Emacs, on Windows, has 3 executable?

  runemacs.exe
  emacs-27.0.90.exe
  emacs.exe (hardlink, now)

Yes, runemacs.exe to remove the DOS window (if I remember): why this cannot be done with a single EXE? On Windows there ar a lot of apps (IDE, Editore, Browser etc) which have only one EXE to be started with (no DOS window etc). WHY not Emacs? This could be another simplification in the spirit of this discussion...

Ciao,
  Angelo.



             reply	other threads:[~2020-03-29 17:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 17:01 Angelo Graziosi [this message]
2020-03-29 17:22 ` Avoid duplicate emacs.exe / emacs-$version.exe Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2020-03-28 16:53 Juan José García-Ripoll
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:41   ` Juan José García-Ripoll
2020-03-28 22:45     ` Phillip Lord
2020-03-29  2:31     ` Eli Zaretskii
2020-03-29  9:38       ` Juan José García-Ripoll
2020-03-29 13:08         ` Phillip Lord
2020-03-29 14:10         ` Eli Zaretskii
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:13   ` Phillip Lord
2020-03-28 20:48     ` Juan José García-Ripoll
2020-03-28 22:22       ` Phillip Lord
2020-03-28 23:36         ` Juan José García-Ripoll
2020-03-29 12:55           ` Phillip Lord
2020-03-29  2:27     ` Eli Zaretskii
2020-03-29 12:52       ` Phillip Lord
2020-03-29 13:56         ` Eli Zaretskii
2020-03-29 17:25           ` Phillip Lord
2020-03-28 23:36   ` Juan José García-Ripoll
2020-03-29  2:36     ` Eli Zaretskii
2020-03-29 12:59       ` Phillip Lord
2020-03-29 13:59         ` Eli Zaretskii
2020-03-29 18:18           ` Phillip Lord
2020-03-29 18:34             ` Eli Zaretskii
2020-03-29 20:49               ` Phillip Lord

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=1985099315.1630555.1585501310037@mail1.libero.it \
    --to=angelo.g0@libero.it \
    --cc=emacs-devel@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 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).