Lisp is a language best "learned" furiously, through different dialects, implementations, extensions and library packages, and of course, thorough own implementation.
Clojure hasn't undergone the same vetting other dialects have gone thorough. Reading Common Lisp the Language (2nd Ed.) you will truly see what it takes to add a feature to a language and what it takes to remove it. 20+ people had to convince each other why something was worth keeping :-) And from there read the specs for ISLisp, EuLisp and and LeLisp. Schemes implementations have been a treasure trove of pure human genius: one implementation, T, has been responsible for so much it merits a year of your life just to read the associated literature and follow the heritage of this beautiful language.
Clojure has Rich Hickey's video, but none of it is, yet, time tested. A fine Lisp, no doubt, just not one for active learning.
I've been meaning to- and will, read PG's On Lisp. I saw the benefit in starting with Clojure being: the setup (basically nothing if you have a JVM installed) and the fact that applications created can be deployed in a JVM container- making it possible you any projects you'd like to host.
Your comment has inspired me to look into some of the schemes at least at the same time. Thanks.
www.dreamsongs.com/Files/HOPL2-Uncut.pdf
Once you know your Lisp, that paper will immerse you into the culture and history you need to become a bona fide Smug Lisp Weenie.
Lisp is not just a language, it's an ongoing and animated debate. Get your feet wet, get emacs and Slime, play around with all the dialects and implementations it supports, hack the good hack, send patches, ask for help, start a company, and welcome to the community! :-)
Now thats the first time I have heard a lisper say that.
I can see evidence that Clojure contributors have read it too, just the other day there was an example of an anaphoric macro posted on the mailing list. Very cool.