Dear Maintainer, fzf currently installs shell completion and key-bindings files into: /usr/share/doc/fzf/examples/ However these files are not documentation files, they are intended to be used by the user, by sourcing them in their shell configuration files. Therefore, the files don't belong in the doc location. For comparison, this is the location that archlinux puts those files into: usr/ usr/bin/ usr/bin/fzf usr/bin/fzf-tmux usr/share/ usr/share/fish/ usr/share/fish/vendor_functions.d/ usr/share/fish/vendor_functions.d/fzf_key_bindings.fish usr/share/fzf/ usr/share/fzf/completion.bash usr/share/fzf/completion.zsh usr/share/fzf/key-bindings.bash usr/share/fzf/key-bindings.zsh usr/share/licenses/ usr/share/licenses/fzf/ usr/share/licenses/fzf/LICENSE usr/share/man/ usr/share/man/man1/ usr/share/man/man1/fzf-tmux.1.gz usr/share/man/man1/fzf.1.gz usr/share/vim/ usr/share/vim/vimfiles/ usr/share/vim/vimfiles/doc/ usr/share/vim/vimfiles/doc/fzf.txt usr/share/vim/vimfiles/plugin/ usr/share/vim/vimfiles/plugin/fzf.vim Please consider installing the shell completion and key-bindings files into: /usr/share/fzf/ and document this location in /usr/share/doc/fzf/README.Debian I know that the bash shell completion file is now in a different location, but I am a zsh user so that doesn't affect me. Thank you.
This is a request for key-bindings and completion files to be moved from /usr/share/doc/fzf/examples to /usr/share/fzf. If we want to do this, we'll need to: 1. Announce the new path in the NEWS file for users who still "source" these files while informing them of the modern way for setting up shell integration (see README.Debian) 2. Modify the path of these files in README.Debian Merge requests to implement this are welcome at https://salsa.debian.org/go-team/packages/fzf/-/merge_requests/ !
Control: tags -1 patch thanks https://salsa.debian.org/go-team/packages/fzf/-/merge_requests/13 dated 2026-04-02, that's six weeks ago.
Control: tags -1 patch thanks https://salsa.debian.org/go-team/packages/fzf/-/merge_requests/13 dated 2026-04-02, that's six weeks ago.
The patch has been in the MR for eight weeks now. The fzf team has requested minor changes of the typ I'd want from a junior dev to educate them. They seem to be unwilling to do those minor changes themselves and instead expect me to do them. We have been through those motions already twice. What has begun to be an easy drive-by change to fix a trivial bug in a package I don't care to much about has become too much a time-eater for me. The first thing people need to learn when they have others do work for them is that those other people will produce results that are not bit-for-bit identical to what they themselves would have produced. The fzf team can now either accept the MR and sort he files yourself the way they like them in the file, or they can reject the MR and leave the bug rotting away some more years. I also don't have the privileges to remove myself as an "Assignee" from the MR in salsa. Salsa is therefore pestering me with messages that I still have "assignments" to do. This is highly demotivating me from helping with packages using the Salsa MR process, it is too much oriented towards an education or work environment and not enough towards a volunteer organizatio where people have the right to refuse being sent around. I'm done with helping here. Have a nice weekend.
The patch has been in the MR for eight weeks now. The fzf team has requested minor changes of the typ I'd want from a junior dev to educate them. They seem to be unwilling to do those minor changes themselves and instead expect me to do them. We have been through those motions already twice. What has begun to be an easy drive-by change to fix a trivial bug in a package I don't care to much about has become too much a time-eater for me. The first thing people need to learn when they have others do work for them is that those other people will produce results that are not bit-for-bit identical to what they themselves would have produced. The fzf team can now either accept the MR and sort he files yourself the way they like them in the file, or they can reject the MR and leave the bug rotting away some more years. I also don't have the privileges to remove myself as an "Assignee" from the MR in salsa. Salsa is therefore pestering me with messages that I still have "assignments" to do. This is highly demotivating me from helping with packages using the Salsa MR process, it is too much oriented towards an education or work environment and not enough towards a volunteer organizatio where people have the right to refuse being sent around. I'm done with helping here. Have a nice weekend.
An attempt to sort this out was done in https://salsa.debian.org/go-team/packages/fzf/-/merge_requests/13 but there are still some questions on how to get the details right. This issue is available for anyone to take a stab at if you have a clear solution for it.
As the MR was closed without result over things that would have cost the package maintainer like five minutes, everything that remains is an unresolved bug report, hours of wasted time and one more demotivated contributor. Well done, everybody. Greetings Marc
As the MR was closed without result over things that would have cost the package maintainer like five minutes, everything that remains is an unresolved bug report, hours of wasted time and one more demotivated contributor. Well done, everybody. Greetings Marc