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: Sun, 27 Jan 2019 14:42:35 -0500 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="148330"; 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 Sun Jan 27 20:43:24 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 1gnqKy-000cVA-C1 for ged-emacs-devel@m.gmane.org; Sun, 27 Jan 2019 20:43:24 +0100 Original-Received: from localhost ([127.0.0.1]:49773 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnqKx-0003ds-ER for ged-emacs-devel@m.gmane.org; Sun, 27 Jan 2019 14:43:23 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44866) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnqKM-0003dm-GL for emacs-devel@gnu.org; Sun, 27 Jan 2019 14:42:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnqKL-0001JQ-Lm for emacs-devel@gnu.org; Sun, 27 Jan 2019 14:42:46 -0500 Original-Received: from [195.159.176.226] (port=49858 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gnqKL-0001Ir-Er for emacs-devel@gnu.org; Sun, 27 Jan 2019 14:42:45 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1gnqKF-000biG-Vd for emacs-devel@gnu.org; Sun, 27 Jan 2019 20:42:39 +0100 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:UgrcR0uvnvRbV1+Z+9QDrCXhpOY= 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:232737 Archived-At: > Sure, but such callers are holding it wrong. If you set argv[0] to some > random string unrelated to Emacs, you break startup. That's fine. Indeed, this is sufficiently rare in my experience that I wouldn't worry about that case. >>> every system I've seen. Here's the algorithm: look at argv[0]: if it's >>> not an absolute path, make it absolute by prepending the startup CWD. >> If the executable is found on $PATH then argv[0] is *not* relative to CWD. > In that case, argv[0] will be absolute. That's not what I'm seeing on my system. When I type `emacs` into my shell (zsh under Debian), it is started with `emacs` as argv[0] and not with an absolute file name. Stefan