All Versions
15
Latest Version
Avg Release Cycle
97 days
Latest Release
977 days ago

Changelog History
Page 1

  • v0.5.8 Changes

    July 18, 2020 
    v0.5.8 - 18 Jul 2020
  Features:
  * Add support for 256-colors in the configuration. You must first enable
    this in the config file by specifying "Use256Colors": true

  • v0.5.7 Changes

    January 10, 2020 
    v0.5.7 - 10 Jan 2020
  Bugs/Fixes:
  * Code introduced in v0.5.5 in turn caused a bug where if the input is coming
    from standard input and is possibly infinite, the user would see the
    query being "stuck" after the first character is entered.
    If peco was applied on a finite set of data, this did not manifest itself.
    (#494 fixed by #495)

  • v0.5.6 Changes

    January 07, 2020 
    v0.5.6 - 07 Jan 2020
  Miscellaneous:
  * I completely messed up the release process. Retagging and uploading
    binaries properly. No code changes except for the version number (#493)

  • v0.5.5 Changes

    January 01, 2020 
    v0.5.5 - 02 Jan 2020
  Features:
  * Properly exit out of peco if --select-1 and --query are both specified,
    and the query produces exactly one result (#490)

  • v0.5.4 Changes

    December 19, 2019 
    v0.5.4 - 19 Dec 2019
  Miscellaneous:
  * Properly set cursor position (#450)
  * Update termbox-go version (#487/#488)
  * Update go version to go 1.13

  • v0.5.3 Changes

    March 11, 2018 
    v0.5.3 - 12 Mar 2018
  Features:
  * New --print-query option prints out the query upon successful exit
  * New actions ScrollFirstItem and ScrollLastItem
  Miscellaneous:
  * Update termbox-go version (#447)
  * Documentation fixes (#444)
  * Build peco using go1.10

  • v0.5.2 Changes

    December 08, 2017 
    v0.5.2 - 08 Dec 2017
  Backwards Incompatible Change:
  * --version flag now prints out the Go version used to build the binary
  Micellaneous:
  * Various doc fixes
  * Build peco using go1.9.2.
  * There have apparently been problems running the stock peco binary in
    MacOS High Sierra, with an error message like "failed MSpanList_Insert...",
    which can averted by compiling the binary with a newer Go.

    Reports suggest that peco v0.5.1 is not affected by this problem, but
    we're making this release anyway just to make sure that we're building
    on a new-ish Go, and that users have a way to see what Go version was
    used to build their binaries

  • v0.5.1 Changes

    March 17, 2017 
    v0.5.1 - 17 Mar 2017
  Bugs/Fixes
  * When --exec is used, and you come back from the external command,
    you lost your selected location in the peco view. #410
  Backwards Incompatible Change:
  * --tty has been removed. it was not being used anyways.
  Miscellaneous
  * When scrolling right, you could potentially keep on scrolling
    infinitely. This has bee addressed by #409, #412
  * External commands specified in --exec now receive
    PECO_FILENAME, PECO_LINE_COUNT, PECO_QUERY, and
    PECO_MACHED_LINE_COUNT as environment variables
  * Removed unused structs
  * Fixed glide related Mkaefile actions

  • v0.5.0 Changes

    March 05, 2017 
    v0.5.0 - 06 Mar 2017
  Backwards Incompatible Change:
  * ExecuteCommand has been removed.
  Features:
  * A new command line option `--exec` has been added. This allows you to
    execute external commands via shell, and should be used as replacement
    to `ExecuteCommand`
  * A new configuration option `MaxScanBufferSize` has been added. Whereas
    bufio.Scanner (which peco internally relies on) only accepts lines that
    are < 64kb when reading the input, specifying this option in the config
    allows you to change this limit.
    The default MaxScanBuferSize is 256kb.
  Bugs/Fixes
  * When executing external commands, the screen and the capturing of user
    input would interfere when getting back to peco.

  • v0.4.9 Changes

    March 01, 2017 
    v0.4.9 - 01 Mar 2017
  Bugs/Fixes
  * SavedSelection under `--selection-prefix` was not properly working
    (#388)
  * An outstanding bug from v0.4.0 where specifying `--query` for a large
    enough input would lose results in the first query execution has been
    fixed (#389)