nushell-show youtube.com/@nushell-prophet
Random videos about Nushell and materials related to them. All of the videos and materials are available for free reuse anywhere, including in other videos. Let's popularize Nushell!
We can use the VS Code diff function to conveniently find new and outdated lines of settings in Nushell.
To do so, we can use the following commands:
config nu --default | code --diff - $nu.config-path
config env --default | code --diff - $env.config-path
The next step after opening files should be cmd + shift + P and then >Compare: swap left and Right Editor Side
# Change directory to the path stored in the environment variable 'nu.data-dir'
> cd $nu.data-dir
# Initialize a new Git repository in the current directory
> git init
# Stage the files 'config.nu', 'env.nu', and 'history.txt' for commit
> git add config.nu env.nu history.txt
# Commit the staged files with the message 'initial commit'
> git commit -m 'initial commit'
# open config.nu file in the default editor
> config nu
# Show the status of the repository (which files are staged, modified, or untracked)
> git status
# Stage the file 'config.nu' for commit (potentially after making changes to it)
> git add config.nu
# Commit the staged file with the message 'update'
> git commit -m 'update'
On macOS, the default location for Nushell configurations is ~/Library/Application Support/nushell. The issue with this path is that it contains a space, which can lead to problems and inconveniences later.
In Linux, the XDG_CONFIG_HOME environment variable is part of the XDG Base Directory Specification, which defines standard locations for various types of configuration files. However, on macOS, the XDG_CONFIG_HOME variable is not set by default, as macOS uses its own conventions for handling configuration files.
In this video, we will manually set the XDG_CONFIG_HOME environment variable so that Nushell and other applications can use it to locate configuration files. The Nushell Book has some details on setting XDG_CONFIG_HOME too.
# Start Nushell without using history so it won't interact with the data folder during our operations
# To avoid problems, do not launch or use another instance of Nushell during this session
> nu --no-history
# See that the current path contains space and might cause inconvenience and even problems
> $nu.default-config-dir
# Let's fix it
# Ensure that you have a `.config` directory in your home directory
> mkdir ~/.config
# Move Nushell's config files and history to the appropriate folder
> mv $nu.default-config-dir ~/.config
# Verify that the files have been moved correctly
> ls ~/.config/nushell
# Create a symlink from the new config location to the default location
> ln -s ~/.config/nushell $nu.default-config-dir
# Check that the symlink was created successfully
> ls $nu.default-config-dir
# Add the XDG_CONFIG_HOME variable to your .zshrc file
> (char nl) + 'export XDG_CONFIG_HOME="$HOME/.config"' + (char nl) | save --append ~/.zshrc
# Verify the current config path
> $nu.default-config-dir
# Log out, log back in, and verify the config path again
> $nu.default-config-dir
A Nushell module to analyze the command frequencies in Nushell history, generate cool graphs, benchmark statistics with other users, and generate a file with statistics to share with the community.
https://github.com/nushell-prophet/nu-history-tools
# analyze your current commands history
> nu-history-tools analyze-history
# interactively select users to use for benchmarks in the analysis
> nu-history-tools analyze-history --pick_users
# parse submitted stats from a folder and aggregates them for benchmarking
> nu-history-tools aggregate-submissions
# parse .nu scripts
> glob **/*.nu --exclude ['**/themes/**/' '**/before_v0.60/**' '**/custom-completions/**'] | nu-history-tools analyze-nu-files
# list the history of Nushell commands with information about their crates and the Nushell versions (git tags) when they appeared.
> nu-history-tools list-all-commands