Getting the Absolute Path

The :a modifier takes the file path and converts it to an absolute path,
expanding relative ".." paths in the process. As you can expect, it doesn't
take into consideration any directory changes, as in:

What did I just run?

You can use the :c modifier to get the file path to the command
that you ran. Why is that important? Probably helpful when something
goes wrong, for instance, let's suppose I ran this cp command, and
I didn't want the Extended Attributes (EAs) or resource forks on my
Mac system:

$ cp -X nothing.clj /tmp
cp: invalid option -- 'X'

What is going on with my Mac!? I try to diagnose what I
previously did:

$ !cp:0:c ## CMD --> Expand to:
$ /opt/local/bin/gcp

Oh! I'm not using the cp command that came with my system, but
picked up a GNU library version… that explains the difference.

That wasn't too much of a contrived example, was it?

Now we're getting ridiculous

The :s modifier is a regular expression conversion… which is
either overkill or freakin' crazy (depending on who you ask):