| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
a single newline) immediately after their opening brace; this was
causing a normal paragraph to be started, thus making it fiddly and
annoying to arrange the first paragraph of a \lcont to be a code
para or anything else special. Now fixed.
[originally from svn r4005]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
markup feature: a \c line in a code paragraph can now be followed by
an optional \e line indicating emphasised bits of its preceding \c.
This allows discretionary bolding and (italic/underline) emphasis
within code paragraphs, but without introducing an escape character
or breaking any existing input files. Users are warned that not all
backends are required to actually render these hints, and so they
should avoid depending on them 100% to convey semantic information
unless they know they're writing for a restricted range of backends.
[originally from svn r3965]
|
| |
|
|
|
|
|
|
|
| |
features commonly used in man pages: (a) the ability to nest
paragraph breaks, code paragraphs and other lists inside list items,
and (b) description lists as normally used in man pages to describe
command-line options.
[originally from svn r3954]
|
| |
|
|
|
|
|
| |
blank-line separators (config directives visually _want_ to be in a
single chunk).
[originally from svn r1837]
|
| |
|
|
| |
[originally from svn r1800]
|
| |
|
|
| |
[originally from svn r1490]
|
| |
|
|
|
|
|
|
|
|
| |
sections. Useful if another program needs to jump to a particular
topic. (Really we should support the proper CTXOMAP / HELP_WM_HELP
system for doing this, but I don't like numeric IDs; you'd have to
parse a bunch of #defines in order to sensibly synchronise the IDs
between help file and code.)
[originally from svn r1457]
|
| |
|
|
|
| |
[originally from svn r1446]
[this svn revision also touched putty]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
`question' or so on, using the syntax
\S{mysection}{example} An example of foobar
so that in cross-references it will be referred to as `example
5.1.2' instead of `section 5.1.2'. NOTE WELL: until now Buttress has
supported multiple section keywords using the same syntax, so that
you could xref the above section as \k{mysection} _or_ \k{example}
with the same effect. This behaviour is now revoked because I don't
think anyone was using it; if you suddenly find you're getting
undefined-keyword errors this may be why.
[originally from svn r1408]
|
| |
|
|
|
|
|
|
|
|
| |
user doesn't skip a heading level (\H before any \C or \A, or \S
straight after \C with no intervening \H). The precise criterion is
that when creating section a.b.c.d, sections a.b.c, a.b and a should
already exist. This ensures the section tree really is a properly
formed tree with no missing nodes.
[originally from svn r1329]
|
| |
|
|
| |
[originally from svn r1325]
|
| |
|
|
| |
[originally from svn r828]
|
| |
|
|
| |
[originally from svn r810]
|
| |
|
|
| |
[originally from svn r274]
|
| |
|
|
| |
[originally from svn r254]
|
| |
|
|
| |
[originally from svn r252]
|
| |
|
|
| |
[originally from svn r248]
|
| |
|
|
| |
[originally from svn r241]
|
| |
|
|
| |
[originally from svn r220]
|
| |
|
|
| |
[originally from svn r200]
|
| |
|
|
| |
[originally from svn r193]
|
| |
|
|
| |
[originally from svn r187]
|
| |
|
|
| |
[originally from svn r27]
|
|
|
[originally from svn r25]
|
