In Issue 7, there are a few references to the .profile file:
* Page 2344 line 74642:
Uses of files as command scripts, or for configuration or control,
are exempt. For example, it is not required that sh be able to
read an arbitrarily large .profile.
* Page 3308 line 111414:
Initialize the terminal according to the type of terminal in the
environmental variable TERM. This command can be included in a
.profile file.
* Page 3726 line 127823:
ENV This variable can be used to set aliases and other items
local to the invocation of a shell. The file referred to
by ENV differs from $HOME/.profile in that .profile is
typically executed at session start-up, whereas the ENV
file is executed at the beginning of each shell invocation.
[...]
but under "sh" (page 3226), there are no mentions of .profile at all.
So why referencing .profile while it is not used by sh?
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
