A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1630 ====================================================================== Reported By: mirabilos Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1630 Category: Base Definitions Type: Clarification Requested Severity: Objection Priority: normal Status: New Name: mirabilos Organization: mksh User Reference: Section: 3.10 Page Number: (page or range of pages) Line Number: (Line or range of lines) Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-01-20 21:39 UTC Last Modified: 2023-02-24 10:03 UTC ====================================================================== Summary: Alias names ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001050 Add support for the hyphen character in... ======================================================================
---------------------------------------------------------------------- (0006171) geoffclare (manager) - 2023-02-24 10:03 https://austingroupbugs.net/view.php?id=1630#c6171 ---------------------------------------------------------------------- That's unfortunate. The plan was not only to decide whether to include the warning based on your feedback but also to base the "since this may cause problems when ..." part of the text on it. For filenames, problems can occur in common everyday interactive commands typed by users, such as "ls -l *.c", if a filename beginning with '-' happens to exist. (It can occur in shell scripts as well, of course, but I think these days shell script authors are more likely to take care to include "--", whereas users don't bother in interactive commands as it's more to type.) The only similar case for aliases I can think of would be some code to unalias or show the definition of a subset of the current aliases. Something like:<pre>for a in $alias_names; do case $a in (foo|bar) ;; (*) unalias "$a" ;; # or: alias "$a" esac done</pre> But this is far from "common everyday" stuff. Unless someone can come up with a use case that merits the warning, I expect we will end up rejecting this bug. Issue History Date Modified Username Field Change ====================================================================== 2023-01-20 21:39 mirabilos New Issue 2023-01-20 21:39 mirabilos Name => mirabilos 2023-01-20 21:39 mirabilos Organization => mksh 2023-01-20 21:39 mirabilos URL => https://austingroupbugs.net/view.php?id=1050 2023-01-20 21:39 mirabilos Section => 3.10 2023-01-20 22:30 kre Note Added: 0006122 2023-01-20 22:36 kre Note Added: 0006123 2023-01-20 22:38 kre Note Edited: 0006123 2023-02-09 17:08 nick Relationship added related to 0001050 2023-02-09 17:09 geoffclare Project Online Pubs => 1003.1(2016/18)/Issue7+TC2 2023-02-13 17:19 geoffclare Note Added: 0006149 2023-02-18 20:33 mirabilos Note Added: 0006156 2023-02-24 10:03 geoffclare Note Added: 0006171 ======================================================================
