*.txt is expanded by your shell into file1.txt file2.txt … automatically. If you quote *.txt, it doesn’t work: [~] ls “*.py” ls: cannot access *.py: No such file or directory [~] ls *.py file1.py file2.py file3.py If you want to get files that match your pattern, use glob: >>> import glob >>> glob.glob(‘/etc/r*.conf’) [‘/etc/request-key.conf’, ‘/etc/resolv.conf’, … Read more
You are confusing regular expression with shell globbing. If you want to use regular expression to match file names you could do: $ ls | egrep ‘.+\..+’
this is one: ls -l . | egrep -c ‘^-‘ Note: ls -1 | wc -l Which means: ls: list files in dir -1: (that’s a ONE) only one entry per line. Change it to -1a if you want hidden files too |: pipe output onto… wc: “wordcount” -l: count lines.
It would be this array=($(ls -d */)) EDIT: See Gordon Davisson’s solution for a more general answer (i.e. if your filenames contain special characters). This answer is merely a syntax correction.
Unfortunately your quest won’t be possible in general, as there are only 3 distinct time values stored for each of your files as defined by the POSIX standard (see Base Definitions section 4.8 File Times Update) Each file has three distinct associated timestamps: the time of last data access, the time of last data modification, … Read more
Use find: find . find /home/dreftymac If you want files only (omit directories, devices, etc): find . -type f find /home/dreftymac -type f
Use find: find . -name \*.txt -print On systems that use GNU find, like most GNU/Linux distributions, you can leave out the -print.
If you give find an absolute path to start with, it will print absolute paths. For instance, to find all .htaccess files in the current directory: find “$(pwd)” -name .htaccess or if your shell expands $PWD to the current directory: find “$PWD” -name .htaccess find simply prepends the path it was given to a relative … Read more
Use egrep-style extended pattern matching. ls !(*.jar) This is available starting with bash-2.02-alpha1. Must first be enabled with shopt -s extglob As of bash-4.1-alpha there is a config option to enable this by default.
This is exactly why you should not use UPPER_CASE_VARS. $PATH is a variable used by the shell to find executables on your system. As soon as you over-write it with user input, your script can no longer find anything that does not reside in whatever the input was. In this case, you entered /bin, so … Read more