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: Fri, 01 Feb 2019 09:22:31 +0200 Message-ID: <83bm3wynuw.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> <608533e75f41da3e36e191f8a670af05.squirrel@dancol.org> <725a9f97-8bb5-4592-2512-dbd422023f51@cs.ucla.edu> <6611df71-c89e-d4ce-5db7-00edec98a9f5@cs.ucla.edu> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="250130"; mail-complaints-to="usenet@blaine.gmane.org" Cc: schwab@linux-m68k.org, rpluim@gmail.com, eggert@cs.ucla.edu, dancol@dancol.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 01 08:22:56 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 1gpTA4-0012ur-HO for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2019 08:22:52 +0100 Original-Received: from localhost ([127.0.0.1]:40076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gpTA3-0002IJ-ID for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2019 02:22:51 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:32785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gpT9y-0002GE-KP for emacs-devel@gnu.org; Fri, 01 Feb 2019 02:22:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53863) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gpT9v-0002wY-TK; Fri, 01 Feb 2019 02:22:44 -0500 Original-Received: from [176.228.60.248] (port=3033 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gpT9n-0003pu-Ab; Fri, 01 Feb 2019 02:22:36 -0500 In-reply-to: (message from Richard Stallman on Thu, 31 Jan 2019 19:23:58 -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:232878 Archived-At: > From: Richard Stallman > Cc: dancol@dancol.org, eliz@gnu.org, schwab@linux-m68k.org, > rpluim@gmail.com, emacs-devel@gnu.org > Date: Thu, 31 Jan 2019 19:23:58 -0500 > > If the program wants to relaunch itself, or find other files that correspond > to its executable file, it should check @code{argv[0]}. 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 or some other method, or because the calling program puts there something unrelated to where the executable lives. There's a reliable way to find where the executable file of a running process lives -- on GNU/Linux, this is via /proc/self. But saying "should" here could be interpreted to mean that the GNU Coding Standards frown on any other method of doing this job. Perhaps "could" or "might". Or "it is customary to ...".