A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1161 ====================================================================== Reported By: steffen Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1161 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: Resolved Name: steffen Organization: User Reference: Section: command Page Number: 2596 Line Number: 84274 ff. Interp Status: --- Final Accepted Text: See http://austingroupbugs.net/view.php?id=1161#c4220 Resolution: Accepted As Marked Fixed in Version: ====================================================================== Date Submitted: 2017-09-04 13:09 UTC Last Modified: 2019-01-25 00:05 UTC ====================================================================== Summary: command -v must find something executable ======================================================================
---------------------------------------------------------------------- (0004224) kre (reporter) - 2019-01-25 00:05 http://austingroupbugs.net/view.php?id=1161#c4224 ---------------------------------------------------------------------- To clarify the problem: the wording in the description of "command -v" that is the real issue does not relate to the bullet points (that which is proposed to be changed) which really are just defining what the output should be in various cases. but to this sentence: Write a string to standard output that indicates the pathname or command that will be used by the shell, in the current shell execution environment (see Section 2.12, on page 2381), to invoke command_name, but do not invoke command_name. The problem is that the way that the shell works out what pathname that "will be used" (when a pathname is to be used, the other cases, when some internal shell object is used are not a problem) is by actually invoking the command name - which this text (quite correctly) says not to do. If that text instead said: Write a string to standard output that indicates the pathname or command that will be first attempted to be used by the shell, [.....] then the issue would go away. Whether this is adequate or not, demands an answer to the question I asked in note 3849. The only (possible) answer to that was given in note 3997. If that is agreed, then the wording I suggest above (rephrased into standards speak however is appropriate) would be just fine. If the intended purpose of command -v is something different, then we need to discover what that is, and then how to meet that demand. If we have no idea what the purpose is (we cannot agree on any useful purpose for it to have) then we should simply delete it completely -- I know that cannot be done for tc3, but the wording could be changed to be so unspecific, that anything is OK, so that command -v is effectively useless to scripts - and a future direction could be added to say that it might go away in some future edition of the standard. Issue History Date Modified Username Field Change ====================================================================== 2017-09-04 13:09 steffen New Issue 2017-09-04 13:09 steffen Name => steffen 2017-09-04 13:09 steffen Section => command 2017-09-04 13:09 steffen Page Number => 2596 2017-09-04 13:09 steffen Line Number => 84274 ff. 2017-09-04 15:49 kre Note Added: 0003821 2017-09-05 06:58 stephane Note Added: 0003823 2017-09-05 08:30 stephane Note Added: 0003824 2017-09-05 12:34 steffen Note Added: 0003825 2017-09-05 12:39 steffen Note Added: 0003826 2017-09-05 12:47 kre Note Added: 0003827 2017-09-05 13:37 steffen Note Added: 0003828 2017-09-05 15:37 chet_ramey Note Added: 0003829 2017-09-05 15:41 stephane Note Added: 0003830 2017-09-05 16:01 stephane Note Added: 0003831 2017-09-05 16:36 stephane Note Added: 0003832 2017-09-05 17:30 stephane Note Added: 0003833 2017-09-05 20:17 steffen Note Added: 0003834 2017-09-05 20:19 steffen Note Added: 0003835 2017-09-05 20:27 kre Note Added: 0003836 2017-09-05 20:29 chet_ramey Note Added: 0003837 2017-09-05 21:27 eblake Note Added: 0003838 2017-09-05 21:50 kre Note Added: 0003839 2017-09-05 21:52 kre Note Edited: 0003839 2017-09-05 22:21 eblake Note Added: 0003840 2017-09-05 22:23 Don Cragun Note Added: 0003841 2017-09-05 22:24 Don Cragun Note Deleted: 0003841 2017-09-06 00:00 kre Note Added: 0003842 2017-09-06 00:00 kre Note Deleted: 0003839 2017-09-06 08:30 stephane Note Added: 0003843 2017-09-06 08:32 stephane Note Edited: 0003843 2017-09-06 09:30 stephane Note Added: 0003844 2017-09-06 09:37 stephane Note Added: 0003845 2017-09-06 09:50 joerg Note Added: 0003846 2017-09-06 09:50 joerg Note Edited: 0003846 2017-09-06 09:50 joerg Note Edited: 0003846 2017-09-06 09:54 stephane Note Edited: 0003845 2017-09-06 12:55 steffen Note Added: 0003847 2017-09-06 13:41 stephane Note Added: 0003848 2017-09-07 17:31 kre Note Deleted: 0003842 2017-09-07 17:58 kre Note Added: 0003849 2017-09-07 18:29 chet_ramey Note Added: 0003850 2017-09-07 21:17 kre Note Added: 0003851 2017-09-07 21:18 kre Note Edited: 0003851 2017-09-09 19:10 chet_ramey Note Added: 0003852 2018-04-25 17:57 McDutchie Note Added: 0003997 2019-01-24 17:11 nick Note Added: 0004220 2019-01-24 17:11 nick Interp Status => --- 2019-01-24 17:11 nick Final Accepted Text => See http://austingroupbugs.net/view.php?id=1161#c4220 2019-01-24 17:11 nick Status New => Resolved 2019-01-24 17:11 nick Resolution Open => Accepted As Marked 2019-01-24 17:12 nick Tag Attached: tc3-2008 2019-01-24 23:33 kre Note Added: 0004223 2019-01-25 00:05 kre Note Added: 0004224 ======================================================================
