diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2016-11-21 15:32:27 +0100 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2016-11-21 15:32:27 +0100 |
| commit | ac6dfe0b4efb601f24e444ac8a4059c4103881ef (patch) | |
| tree | 6eb0a12af38f845bb85acaf7793276544ec53e71 /tests/docx/dummy_item_after_list_item.native | |
| parent | 8d7ecc27a19facf6c4b50a65ee1029c105aacdb2 (diff) | |
| download | pandoc-ac6dfe0b4efb601f24e444ac8a4059c4103881ef.tar.gz | |
Changed resolution of filter paths.
- We now first treat the argument of `--filter` as a full (absolute
or relative) path, looking for a program there. If it's found,
we run it.
- If not, and if it is a simple program name or a relative path,
we try resolving it relative to `$DATADIR/filters`.
- If this fails, then we treat it as a program name and look in
the user's PATH.
Previously if you did `--filter foo` and you had `foo` in your
path and also an executable `foo` in your working directory,
the one in the path would be used. Now the one in the working
directory is used.
In addition, when you do `--filter foo/bar.hs`, pandoc will now
find a filter `$DATADIR/filters/foo/bar.hs` -- assuming there
isn't a `foo/bar.hs` relative to the working directory.
@jkr note the slight revision of what we had before.
This was motivated by the idea that one might clone filter
repositories into the filters subdirectory; it is nice to
be able to run them as `reponame/filtername`.
Diffstat (limited to 'tests/docx/dummy_item_after_list_item.native')
0 files changed, 0 insertions, 0 deletions