From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Mon, 28 Jan 2019 17:41:58 +0200 Message-ID: <8336pc4wmx.fsf@gnu.org> References: <83munr8jb1.fsf@gnu.org> <838szb8ey9.fsf@gnu.org> <83d0oj62bc.fsf@gnu.org> <87ef8z4g1m.fsf@igel.home> <838sz75u7p.fsf@gnu.org> <877eer4e4x.fsf@igel.home> <835zub5p3i.fsf@gnu.org> <8736pf408v.fsf@igel.home> <83womq3z5c.fsf@gnu.org> <871s4yxfvb.fsf@igel.home> <83o9823xcq.fsf@gnu.org> <87womqvyy4.fsf@igel.home> <4f30b2b598e71d2c6ad766a3da8e4a33.squirrel@dancol.org> <87o982vszn.fsf@igel.home> <87k1ipx3jq.fsf@igel.home> <87bm41wzmv.fsf@igel.home> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="73455"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 28 17:00:31 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1go9Kn-000Inx-S1 for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 17:00:30 +0100 Original-Received: from localhost ([127.0.0.1]:34164 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1go9Kh-0005cV-Ek for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 11:00:23 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1go9Hb-00039K-8m for emacs-devel@gnu.org; Mon, 28 Jan 2019 10:57:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53062) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1go936-00010C-NO; Mon, 28 Jan 2019 10:42:12 -0500 Original-Received: from [176.228.60.248] (port=4779 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1go936-0001XX-FL; Mon, 28 Jan 2019 10:42:12 -0500 In-reply-to: (message from Stefan Monnier on Mon, 28 Jan 2019 03:53:33 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232764 Archived-At: > From: Stefan Monnier > Date: Mon, 28 Jan 2019 03:53:33 -0500 > > > I plan to look into the possibility of putting the dump file inside > > the executable (portably, of course) so that Emacs startup needn't > > worry about finding the dump file. This would be significantly better > > for installers and users. > > Allowing the dump file to be a shebang-executable is easy, doesn't > require a C compiler at dump-time, and works well under GNU/Linux. > It can't be "the only way" because it works less well under MacOS and > not at all under Windows (IIUC), but I see no reason not to support it. Its relative complexity is such a reason, IMO. By contrast, opening and reading a file is simple, is portable, and works well. The issue with finding it via argv[0] is relatively simple to solve. And if we for some reason decide that argv[0] is not reliable enough, I already mentioned up-thread an alternative of using platform-specific techniques to obtain the full absolute file name of the executable without relying on argv[0]. I see no reason to increase complexity and introduce methods that expose system dependencies on the user level due to the issue that started this thread. IME, having OS-dependent differences in Emacs invocation and installation is a disadvantage, it complicates the user manual and bug-reporting instructions, if nothing else.