Commit Graph

18 Commits (20230117636c9dfa3ed6f6428c5bc4c51b02f60a)

Author SHA1 Message Date
Junegunn Choi 2023011763
0.36.0 1 year ago
Junegunn Choi d01ae55109
0.35.0 2 years ago
Junegunn Choi 04d0b0223f
0.34.0 2 years ago
Junegunn Choi e03ac3136e
0.33.0 2 years ago
Junegunn Choi f7e7259910
0.32.0 2 years ago
Junegunn Choi ecc418ba77
0.31.0 2 years ago
Junegunn Choi 2093667548
0.30.0 2 years ago
Junegunn Choi dc975e8974
0.29.0 2 years ago
Junegunn Choi e4c3ecc57e
0.28.0 3 years ago
Junegunn Choi 19759ed36e
0.27.0 3 years ago
Junegunn Choi 34fe5ab143
0.26.0 3 years ago
calvin ardi bf447d7703
Update default number version (#2307) 3 years ago
Junegunn Choi b5e0e29ec6
Assign default number version (without patch version)
So that you can still build and use fzf even when the precise version
number is not injected via -ldflags.
4 years ago
Junegunn Choi 3304f284a5
Panic when fzf was built without version information
So that the package maintainers would immediately know that the build is
incorrect. But is there a way to make build simply fail?

Related: https://github.com/junegunn/fzf.vim/issues/1150
4 years ago
Junegunn Choi 552414978e
0.24.0-rc1 4 years ago
Aaron Bieber a1bcdc225e Add pledge(2) support (OpenBSD only) via a 'protector' package. (#1297) 4 years ago
Junegunn Choi 83e9af6601
Add git revision to --version output 7 years ago
Junegunn Choi 8bbf9335e1
Restructuring: main package in project root 7 years ago