nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.98k stars 1.8k forks source link

bug: zoxide: no completions #3792

Open asymmetric opened 1 year ago

asymmetric commented 1 year ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

I have this in my config:

    zoxide = {
      enable = true;
      enableFishIntegration = true;
    };

And z works fine, but there are no tab-completions, even though:

❯ complete z
complete --no-files z -a '(__zoxide_z_complete)'

And if I call __zoxide_z_complete manually, I do get a list of candidates -- it's just not hooked to TAB.

Maintainer CC

@marsam

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.18, NixOS, 23.05 (Stoat), 23.05.20230312.5a1dc8a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"nixos-21.11.335130.386234e2a61"`
 - channels(asymmetric): `""`
 - nixpkgs: `/nix/store/w0x3a7c60df8dlwnnxn8s3bg63cjpxpa-nbp8axqsz7zbkd03zia0v60jhi382ly9-source`
ncfavier commented 1 year ago

If the completions are installed fine this sounds like an issue with zoxide rather than home-manager?

danielpza commented 1 year ago

EDIT: nvm it seems my issue is due to misconfiguration

I have the same issue, my config:

  programs.zoxide = { enable = true; };

Running z gives me z: command not found

However if I manually run zoxide init it works:

$ eval "$(zoxide init bash)
$ z #  zoxide now works
stale[bot] commented 1 year ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

pbek commented 6 months ago

@r-vdp, I wonder, do you have completion for z (or whatever alias you are using)?

r-vdp commented 6 months ago

Not sure, z autocompletes with the directories in the current directory, not with the entries I get with zi. But I'm not so sure what's the expected behaviour. I mostly use zi to fuzzy search and z only to change up and down in the directory tree.

pbek commented 5 months ago

Thank you.

Not sure, z autocompletes with the directories in the current directory, not with the entries I get with zi. But I'm not so sure what's the expected behaviour.

It's the same for me... Would be great to be able tu auto-coplete the partial matches...

stale[bot] commented 2 months ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.