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

docs(nu): Simplify Nushell integration instructions #5845

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

texastoland
Copy link
Contributor

@texastoland texastoland commented Mar 17, 2024

Implements @davidkna's astute feedback in #5844. Always runs unless non-interactive (a script). Clarifies and simplifies installation while reducing (possibly concurrent) file writes. RFC @amtoine (previous committer) @fdncred.

Motivated by jdx/mise-docs#46 for consistency between tools.
@texastoland texastoland force-pushed the nushell_simplify branch 3 times, most recently from ade338e to bdfec33 Compare March 17, 2024 18:01
texastoland added a commit to texastoland/mise-docs that referenced this pull request Mar 17, 2024
@texastoland texastoland force-pushed the nushell_simplify branch 2 times, most recently from 90ebebb to 8bcb200 Compare March 17, 2024 21:31
Reinitializes the script at most once every day. This is necessary because doing so every
time could lead to thousands of concurrent writes calling `| par-each { nu -c }`.
texastoland added a commit to texastoland/mise-docs that referenced this pull request Mar 17, 2024
@texastoland texastoland changed the title Simplify Nushell integration Simplify Nushell integration (based on feedback) Mar 17, 2024
@andytom andytom changed the title Simplify Nushell integration (based on feedback) docs(nu): Simplify Nushell integration instructions Mar 21, 2024
jdx pushed a commit to jdx/mise-docs that referenced this pull request Mar 22, 2024
* Update Nushell integration

Depends on jdx/mise#1763 in release.

* Automate reinstallation

Manually picked from starship/starship#5845.
Copy link
Contributor

@amtoine amtoine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if i may review this PR 😊

i think i find the

'
...
' | save $nu.env-path --append

quite harder to read 😕

README.md Outdated Show resolved Hide resolved
@texastoland
Copy link
Contributor Author

texastoland commented Mar 23, 2024

quite harder to read 😕

Because it follows a convention of providing a command to run instead of code to add 🤓 Here's a deployed example.

The currrent instructions presume the user is already familiar with the configuration docs. Starting Nu they can (I did months ago) run into issues like the files being located in an unexpected place on Mac or not having an editor configured for config env and config nu (or not even knowing the commands).

Starship in particular was the first thing I tried to integrate. This "just works" while providing enough context for expert users to customize as we please!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants