Try putting it in quotes — you’re running into the shell’s wildcard expansion, so what you’re acually passing to find will look like: find . -name bobtest.c cattest.c snowtest.c …causing the syntax error. So try this instead: find . -name ‘*test.c’ Note the single quotes around your file expression — these will stop the shell … Read more
As pointed out by Max, you can’t, but checking files modified or accessed is not all that hard. I wrote a tutorial about this, as late as today. The essence of which is to use -newerXY and ! -newerXY: Example: To find all files modified on the 7th of June, 2007: $ find . -type … Read more
As pointed out by Max, you can’t, but checking files modified or accessed is not all that hard. I wrote a tutorial about this, as late as today. The essence of which is to use -newerXY and ! -newerXY: Example: To find all files modified on the 7th of June, 2007: $ find . -type … Read more
I combined the template format used by John Myczek and Tri Q’s algorithm above to create a findChild Algorithm that can be used on any parent. Keep in mind that recursively searching a tree downwards could be a lengthy process. I’ve only spot-checked this on a WPF application, please comment on any errors you might … Read more
If you are on a OS X, this probably has nothing to do with the sed command. On the OSX version of sed, the -i option expects an extension argument so your command is actually parsed as the extension argument and the file path is interpreted as the command code. Try adding the -e argument … Read more
>>> d = {‘1’: ‘one’, ‘3’: ‘three’, ‘2’: ‘two’, ‘5’: ‘five’, ‘4’: ‘four’} >>> ‘one’ in d.values() True Out of curiosity, some comparative timing: >>> T(lambda : ‘one’ in d.itervalues()).repeat() [0.28107285499572754, 0.29107213020324707, 0.27941107749938965] >>> T(lambda : ‘one’ in d.values()).repeat() [0.38303399085998535, 0.37257885932922363, 0.37096405029296875] >>> T(lambda : ‘one’ in d.viewvalues()).repeat() [0.32004380226135254, 0.31716084480285645, 0.3171098232269287] EDIT: And in case … Read more
To find all files modified in the last 24 hours (last full day) in a particular specific directory and its sub-directories: find /directory_path -mtime -1 -ls Should be to your liking The – before 1 is important – it means anything changed one day or less ago. A + before 1 would instead mean anything … Read more
In GNU find you can use -printf parameter for that, e.g.: find /dir1 -type f -printf “%f\n”
The comm command (short for “common”) may be useful comm – compare two sorted files line by line #find lines only in file1 comm -23 file1 file2 #find lines only in file2 comm -13 file1 file2 #find lines common to both files comm -12 file1 file2 The man file is actually quite readable for this.
This will recursively traverse the /path/to/folder directory and list only the symbolic links: ls -lR /path/to/folder | grep ^l If your intention is to follow the symbolic links too, you should use your find command but you should include the -L option; in fact the find man page says: -L Follow symbolic links. When find … Read more