![]() ![]() Load the standard library by adding use std in your env.nu, reload, then assuming nupass. which will reload the latest you have saved.įrom nu version 0.79.1, you can use the standard library, and use its bench command to do a benchmark. ![]() If you're making changes to the script while testing, you can just re-source the script by doing: Reload nu, then run it to test: nupass -h (you can specify the path as use /path/to/nupass.nu if you're not taking advantage of $env.NU_LIB_DIRS) I haven't tried fzf, but I think it would be possible to interop with it (or something like it) in the future. That said, 'zsh' may have some structured data capabilities I don't know about. Reedline is a project to create a line editor (like bashs readline or zshs zle ) that supports many of the modern conveniences of CLIs, including syntax. Accept a basic breaking change that introduces this field. Load the script with use in your config.nu, something like: The general rule of thumb is that nu works with data in a more structured way, where most shells generally work with strings. Open sholderbach opened this issue 2 weeks ago 10 comments May be fixed by 47 Collaborator sholderbach commented edited Embrace this breaking change and assume that Style shouldn't be built directly (and maybe hide all fields).threads (-t): int = 16 # Number of threads to use in par-each delimiter (-m): string = "-" # Delimiter for diceware symbols (-s): string = # Symbols to use in password ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |