LaTeX
This is a guide to the LaTeX markup language. It is intended to form a useful resource for everybody from new users who wish to learn, to old hands who need a quick reference. TeX and LaTeX TeX is a computer program for typesetting documents, created by Donald Knuth. It takes a suitably prepared computer file and converts it to a form which may be printed on many kinds of printers, including dot-matrix printers, laser printers and high-resolution typesetting machines. LaTeX is a set of macros for TeX that aims at reducing the user's task to the sole role of writing the content, LaTeX taking care of all the formatting process. The book is organized in different parts. Getting Started will provide you with the very first steps to print your first document: general concepts (very important!) Contents[edit] If you have questions related to LaTeX, ask at the Q&A. Edit the TOC or the stages Other wikibooks[edit]
Knotsbag
LaTeX:Layout
From AoPSWiki This article outlines some of the basics of layout in LaTeX. Note: Rather than typing up all the examples, you can copy-paste the examples into your TeXnicCenter files. Source File Format The source file of a LaTeX broadly consists of two parts, the preamble and the document itself. Our next three sections deal primarily with preamble items, while the rest cover tools you might use within your document. The Preamble Document Class The first line of the file sets the document class with the \documentclass[''options'']{''class''} command. article . book report , and letter .) \documentclass , but generally they can be left to their defaults. Packages Packages are included after the \documentclass statement using \usepackage[''options''][''packagename''] . Page Setup LaTeX automatically sets reasonable values for the page dimensions, orientation, etc. The Easy Way The easy way involves using certain packages to do the heavy lifting. \usepackage[margin=2.5cm]{geometry} . \usepackage{parskip} The
SWIG: Wrapper and Interface Generator
LaTeX/Formatting
Altering the paragraph formatting is not often required, especially in academic writing. However, it is useful to know, and applications tend to be for formatting text in floats, or other more exotic documents. Paragraph alignment[edit] Paragraphs in LaTeX are usually fully justified, i.e. flush with both the left and right margins. All text between the \begin and \end of the specified environment will be justified appropriately. Paragraph indent and break[edit] By default, the first paragraph after a heading follows the standard Anglo-American publishers' practice of no indentation. White-space in LaTeX can also be made flexible (what Lamport calls "rubber" lengths). If you want to indent a paragraph that is not indented, you can use at the beginning of the paragraph. To create a non-indented paragraph, you can use as the first command of the paragraph. To indent subsequent lines of a paragraph, use the TeX command \hangindent. \paragraph line break[edit] Anyway, let's analyse the problem.
How to Report Bugs Effectively
There are a number of ways in which non-programmers can contribute to software projects; documentation and testing are among the most frequently-requested services, but testing that results in useless bug reports accomplishes nothing but frustrating the programmer. Today, Simon Tatham shares what it's like to be on the receiving end of bug reports, and offers suggestions for how you can help resolve problems as quickly as possible. Introduction Anybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. There's a reason why technical support is seen as a horrible job to be in, and that reason is bad bug reports. In this essay I'll try to state clearly what makes a good bug report. In a nutshell, the aim of a bug report is to enable the programmer to see the program failing in front of him.
Undoing Changes | Ry's Git Tutorial
‹ Back to Ry’s Git Tutorial In the last module, we learned how to record versions of a project into a Git repository. The whole point of maintaining these “safe” copies is peace of mind: should our project suddenly break, we’ll know that we have easy access to a functional version, and we’ll be able to pinpoint precisely where the problem was introduced. To this end, storing “safe” versions isn’t much help without the ability to restore them. If you’ve been following along from the previous module, you already have everything you need. Display Commit Checksums As a quick review, let’s display our repository’s history. The output for this should look similar to the following, but contain different commit checksums. 1c310d2 Add navigation links 54650a3 Create blue and orange pages b650e4b Create index page Git only outputs the first 7 characters of the checksum (remember that you can see the full version with the default formatting of git log). View an Old Revision View an Older Revision <!
