I am trying to delete certain text that appears before / on every line.
I have something like:
testing.db.com/7fad416d-f2b3-4259-b98d-2449957a3123
testing.db.com/8a8589bf-49e3-4cd7-af15-6753067355c6
and I just want to end up with:
7fad416d-f2b3-4259-b98d-2449957a3123
8a8589bf-49e3-4cd7-af15-6753067355c6
Can anyone help me with a regular expression? Everything I have found is deleting after /, not before.
Using cut :
$ cut -sd'/' -f2 file.txt ##This will print only the lines containing /
7fad416d-f2b3-4259-b98d-2449957a3123
8a8589bf-49e3-4cd7-af15-6753067355c6
The following suggestions assumes that / appears only once in a line :
Using grep :
$ grep -o '[^/]*$' file.txt ##This will print the lines not having / too
7fad416d-f2b3-4259-b98d-2449957a3123
8a8589bf-49e3-4cd7-af15-6753067355c6
If you have / in all of the lines, you can use these too:
Using bash parameter expansion:
$ while read line; do echo "${line#*/}"; done <file.txt
7fad416d-f2b3-4259-b98d-2449957a3123
8a8589bf-49e3-4cd7-af15-6753067355c6
Or python :
#!/usr/bin/env python2
with open('file.txt') as f:
for line in f:
print line.split('/')[1].rstrip()
Note that as far as your example is concerned all of the above suggestions are valid.
cut - because good work and that's what I came here to say. But you've got it in mixed company - for this task these commands are nowhere near equivalent. cut should be the only thing here - to make it act like grep -o use cut -sd. Those other two commands are merely a distraction. Run some time tests on large inputs and you'll see what I mean.
cut -d/ -f2- and ignore the other suggestions.
easy enough with sed:
echo "testing.db.com/7fad416d-f2b3-4259-b98d-2449957a3123" | sed -e "s/.*\///"
basic syntax is "s/search/replace/" and here we search for .*\/ which means everything ending with slash (escaped) and we replace it with nothing.
/ doesn't appear more than once per line
Using Perl:
< file.txt perl -pe 's/.*\///'
's|.*?/||' to bullet-proof the suggestion.
/; if there are more than one in the part to exclude than one should match greedily like I did, otherwise one should match lazily like you suggested. Not knowing this, since the string looks pretty regular (only composed by numbers and -), I'd prefer to bullet-proof the solution against possible subdirs in the link (e.g. testing.db.com/subdir)
Two methods using sed:
sed -i "s|testing.db.com/||g" file_path_here
or
echo "testing.db.com/7fad416d-f2b3-4259-b98d-2449957a3123" | sed -e "s|testing.db.com/||g"
awk -F/ '{print $2}' file > newfile