From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Mon, 28 Jan 2019 13:20:24 -0500 Message-ID: References: <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> <8336pc4wmx.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="185705"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 28 20:00:14 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 1goC8g-000m4o-2b for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 20:00:10 +0100 Original-Received: from localhost ([127.0.0.1]:37088 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1goC8e-0007En-SP for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 14:00:08 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1goBWV-0002Lz-FN for emacs-devel@gnu.org; Mon, 28 Jan 2019 13:20:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1goBWR-00019g-Ix for emacs-devel@gnu.org; Mon, 28 Jan 2019 13:20:41 -0500 Original-Received: from [195.159.176.226] (port=40462 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1goBWP-00014U-PE for emacs-devel@gnu.org; Mon, 28 Jan 2019 13:20:39 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1goBWI-0016VA-2V for emacs-devel@gnu.org; Mon, 28 Jan 2019 19:20:30 +0100 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:c/e12/cwB3AtQeGD0uRFAA77awE= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:232771 Archived-At: > 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]. The issue is the following: User FOO makes his own dump. Maybe even several different dumps (e.g. one for his Gnus session, one for his Org session, and one for his programming sessions). How is he going to start each one of those? He can go and create shell scripts that do `emacs --dump-file `, or he can manually start his Emacs with the corresponding options, but it's much simpler for him to make the dumps executable (and have the dumps look for the only matching `emacs` rather than have `emacs` guess which dump was meant). > 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. AFAIK, the only complexity is to (optionally) skip the first page when loading a dump file. Stefan