How to remove everything before the first : if there are 2 :'s in the file?

AveravaDevs

Example:
jones:hype:fire
jonathan:fire:man
kill:death:fire

I want kill, jonathan, and jones and the : after them removed, leaving only this:
hype:fire
fire:man
death:fire

PeterJones

Thanks for an example with both before and after. It helps.

Find What = (?-s)^.*?:(?=.*:)
Replace With = (empty)
Search Mode = regular expression

Search =

(?-s) = turn off .-matches-newline (overrides the checkbox later in the dialog box)
^ = start the match at the beginning of the line
.*? = match 0 or more characters before…
: = a literal colon
(?=.*:) = the colon must be followed by 0 or more characters and another colon, but don’t include this bit in the stuff to be replaced. If there isn’t a second colon on the line, it won’t match the earlier stuff, so no replace will occur for that line

Replace up through the first colon with nothing, if the given line matches everything above

-----

FYI:

This forum is formatted using Markdown, with a help link buried on the little grey ? in the COMPOSE window/pane when writing your post. For more about how to use Markdown in this forum, please see @Scott-Sumner’s post in the “how to markdown code on this forum” topic, and my updates near the end. It is very important that you use these formatting tips – using single backtick marks around small snippets, and using code-quoting for pasting multiple lines from your example data files – because otherwise, the forum will change normal quotes ("") to curly “smart” quotes (“”), will change hyphens to dashes, will sometimes hide asterisks (or if your text is c:\folder\*.txt, it will show up as c:\folder*.txt, missing the backslash). If you want to clearly communicate your text data to us, you need to properly format it.

If you have further search-and-replace (“matching”, “marking”, “bookmarking”, regular expression, “regex”) needs, study this FAQ and the documentation it points to. Before asking a new regex question, understand that for future requests, many of us will expect you to show what data you have (exactly), what data you want (exactly), what regex you already tried (to show that you’re showing effort), why you thought that regex would work (to prove it wasn’t just something randomly typed), and what data you’re getting with an explanation of why that result is wrong. When you show that effort, you’ll see us bend over backward to get things working for you. If you need help formatting, see the paragraph above.

Please note that for all regex and related queries, it is best if you are explicit about what needs to match, and what shouldn’t match, and have multiple examples of both in your example dataset. Often, what shouldn’t match helps define the regular expression as much or more than what should match.