From: Richard Stallman <rms@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: eliz@gnu.org, dancol@dancol.org, schwab@linux-m68k.org,
rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: Finding the dump
Date: Fri, 01 Feb 2019 22:25:57 -0500 [thread overview]
Message-ID: <E1gplwL-0005TJ-Ah@fencepost.gnu.org> (raw)
In-Reply-To: <5171b7a2-a4aa-4f13-a37a-800c0e9182b3@cs.ucla.edu> (message from Paul Eggert on Thu, 31 Jan 2019 18:09:11 -0800)
[[[ 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. ]]]
Thanks. Here is a new version. See any problems?
Can you tell me where the reference should point to?
If the program wants to relaunch itself, or find other files that correspond
to its executable file, it should check @code{argv[0]}. If that string
contains a slash, it is the file name of the executable and its directory
part says where to find other related files.
If there is no slash, the program should search for the executable in
the directories in @envvar{PATH}, and other related files should be in
the installation directory for the program's version.
@c ??? Someone please add a cross reference to info about that.
Providing this information in @code{argv[0]} is a convention, not a
guarantee. Well-behaved programs that launch other programs, such as
shells follow the convention, and your code should follow it too when
launching other programs. However, any program that needs to know the
location of its executable, or of other associated files, should offer
the user an option to specify the location.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-02-02 3:25 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:15 Finding the dump Stefan Monnier
2019-01-23 13:46 ` Robert Pluim
2019-01-23 15:13 ` Stefan Monnier
2019-01-23 13:55 ` Andreas Schwab
2019-01-23 15:17 ` Stefan Monnier
2019-01-23 15:37 ` Andreas Schwab
2019-01-23 15:44 ` Andreas Schwab
2019-01-23 16:07 ` Stefan Monnier
2019-01-23 15:50 ` Eli Zaretskii
2019-01-23 16:02 ` Stefan Monnier
2019-01-23 16:04 ` Paul Eggert
2019-01-23 16:38 ` Robert Pluim
2019-01-23 17:24 ` Eli Zaretskii
2019-01-26 12:17 ` Eli Zaretskii
2019-01-26 15:03 ` Andreas Schwab
2019-01-26 15:12 ` Eli Zaretskii
2019-01-26 15:44 ` Andreas Schwab
2019-01-26 17:02 ` Eli Zaretskii
2019-01-26 20:44 ` Andreas Schwab
2019-01-27 15:20 ` Eli Zaretskii
2019-01-27 15:46 ` Andreas Schwab
2019-01-27 15:59 ` Eli Zaretskii
2019-01-27 16:37 ` Andreas Schwab
2019-01-27 16:56 ` Eli Zaretskii
2019-01-27 17:00 ` Andreas Schwab
2019-01-27 18:26 ` Daniel Colascione
2019-01-27 18:46 ` Andreas Schwab
2019-01-27 18:58 ` Stefan Monnier
2019-01-27 19:27 ` Daniel Colascione
2019-01-27 19:42 ` Stefan Monnier
2019-01-28 1:06 ` Daniel Colascione
2019-01-27 20:12 ` Andreas Schwab
2019-01-27 21:25 ` Daniel Colascione
2019-01-27 21:37 ` Andreas Schwab
2019-01-27 23:47 ` Paul Eggert
2019-01-28 0:32 ` Daniel Colascione
2019-01-28 1:21 ` Paul Eggert
2019-01-28 1:29 ` Daniel Colascione
2019-01-28 19:03 ` Richard Stallman
2019-01-28 19:23 ` Paul Eggert
2019-01-28 23:09 ` Stefan Monnier
2019-01-29 8:50 ` Richard Stallman
2019-01-31 2:21 ` Paul Eggert
2019-02-01 0:23 ` Richard Stallman
2019-02-01 2:09 ` Paul Eggert
2019-02-02 3:25 ` Richard Stallman [this message]
2019-02-02 7:23 ` Eli Zaretskii
2019-02-03 4:36 ` Richard Stallman
2019-02-01 7:22 ` Eli Zaretskii
2019-02-02 3:25 ` Richard Stallman
2019-02-02 7:22 ` Eli Zaretskii
2019-02-03 4:36 ` Richard Stallman
2019-01-28 3:38 ` Eli Zaretskii
2019-01-28 4:13 ` Paul Eggert
2019-01-28 6:28 ` Daniel Colascione
2019-01-28 15:35 ` Eli Zaretskii
2019-01-28 15:57 ` Paul Eggert
2019-01-28 16:02 ` Daniel Colascione
2019-01-28 17:39 ` Paul Eggert
2019-01-28 19:46 ` Daniel Colascione
2019-01-28 8:53 ` Stefan Monnier
2019-01-28 12:57 ` Fu Yuan
2019-01-28 15:41 ` Eli Zaretskii
2019-01-28 18:20 ` Stefan Monnier
2019-01-28 19:53 ` Eli Zaretskii
2019-01-28 22:30 ` Stefan Monnier
2019-01-27 9:55 ` Stefan Monnier
2019-01-27 10:32 ` Andreas Schwab
2019-01-27 10:44 ` Stefan Monnier
2019-01-27 10:54 ` Andreas Schwab
2019-01-27 15:33 ` Eli Zaretskii
2019-01-27 18:52 ` Stefan Monnier
2019-01-27 19:25 ` Eli Zaretskii
2019-01-27 18:47 ` Stefan Monnier
2019-01-26 17:27 ` Michael Heerdegen
2019-01-26 17:29 ` Eli Zaretskii
2019-01-26 18:05 ` Michael Heerdegen
2019-01-26 18:13 ` Eli Zaretskii
2019-01-26 20:05 ` Michael Heerdegen
2019-01-26 20:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 3:00 Van L
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1gplwL-0005TJ-Ah@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).