phiresky / ripgrep-all

rga: ripgrep, but also search in PDFs, E-Books, Office documents, zip, tar.gz, etc.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

rga-preproc fails when calling pandoc on .docx files (but probably other file types that require pandoc too)

gbstan opened this issue · comments

It seems that calls to rga-preproc is incompatible with the current version of pandoc.

When calling rga on a folder containing .docx files, this is the typical error that occurs for .docx files:

... preprocessor command failed: '"/usr/local/bin/rga-preproc ...:
--atx-header adapter: pandoc
Unknown option --atx-headers.
Try pandoc --help for more information.
Error: subprocess failed: ExitStatus(unix_wait_status(1536))

On some .docx files the error code is different:

adapter: pandoc
Unknown option --atx-headers.
Try pandoc --help for more information.
Error: Broken pipe (os error 32)

Here are the version numbers:
ripgrep-all 0.9.6

pandoc 3.0.1
Features: +server +lua
Scripting engine: Lua 5.4

Looks like they made a fix back in 2021; however, they have not released a new stable version since 2020. You'll probably need to compile from source.

commented

pandoc 3.0 has removed deprecated --atx-headers option, use version before 3.0 instead.

commented

Duplicate of #115.

And yep, fixed in 020000c like @keiichiiownsu12 mentioned.

Any chance a new version of ripgrep-all could be released that fixes this issue? I don't know how to compile from source and ripgrep-all is one of the tools I use regularly.

This has broken an important workflow at work :( Compiling from source did not help. cargo install --locked ripgrep_all installs v0.9.6. Is it possible to install a newer version from source?

Could a new stable version be released? From the comments above it seems a version that fixes exists but hasn't been made available.

Could a new stable version be released? From the comments above it seems a version that fixes exists but hasn't been made available.

@phiresky Could you please release a new version with the fix?

This is fixed in 1.0.0-alpha.4