summarylogtreecommitdiffstats
path: root/fish-fzf.changelog
blob: 5bb87adfe496761cc9b80da82f00add6c91736c0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
2023-11-06	fish-fzf 10.3

* Remove redundant word "Search" from prompts
* Stop warning about removed config vars on update
* Add support for FZF_DEFAULT_OPTS_FILE


2023-11-06	fish-fzf 10.2

Important patch

  I accidentally broke Search History preview in v10.1. This release fixes it.


2023-11-05	fish-fzf 10.1

Breaking change

  Search Directory's and Search Variable's custom fzf opts variables (used to
  pass fzf options to specific commands) were renamed in v9.5. Now the old,
  deprecated names have been completely removed (615ce65):

  * Search Directory: if you use fzf_dir_opts, switch to fzf_directory_opts
  * Search Variables: if you use fzf_shell_vars_opts, switch to fzf_variables_opts

Search History

  Slightly improve performance, add test and comments (82dd51e).


2023-08-22	fish-fzf 10.0

[git log][git status] Integrate preview with diff highlighters

  If fzf_diff_highlighter is set, fzf.fish will pipe git diff-like output
  through its value. This enables integration with delta, diff-so-fancy,
  diff-highlighter, or https://github.com/walles/riff

[history][git log] Use fzf history scoring scheme

  The history scoring scheme is much better suited for ranking input in which
  chronological order is important. The previous scheme was commonly causing
  commands and commits from months ago to overtake those more recent. This
  issue is now mostly alleviated.


2023-08-21	fish-fzf 9.10

[git log][git status] Integrate preview with diff highlighters

  If fzf_diff_highlighter is set, fzf.fish will pipe git diff-like output
  through its value. This enables integration with delta, diff-so-fancy,
  diff-highlighter, or https://github.com/walles/riff

[history][git log] Use fzf history scoring scheme

  The history scoring scheme is much better suited for ranking input in which
  chronological order is important. The previous scheme was commonly causing
  commands and commits from months ago to overtake those more recent. This
  issue is now mostly alleviated.