From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Fri, 01 Feb 2019 22:25:50 -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> <87k1ipx3jq.fsf@igel.home> <87bm41wzmv.fsf@igel.home> <608533e75f41da3e36e191f8a670af05.squirrel@dancol.org> <725a9f97-8bb5-4592-2512-dbd422023f51@cs.ucla.edu> <6611df71-c89e-d4ce-5db7-00edec98a9f5@cs.ucla.edu> <83bm3wynuw.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="143088"; mail-complaints-to="usenet@blaine.gmane.org" Cc: rpluim@gmail.com, eggert@cs.ucla.edu, schwab@linux-m68k.org, emacs-devel@gnu.org, dancol@dancol.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 02 04:26:04 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 1gplwS-000b80-Fn for ged-emacs-devel@m.gmane.org; Sat, 02 Feb 2019 04:26:04 +0100 Original-Received: from localhost ([127.0.0.1]:36718 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gplwR-0005Mh-G7 for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2019 22:26:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gplwF-0005Ko-Dg for emacs-devel@gnu.org; Fri, 01 Feb 2019 22:25:52 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gplwE-0000b1-UP; Fri, 01 Feb 2019 22:25:51 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1gplwE-0005QN-Me; Fri, 01 Feb 2019 22:25:50 -0500 In-Reply-To: <83bm3wynuw.fsf@gnu.org> (message from Eli Zaretskii on Fri, 01 Feb 2019 09:22:31 +0200) 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:232897 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I would suggest to use another word instead of "should". Using > argv[0] has its drawbacks, e.g., if the string there neither has a > slash nor is a file found along PATH -- this could happen when a > program is invoked via a symlink How so? I don't see how this could happen. If the symlink was found in PATH to run the program, it should be there when the program looks for it, except in the case where it was deleted or renamed in the mean time. or some other method, or because the > calling program puts there something unrelated to where the executable > lives. Yes, that can happen, but I think that is an error on the caller's part. Anyway, there is no other portable method besides argv[0]. I don't know whether we want to assume that all kernels for GNU will support /proc/self. -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)