From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Daniel Colascione" Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Sun, 27 Jan 2019 17:06:15 -0800 Message-ID: <851e8d027a48752a60831a7e5c3fa3da.squirrel@dancol.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> Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="47722"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: SquirrelMail/1.4.23 [SVN] 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 02:21:58 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 1gnvcb-000CIk-Jl for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 02:21:58 +0100 Original-Received: from localhost ([127.0.0.1]:52407 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnvca-0006Ip-Fm for ged-emacs-devel@m.gmane.org; Sun, 27 Jan 2019 20:21:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnvat-00051t-Nc for emacs-devel@gnu.org; Sun, 27 Jan 2019 20:20:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnvNZ-0004MY-JG for emacs-devel@gnu.org; Sun, 27 Jan 2019 20:06:29 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:42314) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnvNX-0004Lj-KO for emacs-devel@gnu.org; Sun, 27 Jan 2019 20:06:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=MsE1uAY9zmTktX1JFlNeQoUuPvXuxCFBsbzOn4aAspg=; b=lhUKl2GTjbx2QyVjridaUkpvLqhrcaVAvGyFNJhzkXz2H3Jzs6Mbs4N78+igem5W3n/y8yzDsZhNGmeBHitzr6dhSEEkis8ulsK66B6VcngIfrHNPcoL+tRSmlFwF3NdT+SM5KNPNYKjwIXVCJ2eiAdFtGbxO9kKZIrf/9ohAGbO/NtnoC5XWb5LFqO8lovkjEVGntLsWcHMtQ1LLfQ/9VSkl2YueD8jG0qSDr723s8KdilqRwFTShgjntb/CcHffTFDfmJ/wx+wzyfaBQruJh9kzxOsBGO5su1X/zVG9QV1V1pScmwUeiyomxiTufWh2kBF2MTV1jIGmFJqqAQBNw==; Original-Received: from localhost ([127.0.0.1] helo=dancol.org) by dancol.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gnvNP-0002Hs-DV; Sun, 27 Jan 2019 17:06:15 -0800 Original-Received: from 127.0.0.1 (SquirrelMail authenticated user dancol) by dancol.org with HTTP; Sun, 27 Jan 2019 17:06:15 -0800 In-Reply-To: X-Priority: 3 (Normal) Importance: Normal X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:232745 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. Ah, in my tests, the path to the program run becomes absolute during shebang execution. For a raw executable, it's indeed pathless, but a search should PATH should solve that problem. That's what Emacs does today in init_cmdargs.