Age | Commit message (Collapse) | Author | Files | Lines |
|
Previously comments sometimes got extended too far. Closes #7134.
|
|
|
|
Adjust line wrapping if default wrapping would cause a line to be read
as an ordered list item.
Fixes #7132
|
|
Code blocks that are not marked as a language supported by Jira are
rendered as preformatted text with `{noformat}` blocks.
Fixes: tarleb/jira-wiki-markup#4
|
|
Closes #7129.
|
|
Closes #7127.
|
|
Previously, if `--resource-path` were used multiple times, the last
resource path would replace the others.
With this change, each time `--resource-path` is used, it prepends
the specified path components to the existing resource path.
Similarly, when `resource-path` is specified in a defaults file,
the paths provided will be prepended to the existing resource
path.
This change also allows one to avoid using the OS-specific path
separator; instead, one can simply use `--resource-path`
a number of times with single paths. This form of command
will not have an OS-dependent behavior.
This change facilitates the use of multiple, small defaults
files: each can specify a directory containing its own
resources without clobbering the resource paths set by
the others.
Closes #6152.
|
|
to refer to the directory where the default file is.
This will make it possible to create moveable
"packages" of resources in a directory.
Closes #5871.
|
|
This allows the syntax `${HOME}` to be used, in fields that expect
file paths only. Any environment variable may be interpolated
in this way. A warning will be raised for undefined variables.
The special variable `USERDATA` is automatically set to the
user data directory in force when the defaults file is parsed.
(Note: it may be different from the eventual user data directory,
if the defaults file or further command line options change that.)
Closes #5982.
Closes #5977.
Closes #6108 (path not taken).
|
|
* Add `optCSL`, `optBibliography`, `optCitationAbbreviations` to
`Opt` [API change].
* Move `addMeta` from T.P.App.Opt to T.P.App.CommandLineOptions.
|
|
[API change]
|
|
Rationale: the manual says that the XDG data directory will
be used if it exists, otherwise the legacy data directory.
So we should just determine this and use this directory,
rather than having a search path which could cause some
things to be taken from one data directory and others from
others.
[API change]
|
|
This reverts commit 916ce4d51121e0529b938fda71f37e947882abe5.
I was confused in thinking it wouldn't work.
|
|
This reverts commit e461b7dd45f717f3317216c7d3207a1d24bf1c85.
Ill-advised change. This doesn't work because we parse
strings in chunks.
|
|
Partially addresses #7124.
|
|
This reverts commit b569b0226d4bd5e0699077089d54fb03d4394b7d.
Memory usage improvement in compilation wasn't very significant.
|
|
|
|
Incorporate accentCommands into T.P.Readers.LaTeX.Inline.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
with T.P.Writers.Markdown.Types and T.P.Writers.Markdown.Inline.
The module was difficult to compile on low-memory system.s
|
|
[API change]
This is really an implementation detail that shouldn't be
exposed in the public API.
|
|
|
|
Closes: tarleb/jira-wiki-markup#3.
|
|
|
|
instead of individual commands.
|
|
[API change]
These were only exported for testing, which seems the
wrong thing to do. They don't belong in the public
API and are not really usable as they are, without access
to the Tok type which is not exported.
Removed the tokenize/untokenize roundtrip test.
We put a quickcheck property in the comments which
may be used when this code is touched (if it is).
|
|
|
|
|
|
|
|
Benchmarks show that these make the reader 13-17% faster,
depending on extensions.
|
|
|
|
In conjunction with other changes this makes the reader
almost twice as fast on our benchmark as it was on Feb. 10.
|
|
|
|
These are handled anyway by regularSymbol.
|
|
|
|
|
|
To help reduce memory demands compiling the main LaTeX reader.
|
|
Fixes: #6674
|
|
|
|
Previously we didn't allow unescaped quotes in unquoted values,
but they are allowed. Closes #7112.
|
|
...when handling URL argument served with no charset in the mime type.
The assumption is that most pages that don't specify a charset
in the mime type are either UTF-8 or latin1. I think that's a good
assumption, though I'm not sure.
|
|
the character encoding. We can properly handle UTF-8 and
latin1 (ISO-8859-1); for others we raise an error.
See #5600.
|
|
...for PandocError. [API change]
|
|
[API change]
|
|
[API change] This affects `readFile`, `getContents`, `writeFileWith`,
`writeFile`, `putStrWith`, `putStr`, `putStrLnWith`, `putStrLn`.
`hPutStrWith`, `hPutStr`, `hPutStrLnWith`, `hPutStrLn`, `hGetContents`.
This avoids the need to uselessly create a linked list of characters
when emiting output.
|