| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
[originally from svn r4007]
|
| |
|
|
|
|
|
|
|
| |
the preamble: \copyright paragraphs are now treated identically to
normal paragraphs (so they appear precisely where they're put
instead of in a fixed location), _except_ that the Windows Help
backend also copies their text into the help file's copyright slot.
[originally from svn r4001]
|
| |
|
|
|
|
| |
so. It's restorable using \IM.
[originally from svn r4000]
|
| |
|
|
| |
[originally from svn r3999]
|
| |
|
|
|
|
|
| |
Jacob points out that I didn't specify whether inline formatting
commands can surround line breaks (they can).
[originally from svn r3994]
|
| |
|
|
|
|
|
|
| |
I _think_ the manual now contains all the information a user should
need, even if not yet in an optimal order for a beginner to learn
from.
[originally from svn r3989]
|
| |
|
|
|
|
|
|
|
| |
zero-width delimiter between a macro invocation and text beyond it,
so that you can define (say) a macro which expands to a Euro sign
and then write `\eur\.2500' to avoid having space between the Euro
sign and the number.
[originally from svn r3982]
|
| |
|
|
|
|
|
|
|
|
| |
any ordinary displayable paragraph(s) appearing before the first
chapter heading, meaning in particular that you can put lists, code
paragraphs etc in preambles. Of course, `\preamble' is still
supported for backwards compatibility, but it's now a zero-effect
paragraph marker.
[originally from svn r3981]
|
|
|
(nearly nonexistent) invocation syntax and the input format.
[originally from svn r3979]
|
