Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Persist the necessary configuration for navi interactive cheat sheet. #4647

Open
3 tasks done
langshangyuan opened this issue Apr 10, 2023 · 2 comments
Open
3 tasks done
Labels
bug Something isn't working

Comments

@langshangyuan
Copy link
Contributor

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues/PRs to ensure it has not already been reported or fixed.
  • I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

navi

Expected/Current Behaviour

Currently, if you don't manually config the navi using %USERPROFILE%/AppData/Roaming/navi/config.yaml to set the shell to pwsh or cmd something else. The navi will show the error /bin/bash command not found.

Steps to Reproduce

scoop install navi


`navi fn welcome` → `/bin/bash` command not found.

Possible Solution

  1. I think we can persist the configuration of navi.
  2. Make a symbol link to the original configuration file location %USERPROFILE/AppData/Roaming/navi/config.yaml.

Scoop and Buckets Version

Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
759a54d71 (HEAD -> master, origin/master, origin/HEAD) dbeaver: Update to version 23.0.2

'java' bucket:
f27532e3 (HEAD -> master, origin/master, origin/HEAD) temurin8-nightly-jre: Update to version 8.0.372-6.0.202304071827

'main' bucket:
74570c859 (HEAD -> master, origin/master, origin/HEAD) oh-my-posh: Update to version 14.29.1

'nerd-fonts' bucket:
d7b401e (HEAD -> master, origin/master, origin/HEAD) SarasaGothic: Update to version 0.40.5

'versions' bucket:
a897289bf (HEAD -> master, origin/master, origin/HEAD) zig-dev: Update to version 0.11.0-dev.2470

Scoop Config

last_update          aria2-warning-enabled scoop_repo                              scoop_branch
-----------          --------------------- ----------                              ------------
4/10/2023 6:29:01 AM                 False https://github.com/ScoopInstaller/Scoop master

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.3.3
PSEdition                      Core
GitCommitId                    7.3.3
OS                             Microsoft Windows 10.0.25336
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Additional Softwares

No response

@HUMORCE
Copy link
Member

HUMORCE commented Aug 2, 2023

In current situation to manages its config, we need to operates files that out of Scoop Dir, and its content of config file(value of shell.command). I don't even know which shell(cmd|pwsh|powershell) should be specify by default.

@alexis-opolka
Copy link

alexis-opolka commented Feb 5, 2025

@HUMORCE @langshangyuan I'm following up from denisidoro/navi#40.

Navi, as of its latest version, 2.24.0, supports setting the config path using the NAVI_CONFIG environment variable, may this solve your issue? (For more details, see: https://github.com/denisidoro/navi/blob/master/docs/navi_config.md#config-file-path)

On the matter of specifying the default shell on windows 10/11, I think it would be best to specify powershell since this refers to PowerShell version 5.X which is the version of the default powershell shipped with windows.
This is also the shell launched by default when using the new windows terminal app, if I'm not mistaken.

If the current way of specifying the config path does not help you, may I know how you would need navi to work in order to solve this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants