Skip to main content
12 events
when toggle format what by license comment
Mar 30 at 12:15 history edited Sotto Voce CC BY-SA 4.0
Fixed typo in title: backtik -> backtick
Mar 30 at 11:38 comment added dAllARA Dear members all... Should I edit my question in order to clarify the actual issue? Let me know.
Mar 30 at 11:35 history closed muru
Kamil Maciorowski
MC68020
CommunityBot
Duplicate of Prevent wildcard expansion on find
Mar 30 at 11:34 answer added dAllARA timeline score: 1
Mar 30 at 11:23 comment added dAllARA @muru I didn't know the exact -name (or -iname) behaviour in find; you're right, indeed. Thanks, dear! unix.stackexchange.com/questions/773436/… yes! This helped me
Mar 30 at 10:36 comment added ilkkachu Too bad find doesn't have the equivalent of grep -F. Not even in GNU find, even though it supports various regex dialects via the -regextype option.
Mar 30 at 8:47 review Close votes
Mar 30 at 11:41
Mar 30 at 8:30 history edited muru
edited tags
Mar 30 at 8:30 comment added Kamil Maciorowski "$song" and "${song}" (and "*$song*", if you want to pass asterisks) are properly quoted and the value of the variable cannot break them. Bash cannot store null bytes in a variable, but filenames (pathnames in general) also cannot contain null bytes, so this shouldn't be a problem in this usage case. AFAIK everything else can be stored in a variable. If your code does not work as expected, it's not because allegedly "the variable cannot be quoted correctly"; it can.
Mar 30 at 8:30 history edited muru
edited tags
Mar 30 at 8:28 comment added muru I'd bet that the problem isn't the quotes. The problem is the text in [...], which is a shell glob, e.g., [2000] matches a 2 or 0, [CONCERTI] matches C, O, N, E, R, T or I.
Mar 30 at 8:10 history asked dAllARA CC BY-SA 4.0