We have come some distance in these preliminary chapters, having examined the historical basis for a new theory of dreams, the epistemological problem concerning the evidence of dream-life, the grounds for considering dreaming as a form of unconscious thinking equivalent to the actions and play of babies and small children, a theory of symbolism which places it at the core of the process for thinking about the meaning of our emotional experiences, and finally an outline of the theory of extended metap-sychology upon whose foundation we wish to construct our theory of dreams. It is necessary now to outline the theory itself so that we may examine its various components in some greater detail.
Let us start some dream material to which we may refer back as we go along. You will recall the four “crucifixion” dreams: the cleared bridle-way, but for the hazel saplings; the young couple worshipping their tomato plant; the inhibited necrophilia; and the paralysis by Mr Parker 51. Let us add to that series another duet of dreams from a young man who returned to analysis after a weekend reporting that he had a new girl-friend who seemed very interested in him, had gone back to his flat with him but had probably been disappointed that he had made no sexual advance to her. The trouble had been that he had not yet written the lecture which he had to deliver the morning of the session to his senior colleagues, although he had known of it for over a month. Not only had he disappointed the girl but he had had to cancel a lecture to his students as well. Two little dream images were vivid in his mind from the brief nap he had had in his office after writing until five in the morning.
Freed, as such bodies are, from the sure bounds to the schemes of individuals—the grave—they are able to add field to field, and power to power, until they become entirely too strong for that society which is made up of those whose plans are limited by a single life. —Supreme Court of Georgia, Railroad Co. v. Collins, 1929
EARLY MORNING AT THE Dallas/Fort Worth Airport. As I step out to the taxi curb, I feel a coolness in the air that I suspect will not stick around once that big Texas sun reports for duty. I have arrived on a redeye flight, and as I take a taxi into the city I imagine the inhabitants waking up and drinking their breakfast coffee. I’ve never been to Dallas before (“The place where Kennedy got shot” keeps sneaking into my thoughts), but the driver of my cab, a man full of stories and warm southern exuberance, quickly puts me at ease. Turning off his meter, he takes me the long way to my hotel, pointing out the local sights.
Far less welcoming is the darkened hall of grandiose proportions where I eventually find myself, in the midst of a hushed, submissive audience. In front is a podium raised to an unnatural height, where Lee Raymond, chairman and CEO of ExxonMobil Corporation, announces the company’s recent triumphs and outlines its strategy going forward. Above the stage is the glowing logo of the corporation, and next to the logo, in a touch of exquisite irony, a glistening blue image of Planet Earth hangs in midair as though floating through space.
If you write either large programs or long documents, you have
probably been caught at least once in a situation where
you've made changes that turned out to be a bad
thing, only to be confused and stymied because you
weren't sure exactly how to reverse them and get
back to a known good
state. Or, perhaps you've released a program or
document to someone else, then gotten a bug fix or a comment that you
couldn't integrate properly because you
couldn't recover the old version that person was
working with. Perhaps you're a member of a
development or documentation team and have felt the need for some way
to keep change histories, indicating who was responsible for each
These common kinds of problems can be addressed with a
version control system. A version control system
gives you automated help at keeping a change history for a file or
group of files. It allows you to recover any stage in that history,
and it makes getting reports on the differences between versions
Today a variety of version control systems are widely available on
machines that run Emacs. Some are commercial, but there are a wealth
of free, open, and powerful choices, and it seems appropriate for our
discussion to focus on these. Historically, Emacs evolved largely in
a Unix environment alongside the SCCS and RCS systems, and its
built-in support for version control reflects their approach and
terminology. Today the most popular by far is CVS (which builds on
RCS, giving it more flexibility and power), and there is a new system
called Subversion that is starting to catch on. Preliminary support
for working with Subversion shipped with Emacs 21.3.5; its
documentation suggests you check the Subversion site, http://subversion.tigris.org/, for updates.