In vi or vim, search is started in command mode by hitting ESC then /, but it’s case-sensitive by default.
Searching for /year would only come up with the second occurrence of year.
Year one. Then year two.
Now to make it case-insensitive, prefix your search term with \c like \cyear and it’ll find both instances.
Issue
When trying to list, copy, move, etc with a * wildcard, the shell gives you an issue like “no such file or directory”
Cause
User account doesn’t have access to the directory or something else is preventing/causing “*” to be used as a literal than having the shell expand it
Solution
set +f
or
bash -c "ls -l directory/*"
When searching for files and only a single character or range is different, use the [square bracket] to locate the target.
$ ls -l file* -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file1 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file10 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file2 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file3 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file4 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file5 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file6 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file7 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file8 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file9 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:56 fileA -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:55 file_for_james -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:56 fileb -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:55 files_for_ken
With single character substitutions, the shell will attempt to locate files with each character in the brackets. Ex: file[abc] will locate filea, fileb, and filec.
$ ls -l file[aAB] -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:56 fileA
$ ls -l file[aABbc] -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:56 fileA -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:56 fileb
In range pattern matching, it can instead search a given range of characters instead. Ex: file[a-c] will locate filea, fileb, and filec. This is the same as file[abc] but the hyphen gives it a range which the shell will automatically expand for you. Range can also do numbers like file[1-3] .
$ ls -l file[1-5]* -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file1 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file10 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file2 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file3 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file4 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file5
Note: Both do the same thing
$ ls -l file[1-5,7-9]* -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file1 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file10 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file2 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file3 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file4 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file5 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file7 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file8 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file9 $ ls -l file[1-57-9]* -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file1 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file10 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file2 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file3 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file4 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file5 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file7 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file8 -rw-r--r-- 1 jvalero wheel 0 Jun 5 06:53 file9
Why did it also find file10 ? It was looking for anything matching file1* and file10 fits the bill. It doesn’t consider anything after the first range substitution character.
These are great tricks to narrow down searches, locate/use similarly named files, make queries more concise, and just look like a pro in shell expansion. Also check out my article about substituting whole words.
Single character/range pattern matching is great but we can do the same with strings. This way, there’s no need to repeat the entire length of the filename if a section has the same name. Check out the examples below using the {curly brace}.
$ touch {james,ken,ryu,vega,bison}_files.txt; ls -l
total 0
-rw-r--r-- 1 jvalero wheel 0 Jun 5 06:42 bison_files.txt
-rw-r--r-- 1 jvalero wheel 0 Jun 5 06:42 james_files.txt
-rw-r--r-- 1 jvalero wheel 0 Jun 5 06:42 ken_files.txt
-rw-r--r-- 1 jvalero wheel 0 Jun 5 06:42 ryu_files.txt
-rw-r--r-- 1 jvalero wheel 0 Jun 5 06:42 vega_files.txt
$ echo bad > bison_files.txt ; echo good > ken_files.txt ; echo good > ryu_files.txt
$ grep good {bison,ken,ryu}_files.txt
ken_files.txt:good
ryu_files.txt:good
Check this out. Lots of nice shortcuts to be a Bash shell wizard.
Need to extract key tags within a file.
These key tags are not predictable where it appears in a large file as there are nested within another parent tag. To make the problem even worse, it doesn’t always appear on the same line after the parent tag.
grep --include=*2015-10-06* --include=*20151005* -A15 "record\ product-id" * | grep -B5 value\>Out | grep record\ product-id* | awk -F\" '{print $2}' | sort -u
Close in areas you know and effectively use -A (lines to capture after keyword) and -B (lines to capture before keyword) to inch yourself closer to what you need. Consider unique patterns that relate to what you want to keep.
I’ve built a new aStore to keep an organized list of my product recommendations. Check it out
As the site is still getting redesigned/rebuilt, you may see a lot of random postings. Most of these are from my documentation notes. I may go back at a later time to make it more reader friendly.
test
test
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!