Marc -- ...and then Marc Chamberlin said... % % On 03/16/2017 06:44 PM, David T-G wrote: % > ... % >grep insists that the first pattern it gets is its search pattern. Even % >if you have a file called 'run' in the current directory, it's going to % >look for that string. If you don't put anything after the pattern, it's % >going to search stdin. % % Then Hann, I refer you back to my original posting asking why this % simple grep command failed in certain directories? The answer that I Did you ever provide a listing of the contents of your example directory? I've been watching this thread, and if you sent it I must have missed it. I'm very interested in what that period-space appears to be and how it played into your command line, not least because * does not pick up "hidden" files (those starting with a period). % got, (at least my interpretation of the answers) was that it failed % because there are file names in the directory which had the string % "run" within the filename... Hence the need for the double dashes as I believe your interpretation is incorrect. % the first parameter in order to get this grep command to work.. % Please review this thread from the beginning... I just went back and looked again, and I still don't see any further diagnostic information from you. If you wish an explanation of the cause beyond Linda's excellent suggestion to de-argument-ify the tokens on the command line, you should show us with what you're working. % % Marc.. HANN again & I'm off to bed to see the rest of this tomorrow :-) :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org