Skip to content

3.0.0
Compare
Choose a tag to compare
@darrenldl darrenldl released this 12 Mar 11:00
· 742 commits to main since this release
3.0.0
938fa6e

For packagers: Docfd now needs pandoc at run time for support of .epub, .odt, .docx, .fb2, .ipynb, .html, and .htm files

  • Fixed crash from search result snippet being bigger the content view pane

    • Crash was from Content_and_search_result_render.color_word_image_grid

  • Added key bindings

    • p: exit and print search result to stderr
    • Shift+P: exit and print file path to stderr

  • Changed --debug-log - to use stderr instead of stdout

  • Added non-interactive search mode where search results are printed to stdout

    • --search EXP invokes non-interactive search mode with search expression EXP
    • --search-result-count-per-document sets the number of top search results printed per document
    • --search-result-print-text-width sets the text width to use when printing

  • Added --start-with-search to prefill the search field in interactive mode

  • Removed content requirement expression from multi-file view

    • Originally designed for file filtering, but I have almost never used
      it since its addition in 1.0.0

  • Added word based line wrapping to following components of document list in multi-file view

    • Document title
    • Document path
    • Document content preview

  • Added word breaking in word based line wrapping logic so all of the original characters
    are displayed even when the terminal width is very small or when a word/token is very long

  • Added --paths-from to specify a file containing list of paths to (also) be scanned

  • Fixed search result centering in presence of line wrapping

  • Renamed --max-fuzzy-edit to --max-fuzzy-edit-dist for consistency

  • Changed error messages to not be capitalized to follow Rust's and Go's
    guidelines on error messages

  • Added fallback rendering text so Docfd does not crash from trying
    to render invalid text.

  • Added pandoc integration

  • Changed the logic of determining when to use stdin as document source

    • Now if any paths are specified, stdin is ignored
    • This change mostly came from Dune's cram test mechanism
      not providing a tty to stdin, so previously Docfd would keep
      trying to source from stdin even when explicit paths are provided
Assets 4
Loading