Age | Commit message (Collapse) | Author | Files | Lines |
|
This was failing because of a small discrepancy in markdown
table header line lengths on appveyor.
It's a minor issue, I can't see what is causing it, and
it's irrelevant to the issue this is testing, so we'll
just write native for this test.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We now use static-linux to create the deb.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also build pandoc-citeproc.
Put pandoc and pandoc-citeproc executables into a version-labeled tgz.
|
|
This also affects the Markdown reader.
Closes #3257.
|
|
|
|
This should address appveyor test failures.
|
|
This is meant to address a test failure on appveyor.
|
|
* Use -split-objs (reduces executable size from ~50M to 32M), at
cost of much slower compilation.
* Moved building of prereqs from CMD to RUN, so they can be cached.
Doing 'make build' will fetch the latest from git and rebuild
pandoc, but dependencies needn't be rebuilt.
|
|
This provides a Makefile and Dockerfile sufficient for
producing a completely statically linked linux executable
for maximum portability.
If docker is installed, this should suffice:
make setup
make build
The binary will be placed in artifacts/.
|
|
|
|
Closes #256.
|
|
This contains a list of strings that will be recognized by pandoc's
Markdown parser as abbreviations. (A nonbreaking space will
be inserted after the period, preventing a sentence space in
formats like LaTeX.)
Users can override the default by putting a file abbreviations
in their user data directory (`~/.pandoc` on *nix).
|
|
|
|
Previously you could link to a header above or below slide
level but not TO slide level. This commit changes that.
Hypertargets are inserted inside frame titles; technically
the reference is to just after the title, but in normal
use (where slides are viewed full screen in a slide show),
this does not matter.
Closes #3220.
|
|
|
|
The old characters weren't available in some font sets.
These seem to work well on Windows and Linux versions of LibreOffice.
Closes #1400.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #1905.
Removed stateChapters from ParserState.
Now we parse chapters as level 0 headers, and parts as level -1 headers.
After parsing, we check for the lowest header level, and if it's
less than 1 we bump everything up so that 1 is the lowest header level.
So `\part` will always produce a header; no command-line options
are needed.
|
|
Closes #1642.
|
|
|
|
|
|
|
|
This allows us to display error information returned by the
skylighting library.
Display a warning if the highlighting library throws an error.
|
|
Also added identifiers on `<div>` elements. These were commented
out before, not sure why?
|
|
The values of the following meta variables are now interpreted using
org-markup instead of treating them as pure strings:
- *keywords*: comma-separated list of inlines
- *subtitle*: inline values
- *nocite*: inline values; using it multiple times accumulates the
values.
|
|
|
|
|
|
As noted in the previous commit, an autogenerated identifier
may still coincide with an explicit identifier that is given
for a header later in the document, or with an identifier on
a div, span, link, or image. This commit adds a warning
in this case, so users can supply an explicit identifier.
* Added `DuplicateIdentifier` to LogMessage.
* Modified HTML, Org, MediaWiki readers so their custom
state type is an instance of HasLogMessages. This is necessary
for `registerHeader` to issue warnings.
See #1745.
|
|
Previously only autogenerated ids were added to the list
of header identifiers in state, so explicit ids weren't taken
into account when generating unique identifiers. Duplicated
identifiers could result.
This simple fix ensures that explicitly given identifiers are
also taken into account.
Fixes #1745.
Note some limitations, however. An autogenerated identifier
may still coincide with an explicit identifier that is given
for a header later in the document, or with an identifier on
a div, span, link, or image. Fixing this would be much more
difficult, because we need to run `registerHeader` before
we have the complete parse tree (so we can't get a complete
list of identifiers from the document by walking the tree).
However, it might be worth issuing warnings for duplicate
header identifiers; I think we can do that. It is not
common for headers to have the same text, and the issue
can always be worked around by adding explicit identifiers,
if the user is aware of it.
|