A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1234 ====================================================================== Reported By: stephane Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1234 Category: Shell and Utilities Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: Stephane Chazelas Organization: User Reference: Section: 2.13.1 Page Number: 2382 Line Number: 76212-76215 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2019-03-08 23:58 UTC Last Modified: 2019-03-12 12:15 UTC ====================================================================== Summary: in most shells, backslash doesn't have two meaning wrt pattern matching ======================================================================
---------------------------------------------------------------------- (0004313) kre (reporter) - 2019-03-12 12:15 http://austingroupbugs.net/view.php?id=1234#c4313 ---------------------------------------------------------------------- Re: http://austingroupbugs.net/view.php?id=1234#c4309 (I wonder if that will work?) You probably mean eval ls -l "$var" without the quotes you'd get pathname expansion on $var (files that start with a '*' for example - however that is encoded in var) and then the eval would do pathname expansion again on each of the results from the first time. That's rarely going to be what anyone wants. But for the form with quotes in it, imagine var="[']*.c" then what the eval sees is eval ls -l [']*.c That isn't going to work at all. There's often (but not always) a way to code around this, but then it means that the variable needs to be different to be used in glob expansions like this, and in case patterns, or parameter expansion substring operators - and certainly as an arg to find. The same thing ought to be able to be used, with the same meaning in all of those contexts. Issue History Date Modified Username Field Change ====================================================================== 2019-03-08 23:58 stephane New Issue 2019-03-08 23:58 stephane Name => Stephane Chazelas 2019-03-08 23:58 stephane Section => 2.13.1 2019-03-08 23:58 stephane Page Number => 2382 2019-03-08 23:58 stephane Line Number => 76212-76215 2019-03-11 02:42 kre Note Added: 0004296 2019-03-11 02:58 kre Note Edited: 0004296 2019-03-11 03:07 kre Note Edited: 0004296 2019-03-11 03:10 kre Note Added: 0004297 2019-03-11 03:16 kre Note Edited: 0004296 2019-03-11 03:23 kre Note Added: 0004298 2019-03-11 07:24 stephane Note Added: 0004300 2019-03-11 07:31 stephane Note Added: 0004301 2019-03-11 09:41 geoffclare Note Added: 0004303 2019-03-12 03:24 kre Note Added: 0004306 2019-03-12 03:37 kre Note Added: 0004307 2019-03-12 03:38 kre Note Deleted: 0004297 2019-03-12 09:13 Konrad_Schwarz Note Added: 0004309 2019-03-12 09:58 geoffclare Note Added: 0004310 2019-03-12 12:13 Don Cragun Note Edited: 0004306 2019-03-12 12:14 Don Cragun Note Edited: 0004306 2019-03-12 12:15 kre Note Added: 0004313 ======================================================================
