With gnu find you can use regex, which (unlike -name) match the entire path: To just count the number of files: (The %i format code causes find to print the inode number instead of the filename; unlike the filename, the inode number is guaranteed to not have characters like a newline, so counting is more reliable. Thanks to @tripleee for … Read more
There are two easy and safe rules which work not only in sh but also bash. 1. Put the whole string in single quotes This works for all chars except single quote itself. To escape the single quote, close the quoting before it, insert the single quote, and re-open the quoting. sed command: sed -e “s/’/’\\\\”/g; 1s/^/’/; \$s/\$/’/” 2. … Read more
You can use these ANSI escape codes: And then use them like this in your script: which prints love in red. From @james-lim’s comment, if you are using the echo command, be sure to use the -e flag to allow backslash escapes. (don’t add “\n” when using echo unless you want to add an additional empty line)
Normally, when a glob which does not match any filenames is expanded, it remains unchanged. Thus, you get results like this: $ rm .bak rm: cannot remove `.bak’: No such file or directory To avoid this we need to change the default value of nullglob variable. Read more about it here: http://mywiki.wooledge.org/NullGlob Hope this helps!
1277 Try: Or alternatively, with the short flags -qr: If you also want to see differences for files that may not exist in either directory:
You can output the variables to same file in stage, then read back and assign to env at the beginning of each stage as following:
You don’t have to call the external basename command. Instead, you could use the following commands: Note that this solution should work in all recent (post 2004) POSIX compliant shells, (e.g. bash, dash, ksh, etc.). Source: Shell Command Language 2.6.2 Parameter Expansion More on bash String Manipulations: http://tldp.org/LDP/LG/issue18/bash.html
More information: http://linux.about.com/library/cmd/blcmdl1_pkill.htm
Adapting the PATH should work. Just tried on my Git bash: In particular, only provide the directory; don’t specify the .exe on the PATH ; and use slashes.
Try: or (when file names include special characters such as spaces) The SLOCCount tool may help as well. It will give an accurate source lines of code count for whatever hierarchy you point it at, as well as some additional stats. Sorted output: find . -name ‘*.php’ | xargs wc -l | sort -nr