From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Bloat in Windows (revisited)
Date: Sun, 09 Jun 2019 22:16:42 +0100 [thread overview]
Message-ID: <87pnnme9xh.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvimtitatw.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 06 Jun 2019 22:07:45 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I think many editors would have "integrated" find tools even if this is
>> just a call out to the OS GUI tool for doing the same. Likewise, spell
>> checker.
>
> Yes, I agree with the general desire. I just proposed a hypothetical
> way to make the slope less slippery by reducing the difference between
> the tools that are bundled and those that aren't.
>
>> A quick "grep" for executable-find gives 300 hits. Many are
>> languages (i.e. in progmodes), many are text processing commands or
>> viewers. After that, we do not have that large a list.
>
> [ Not sure what is the relation between executable-find and this
> discussion. I was thinking about catching the error you get from
> start/call-process and then looking up some ad-hoc list of
> known commands and their corresponding MSYS2 package. ]
Oh, "executable-find" is just a cheap and cheerful way of giving some
idea of what executables Emacs might well look for.
>> I don't think that there are simple instructions on how to install these
>> tools, other than "re-install this version of Emacs over msys2 (or just
>> install Emacs via msys2) then add the packages with pacman". This is why
>> I am asking the question.
>
> I'm too far from Windows to know anything about that.
> So maybe indeed there's no good solution here.
>
> I was hoping we could write some Elisp that can download&install
> a minimal MSYS2, and another that can ask MSYS2 to install some tool.
I think this would be effectively rewriting pacman in elisp which seems
like a bad idea. Pre-bundling seems the only sensible solution. People
who want to install new dependencies already know how to do this, I
think -- which is install the no-deps Emacs over an existing MSYS.
>> On the other question, does excluding mingw-w64-x86_64-glib2 and subtree
>> seem sensible?
>
> I'm too far from Windows to know anything about that ;-)
Me too, alas.
next prev parent reply other threads:[~2019-06-09 21:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 21:46 Bloat in Windows (revisited) Phillip Lord
2019-06-05 23:24 ` Tak Kunihiro
2019-06-06 14:29 ` Eli Zaretskii
2019-06-06 14:34 ` Stefan Monnier
2019-06-06 20:14 ` Phillip Lord
2019-06-07 2:07 ` Stefan Monnier
2019-06-09 21:16 ` Phillip Lord [this message]
2019-06-10 8:59 ` Nikolay Kudryavtsev
2019-06-10 12:17 ` Óscar Fuentes
2019-06-10 15:47 ` Nikolay Kudryavtsev
2019-06-10 21:28 ` Phillip Lord
2019-06-13 17:27 ` Nikolay Kudryavtsev
2019-06-13 17:53 ` Eli Zaretskii
2019-06-13 18:12 ` Nikolay Kudryavtsev
2019-06-13 21:34 ` Phillip Lord
2019-06-14 8:19 ` Nikolay Kudryavtsev
2019-06-17 15:59 ` Phillip Lord
2019-06-18 16:29 ` Eli Zaretskii
2019-06-18 17:59 ` Stefan Monnier
2019-06-18 19:27 ` Óscar Fuentes
2019-06-13 21:31 ` Phillip Lord
2019-06-07 6:08 ` Eli Zaretskii
2019-06-10 8:52 ` Nikolay Kudryavtsev
2019-06-10 15:27 ` Eli Zaretskii
2019-06-10 21:17 ` 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=87pnnme9xh.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).