This executable is provided as a part of the Caja package for the MATE Desktop Environment.

.SH "BUGS"

.SS Should you encounter any bugs, they may be reported at:

.SH "LICENSE"

GPL v2 or later

.SH "SEE ALSO"

.SS

Caja documentation can be found from the "Help" menu, or by pressing the F1 key.

.P

.BR "caja" (1),

.BR "caja-connect-server" (1),

Print all command line options.

.SH "BUGS"

.SS Should you encounter any bugs, they may be reported at:

.SH "AUTHORS"

.SS This Man Page has been written for the MATE Desktop Environment by:

Adam Erdman <[email protected]> (2014)

.SH "SEE ALSO"

.SS

Caja documentation can be found from the "Help" menu, or by pressing the F1 key.

.P

.BR "caja" (1),

.BR "caja-autorun-software" (1),

You can specify appearance preferences for the Default View; and defaults for Icon, Compact, List, and Tree View; and select sort options and display options. You can configure Caja to recognize Single or Double Click input; as well as Include a Delete command and menu option that bypasses the Trash. Caja File Management Preferences (\fBcaja-file-management-properties\fR) also allows you to tell Caja how to handle certain files; whether to View or Run executable text files; Automatically view or play Media like CDs, DVDs, or photos, and which applications to use when performing these tasks. Among some other options, this dialog also allows you to adjust file-preview settings, and settings for installed plugins if they exist.

.SH "BUGS"

.SS Should you encounter any bugs, they may be reported at:

.SH "AUTHORS"

.SS This Man Page has been written for the MATE Desktop Environment by:

Adam Erdman <[email protected]> (2014)

.SH "SEE ALSO"

.SS

Caja documentation can be found from the "Help" menu, or by pressing the F1 key.

.P

.BR "caja" (1),

.BR "caja-autorun-software" (1),

Open a Caja window that is 600 pixels wide by 400 pixels high.

.SH "BUGS"

.SS Should you encounter any bugs, they may be reported at:

.SH "AUTHORS"

.SS This Man Page has been updated/re-written for the MATE Desktop Environment by:

Adam Erdman <[email protected]> (2014)

.SH "SEE ALSO"

.SS

Caja documentation can be found from the "Help" menu, or by pressing the F1 key.

.P

.BR "caja-file-management-properties" (1),

.BR "caja-autorun-software" (1),

C++ standard itself also contain useful introductory material. For some

programmers, these are enough to explain the features of the language.</p>

Bjarne Stroustrup. This is the book by the creator of the C++ language. This third edition is far superior

to the first two, and covers the ISO Standard version of the language in detail, including the library.

Any serious C++ programmer should read this book. There have been many corrections since the first printing, so get

the newest printing you can. Bjarne has <a href="http://www.research.att.com/~bs/3rd.html">supporting materials</a>

for the book on the web, including the errata lists that enumerate all changes between printings.</p>

Nicolai M. Josuttis. This book has the best coverage of the library. There have been tons of others that cover

the library, or focus on the STL or streams. But Josuttis covers all these subjects better than any of his

predecessors. Since we use the library extensively in Eazel projects, this is a must read.

This kind of idiomatic programming is important in C++, because the language

gives you so much freedom to write unusable, unmaintainable code.</p>

Herb Sutter. This is a collection of material that was originally part of Herb's

<a href="http://www.peerdirect.com/resources"><i>Guru of the Week</i></a>. This includes much of the most

advanced C++ information available. I learned many of the most important techniques from Herb, including

the swap technique for writing safe assignment operators. Herb covers each topic thoroughly.</p>

Andrew Koenig and Barbara Moo.</p>

Scott Meyers. These books contain a laundry list of important C++ idioms. The books are a bit less

important now than when they were first released, but still full of valuable stuff. There's also a

(there's a <a href="http://mox.eazel.com/mec">copy</a> of it on Rob's machine)

that contains both books in electronic form. The publisher's web site has a good collection of

supporting materials for both

<a href="http://cseng.aw.com/bookdetail.qry?ISBN=0-201-92488-9">the original</a> and

<a href="http://cseng.aw.com/bookdetail.qry?ISBN=0-201-63371-X">the second book</a></p>

Bjarne Stroustrup. While this book doesn't prescribe any specific techniques, it will help you understand the

tradeoffs behind all the language features, and how C++ got to be what it is. I highly recommend it.</p>

<p>These books explain C++ programming from scratch. These particular examples are so good that they

can be useful even for experienced programmers who already know C++ well.</p>

Stanley Lippman. This tutorial is much more useful than the longer and more complete works, like

<a href="#Primer"><i>C++ Primer</i></a>.

It covers the features and the reasons for the features quite well. In particular, it has a good explanation

<p>OK, so I'm not an expert on Gtk yet. But I'm becoming one.</p>

Havoc Pennington. I learned a lot from this book. But it's all Gtk+ and C; things are done

a bit differently with Gtk-- from C++. It's still worth reading.</p>

<p>These books are valuable because of the ideas in them, but are not specific to a particular programming language or toolkit.</p>

Martin Fowler. This book outlines a philosophy of programming that we embrace at Eazel. The ideas

about changing existing code to improve it so it can be modified are extremely important. The ideas

about unit testing as a means to this end shape the way we use unit testing at Eazel.

All the examples in the book are in Java, but the ideas apply well to C++.</p>

Brian Kernighan, Rob Pike. This book, by two of the most famous UNIX programmers, covers a lot of basic

programming smarts. I don't agree with everything they have to say, but the book is great as a whole.</p>

Jon Bentley. This classic has recently been updated with a second edition. I haven't read the second edition

yet, but I'm sure it's great. When I read it, I'll put more specific comments here.</p>

(there's a <a href="http://mox.eazel.com/dp">copy</a> of it on Rob's machine).</p>

<h2>Books I Have Read, But Do Not Recommend</h2>

from the truly awful. If you see a book that's not on this list, it might be one I'd recommend. Maybe

I haven't read it.</p>

Steve Teale. <a href="Josuttis">Josuttis</a> covers streams better.</p>

My love for <a href="Refactoring"><i>Refactoring</i></a> had me excited about this one, but it was a disappointment.</p>

Matt Austern. I don't know of anyone who knows more about the STL than Matt Austern, who's currently

maintaining the main implementation at SGI. But <a href="Josuttis">Josuttis</a> covers the STL better.</p>

John Lakos.</p>

This is a basically an "Eiffel is great, C++ sucks" book. Some interesting insights, but a lot of sloppy thinking.</p>

<h2>Books That Need Review</h2>

<p>This is a list of possibly important books that I haven't checked out yet.</p>

Stanley Lippman, Josee Lajoie. The earlier editions were good but not great. But I have reason

to believe that this one might be better than those were.</p>

I checked, and this answer book does go with the third edition of <i>C++ Primer</i>.</p>

</body>

<p>To make code written for Caja look and act in a predictable way,

we follow a set of guidelines that specify some details of how we write code.

To start, we follow all the guidelines outlined in the

<p>This document covers both things that are not mentioned in the MATE

Programming Guidelines and things that are mentioned there but need