Timeline for Asterisk in file path in MacOS Ventura
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2023 at 1:15 | comment | added | dmg15 | I understand the use of the asterisk as a wildcard in the command line, I didn't know about the double asterisk though, so thank you for that Allan. However, as Barmar mentioned, it's not being used as a wildcard in this context. At least, It doesn't make sense that it would be a wildcard in this context. Usually that section of little snitch would show the enclosing folder of the binary, which is a property that shouldn't contain a wildcard. | |
| Dec 13, 2023 at 16:35 | comment | added | Barmar | The context of this isn't a shell command line, it's the output of an application (Little Snitch in this case) that should be showing the path to an actual file. Why would a wildcard be there? | |
| Dec 13, 2023 at 7:16 | comment | added | fd0 | works with ksh and bash 5 | |
| Dec 13, 2023 at 7:10 | comment | added | nohillside♦ |
** only works in zsh.
|
|
| Dec 13, 2023 at 7:07 | history | answered | Allan | CC BY-SA 4.0 |