From: Phillip Lord <phillip.lord@russet.org.uk>
To: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Avoid duplicate emacs.exe / emacs-$version.exe
Date: Sat, 28 Mar 2020 22:22:18 +0000 [thread overview]
Message-ID: <87r1xcjf1h.fsf@russet.org.uk> (raw)
In-Reply-To: <86r1xcb3zc.fsf@csic.es> ("Juan José García-Ripoll"'s message of "Sat, 28 Mar 2020 21:48:23 +0100")
Juan José García-Ripoll <juanjose.garciaripoll@gmail.com> writes:
> Phillip Lord <phillip.lord@russet.org.uk> writes:
>> Incidentally, I build, run and (sort of) test the Windows distribution
>> under NTFS compression which all works fine. If these circumstances, I
>> think, even the difference between two files or hard-linked is moot.
>
> Not everyone has the luxury of commanding full configuration of their
> computers. Some have to install software at the user level, without
> administrator priviledges to do that configuration, or in a hardened
> virtual machine or a computer that is not really up to the task of
> handling everything with compression. So, while space nowadays seems
> "free", if small changes can tidy up a piece of sofware, why not
> implement them?
I think we all carry around the prejudices of our childhood. I taught
myself to program a while back. I often take a slow, cautious approach
with memory and space. My students tend not to at least not when talking
about less than 100Mb and increasing Gb. I used to shake my head in
despair, but then I realised that their code was simpler, cleaner and
faster than mine.
It's good that you are picking around the Windows build and I would like
to incorporate some of the changes; but not at the cost of (too much)
increased complexity in the source code. My build files have got too
complex already.
Phil
next prev parent reply other threads:[~2020-03-28 22:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 16:53 Avoid duplicate emacs.exe / emacs-$version.exe 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-03-29 17:01 Angelo Graziosi
2020-03-29 17:22 ` Eli Zaretskii
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=87r1xcjf1h.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=juanjose.garciaripoll@gmail.com \
/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).