Notes |
(0002801)
jilles (reporter)
2015-08-31 21:43
|
Although I agree that the "nolog" option no longer means anything, we should be careful with removing shell options entirely, since attempting to set an unknown option aborts execution of a profile or script unless special measures are taken. |
|
(0002806)
joerg (reporter)
2015-09-02 16:02
|
There is no history for commands from within scripts and the worst result I could imagine is a "nolog: bad option(s)" mesage from $ENV. |
|
(0003261)
geoffclare (manager)
2016-06-09 16:30
edited on: 2016-06-10 06:48
|
Interpretation response
------------------------
The standard states the requirements for set -o nolog, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.
Rationale:
-------------
The standard developers could not identify any shell in which set -o nolog has an effect on shell history.
Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
After page 2382, Lines 75893-75894 in the description of the set utility:nologPrevent the entry of function definitions into the command history; see Command History List. add:This option may have no effect; it is kept for compatibility with previous versions of the standard. and mark page 2382, lines 75893-75894 (including the nolog heading and the newly added text) OB.
On page 2386, line 76051, change FUTURE DIRECTIONS from:None. to:A future version of this standard may remove the -o nolog option. On page 3204 line 107359 section sh, delete:For example, function definition commands are recorded in the history file, unless the set −o nolog option is set. If the system administrator includes function definitions in some system start-up file called before the ENV file, the history file is initialized before the user gets a chance to influence its characteristics.
|
|
(0003266)
ajosey (manager)
2016-06-17 07:11
|
Interpretation Proposed: 17 June 2016 |
|
(0003299)
ajosey (manager)
2016-07-19 11:36
|
Interpretation approved: 19 July 2016 |
|