Quick links (alphabetically)

Additional (math) operators, relations and so onBeamerBibliographies and citationsClasses and class optionsCore conceptsCooperation with editors and non-TeX applicationsCorrect centeringCross-referencing, including hyperrefDatabasesDate and TimeDebugging & log filesDisaster recoveryDocumentation & Definition of commandsFigure/table numberingFigure/table (float) positioningFonts & font encodingFront matterImages/GraphicsIndexing and GlossariesInstalling, updating, restoring, other system operationsLists, itemize, enumerateMath environmentsMeta TeX.SENamingOld font macrosPage layout and outputSectioning and blocks of textSource code related issuesSpacing and pagination, hyphenation, line breakingSymbolsTable formattingTeaching/learning resources, and examplesText as textTheorems and friendsTikZ issues

I keep seeing the same bad coding styles being used in MWE or even recommended in answers or comments. There are also some FAQs (like the famous and repeatable asked how-to-place-my-figure-here question) which need to be linked to the appropriate existing question. Sometimes I have issues finding the related question quickly even if I already linked to it a couple of times before.

So I thought it would be good to have a collection of such often references questions sorted after topic in a meta post similar to our create Text building blocks.

Questions should be listed after topic. Every topic as CW answer to this post. Please use the following format:

## Topic Headline at Start of Answer Post

* [question title](http://tex.stackexchange.com/q/<question id>) [2 spaces] [linebreak]
 ``[question title](http://tex.stackexchange.com/q/<question id>)``

This way the question is provided as link (for quick access from this page) as well as markdown code suitable for comments (and as in-line link in a chat message). The URL can be received by using the link link below a question. There is also an stackapps app (modified by me) which produces this format. The include /<user id> should be removed to have the links in a neutral form. The two spaces and line break after the first line makes sure that the code starts at a new line.

Topic headers at the start of every answer post should be done using second order headlines, i.e. ## Topic. The first order headlines are a little to large IMHO.

  • 13
    Great list: thanks Martin!
    – Joseph Wright Mod
    Apr 14, 2012 at 16:43
  • 4
    @doncherry: Good idea with the quick links, thank you!
    – Jake
    May 8, 2012 at 19:58
  • @Jake: I was thinking to add a bullet-point list at the bottom myself, but it didn't looked good. I like the top list in this form much better. May 8, 2012 at 20:03
  • @MartinScharrer I'm not sure if the format with several categories in separate answers is working out. We have 26 questions in 12 answers, that's about two per category, and whenever I want to add a question, I'm having trouble finding the right category. One answer with broader categories might be a better solution and more flexible?
    – doncherry
    Nov 16, 2012 at 21:34
  • @JosephWright Would it be useful to add tex.stackexchange.com/questions/255709/… here? If so, does it belong with Installing or Fonts? I hesitate to just add it because it may be only frequently referenced by me and I don't want to use this meta-post for self-advertising ....
    – cfr
    Nov 1, 2016 at 4:16

35 Answers 35


Date and Time


Disaster recovery


Core concepts


Cooperation with editors and non-TeX applications

Input (editors)

Output (PDF readers)

Other tools


Page layout and output

Design examples and methods


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .