Up to [cvs.NetBSD.org] / pkgsrc / shells / nushell
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
shells/nushell: update to 0.117.0 This is the 0.117.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-11-09-nushell_v0_117_0.html
shells/nushell: update to 0.116.1 Today, we're releasing version 0.116.1 of Nu. This patch release improves TUI widgets with live stream updates, customizable borders and titles, and more reliable pane resizing, while fixing completions and refining startup-time reporting.
shells/nushell: update to 0.116.0 This is the 0.116.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-09-26-nushell_v0_116_0.html
nushell: updated to 0.115.1 0.115.1 This patch release improves completions, adds Helix keybinding support, and fixes issues with semver comparisons, $ans, SQLite table updates, and keybinding merging.
shells/nushell: update to 0.115.0 This is the 0.115.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-08-15-nushell_v0_115_0.html
nushell: updated to 0.114.1 0.114.1 This patch release fixes issues found after enforce-runtime-annotations became opt-out in the last version, improving runtime type checks and error reporting.
nushell: updated to 0.114.0 0.114.0 This release brings sharper type checking, POSIX-style -- option parsing, the new run command for pipeline-friendly scripts, and nice built-in support for working with Semantic Versioning.
nushell: updated to 0.113.1 0.113.1 This patch release fixes issues introduced in 0.113.0, including YAML string quoting behavior, reliability problems across the idx command family, and a REPL regression in commandline edit.
shells/nushell: revert back to vendor libgit2 Avoid mismatch versions issue.
nushell: updated to 0.113.0 0.113.0 This release adds fast in-memory indexing and search via idx, stream inspection without collection via peek, structured verbose output for file operations, and a more concise default output mode for from md.
nushell: updated to 0.112.2 0.112.2 Fixed regressions in quoting for string arguments in Nu script calls Fixed regressions for input list
shells/nushell: update to 0.112.1 This is the 0.112.1 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-04-11-nushell_v0_112_1.html (We skipped release 0.112.0 due to issue when releasing to crates.io.)
shells/nushell: uodate to 0.111.0 This is the 0.111.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-02-28-nushell_v0_111_0.html
shells/nushell: update to 0.110.0 This is the 0.110.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2026-01-17-nushell_v0_110_0.html
nushell: updated to 0.109.1 0.109.1 This release fixes some regressions of Nu 0.109.0, especially fixes to http get and source.
shells/nushell: update to 0.109.0 This is the 0.109.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-11-29-nushell_v0_109_0.html
shells/nushell: update to 0.108.0 This is the 0.108.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-10-15-nushell_v0_108_0.html
nushell: updated to 0.107.0 Nushell 0.107.0 Today, we're releasing version 0.107.0 of Nu. This release has a pretty big variety of improvements to various parts of Nushell. There are some new features for watch, find, and query xml, and changes to over 50 commands!
shells/nushell: update to 0.106.1 This patch release fixes a regression with bare string interpolation from 0.106.0, the const version of get, and several build-related issues.
shells/nushell: update to 0.106.0 This is the 0.106.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-07-23-nushell_0_106_0.html
shells/nushell: update to 0.105.1 0.105.1 This release adds a fix to make cargo install nu possible again. 0.105.0 This is the 0.105.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-06-10-nushell_0_105_0.html
nushell: updated to 0.104.1 0.104.1 This release fixes some issues related to the Windows MSI installer and the Nushell winget package. macOS and Linux users are not affected.
shells/nushell: update to 0.104.0 This is the 0.104.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-04-29-nushell_0_104_0.html
shells/nushell: doesn't need sse2
shells/nushell: not for i386
shells/nushell: update to 0.103.0 This is the 0.103.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-03-18-nushell_0_103_0.html
nushell: try bumping ARGMAX_REQD even higher since this still fails on shadow
nushell: try bumping ARGMAX_REQ to fix build
shells/nushell: update to 0.102.0 This is the 0.102.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2025-02-04-nushell_0_102_0.html
shells/nushell: update to 0.101.0 This is the 0.101.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes: https://www.nushell.sh/blog/2024-12-24-nushell_0_101_0.html
shells/nushell: update to 0.100.0 This is the 0.100.0 release of Nushell. The ChangeLog is too long to reproduce here, see release notes.
shells/nushell: update to 0.99.1 A bug was introduced in 0.99.0 where return, break, and continue could cause $env.LAST_EXIT_CODE to be set to 1. This has been fixed in #14120.
shells/nushell: update to 0.99.0 This is the 0.99.0 release of Nushell. ChangeLogs are too long to reproduce here, see: https://www.nushell.sh/blog/2024-10-15-nushell_0_99_0.html
shells/nushell: fix curl-sys crate version
shells/nushell: update to 0.98.0 ChangeLogs are too long to reproduce here. See: https://www.nushell.sh/blog/2024-09-17-nushell_0_98_0.html https://www.nushell.sh/blog/2024-08-20-nushell_0_97_1.html
shells/nushell: update to 0.96.1 See https://www.nushell.sh/blog/2024-07-29-nushell_0_96_1.html for ChangeLog.
shells/nushell: update to 0.96.0 This is the 0.96.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-07-23-nushell_0_96_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.95.0 This is the 0.95.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-06-25-nushell_0_95_0.md The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.94.2 In this release, we're releasing two bugfixes: - Fix external command name parsing with backslashes, and add tests by @devyn in #13027 - Fix run_external::expand_glob() to return paths that are PWD-relative but reflect the original intent by @devyn in #13028 This release was made possible by PR contributions from @devyn.
shells/nushell: update to 0.94.1 This is a patch release to fix issues introduced by 0.94.0, including path expansion for external commands, path type changes, shell integration, and more.
shells/nushell: update to 0.94.0 This is the 0.94.0 release of Nushell. You can learn more about this release here: http://www.nushell.sh/blog/2024-05-28-nushell_0_94_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.93.0 This is the 0.93.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-04-30-nushell_0_93_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.92.2 This is the 0.92.2 patch release of Nushell. This hot-fix addresses a security concern with how arguments are passed to external commands on Windows. The underlying vulnerability was found in the interaction of the Rust standard library we use and the Windows command invocation logic and documented as CVE-2024-24576 To address this concern, we update the version of the Rust compiler and standard library used to build Nushell to the latest stable version (1.77.2). Note: Distributors of Nushell need to upgrade their Rust toolchain to provide a patched Nushell build. pkgsrc note: As CVE-2024-24576 only affects Windows, we are patching away the requirement for MSRV 1.72.2 back to 1.75.0
shells/nushell: add update warning
shells/nushell: update to 0.92.1 This is the 0.92.1 patch release of Nushell. This patch addresses several bugs and regressions present with 0.92.0: - The configured hooks should again properly affect the scope (e.g. virtualenv integrations using a hook to activate as an overlay) (#12383) - mkdir/touch did not correctly resolve relative paths after using cd. This is now fixed. (#12394) - The default config file created by 0.92.0 assumed that you built with the default feature set including the system-clipboard. This is not working on platforms like Android/Termux (termux builds with default-no-clipboard). Now we only create keybindings in config.nu that are supported on all platforms and provide suggestions as comments. You may want to recreate config.nu with 0.92.1 if you run into this issue. (#12385) - The timing of drop notifications sent to plugins has been corrected. (#12341)
shells/nushell: update to 0.92.0 This is the 0.92.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-04-02-nushell_0_92_0.html The ChangeLog is too long to reproduce here.
shells/nushell: Add use of mk/atomic64.mk to make this build on macppc.
shells/nushell: update to 0.91.0 This is the 0.91.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-03-05-nushell_0_91_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.90.1 This is the 0.90.1 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-02-06-nushell_0_90_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.89.0 This is the 0.89.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2024-01-09-nushell_0_89_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.88.1 v0.88.1 This is the 0.88.1 patch release of Nushell. With this hotfix we adress a regression in the redirection to external commands and fix build failures using cargo install and on some platforms. v0.88.0 This is the 0.88.0 release of Nushell. You can learn more about this release here: https://www.nushell.sh/blog/2023-12-12-nushell_0_88_0.html The ChangeLog is too long to reproduce here.
shells/nushell: update to 0.87.1 This is the 0.87.1 patch release of Nushell. In this hotfix we resolve two issues with the file system commands rm and cp. Nushell's cp command in 0.87.0 did not correctly handle changes to the directory by the Nushell internal cd when invoked inside a block. Furthermore the rm command was not able to correctly handle paths requiring expansion.
shells/nushell: update to 0.87.0 Learn more about this release and changes at: https://www.nushell.sh/blog/2023-11-14-nushell_0_87_0.html The ChangeLog is too long to reproduce here.
*: bump for openssl 3
shells/nushell: update to 0.86.0 Learn more about this release and changes at https://www.nushell.sh/blog/2023-10-17-nushell_0_86.html The ChangeLog is too long to reproduce here.
shells/nushell: enable trash feature
shells/nushell: update to 0.85.0 Themes of this release/New features Nushell + Uutils = ❤️ he Nushell team is thrilled to announce 🥳 that we've begun working with the uutils/coreutils team on integrating some of their foundational core utilies into nushell. With this release, we've started with the coreutils cp command, which we've temporarily named ucp. We're starting with ucp to allow broad testing while the current nushell cp command remains the default. We've already found one bug in the coreutils cp command and you might find others. Once it stabelizes, probably with the 0.86.0 release, we'll remove the nushell cp command and rename ucp to cp. In keeping with the nushell style, we've only added a handful of parameters. We can, and probably will, add more if the community determines we need them. We're so very excited and would like to thank terts, from the coreutils team, for his excellent help and special appreciation to dmatos2012 for the, very iterative, first uutils/coreutils integration PR #10097 for the cp command. To read more about how this came to be, checkout our blog post. Read about the full list of changes at: https://www.nushell.sh/blog/2023-09-19-nushell_0_85_0.html
shell/nushell: update to 0.84.0
Themes of this release / New features
*(Major Breaking Change!) str replace matches substring by default (kubouch)
str replace now matches a substring instead of a regular expression by default
and the -s/--string flag is deprecated (will be removed altogether in 0.85).
Matching a substring by default makes it more consistent with the rest of the
Nushell's commands.
Note! Since str replace is a widely used command, many scripts are going to
break. Fixing it is easy:
- If you used str replace without the -s/--string flag, you used regex matching
and you should add --regex flag to keep the previous functionality.
- If you used str replace with the -s/--string flag, you will get a deprecation
warning. To get rid of the warning, simply remove the flag.
*Constants from modules (WindSoilder, kubouch)
You can now use constants in modules and export them. Calling use on a module
will create record containing all module's constants. You can also import the
constants directly, for example with use module.nu const-name, without creating
the module's record.
The exported values are true constants which means that you can use them in some
scenarios where you cannot use normal variables.
*New options for more compact table display (@zhiburt, #9796)
To save screen space, you can now display tables with the header directly
displayed on the border through the $env.config.table.header_on_separator
option.
Additionally you can now configure the padding left and right of the table cell
content either separately or all at once to adjust the layout for your
readability needs.
*More consistent format ... commands (@sholderbach, @WindSoilder)
With this release we moved several commands that serve to produce string output
from a particular data type as format subcommands.
- date format has been renamed to format date (#9788).
- into duration --convert was previously used to provide string
representations of durations. This option has been removed and you should
now use format duration. (#9902)
- format filesize that was previously moved into the --features extra set is
back in the core (#9978).
*scope commands enhancements (kubouch, kubouch)
scope commands received a significant amount of improvements making them more
useful for advanced introspection of Nushell's definitions.
- scope externs now lists known externals (defined with extern)
- scope aliases is now fixed and lists names and usages of the aliases, not
of the aliased commands (this used to cause some confusion)
- scope modules now lists all the exportable of the module, including
submodules with their contents
- all scope commands now list the definition's ID which can be used for
reliable tracking of definitions. For example, a command foo imported from
a module spam using use spam will be named spam foo, therefore, relying
solely on names of the definitions can sometimes be misleading.
- module_name field is no longer present
- scope variables now denotes whether a variable is a constant or not
*http commands now handle headers better (@jflics6460, @ineu)
You can now pass headers directly as a record to the -H flag.
When running a http command with --full to get additional metadata about the
response you can now get both the request and the reponse header.
*Work on the optional dataframe features (@ayax79)
@ayax79 has been working hard to update our dataframe command to work again
with the stricter type check by consolidating internal logic (#9860, #9951).
Furthermore, dfr open now suppports the avro exchange format and a new dfr
to-avro command was added in #10019
*Changes to other commands
Since last release, some commands have changed, here is a list of some
interesting changed
- @atahabaki in #9841, #9856 and #9940: Some refinement of the str expand
command (it's a really cool command, i recommend you check it out 😃)
- @fdncred in #9987: Allow select to take a variable with a list of columns
- @fdncred in #10048: Allow int as a cellpath for select
*Command organization (@storm, @jntrnr)
In our efforts towards stabilization we moved several commands either behind
the --features extra build-flag or back into the core set of commands. The
special str *-case commands for example have been moved out of the core set,
while the bytes commands to deal with bytes in arbitrary encodings have returned
to the core set. Furthermore all commands in the core set should now have
helpful categories associated with them.
*Deprecation and removal of commands (@amtoine, @sholderbach)
We previously used the term "deprecation" pretty loosely to describe the removal
of commands while emitting a helpful error. We intend to now start to use
deprecation to warn you before the final removal of a particular option or
command. When we removed a command we will now properly refer to it as removal
and started adding warnings where appropriate (e.g. str replace --string). As
part of this update we removed some very old error helpers nudging you to
upgrade to new commands.
*Documentation
Thanks to @rgwood, @sholderbach, @kubouch and @fdncred the documentation has
become a bit better in #9961, #9996, #10004 and #10057.
*Notable bugfixes
- A panic when parsing the context of let assignments has been fixed
(@mengsuenyan in #9851)
- Invoking --help on a script with a def main command will now report the
script's name instead of a more confusing main (@jntrnr in #9948)
- Serious bugs in parse that produced incorrect output when given a long
input stream have been fixed (@panicbit in #9925, #9950)
*Breaking changes
- #9902 date format has been renamed to format date for consistency.
- #9788 The option into duration --convert to format durations has been
removed. Use the format duration command instead.
- #10038 str replace now by default matches to strings by default. If you
want to use regexes you need to use the -r flag. The --strings flag has
been removed
- #9632 To be unambiguous the duration type now does not report months or
years. The largest unit reported is weeks as they have a consistent length
compared to months or years.
- #9926 We moved some of the more exotic str case-commands behind the
--features extra build-flag. This affects:
- str camel-case
- str kebab-case
- str pascal-case
- str screaming-snake-case
- str snake-case
- str title-case
- #10053 make the charpage optional for std clip
- #10023 The output of the scope commands has changed
*Internal breaking change only affecting plugin authors
- #9927 Make Value::columns return slice instead of cloned Vec
shells/nushell: update to 0.83.1 Nushell 0.83.1 (hot-fix) A few days ago, we released the 0.83 version of Nushell. As you can see in the release notes, the release included a major upgrade to the type system as well as wide-reaching breaking changes. Extensive efforts were made before the release to mitigate these changes to make them easier to adopt when 0.93 was released, and included: - quite a lot of command signatures have been updated to keep functionalities at the same level while adding better type checking - major integration scripts from 3rd-party applications have been fixed prior to the release However, as you might have noticed and thanks to the feedback of you the community, more issues and bugs have been found. Many commands needed additional updates to play well with the updated type system. We decided to release a hotfix release to address what had been found, and this is that release. You can find out more about the hotfix in Tracking issue for 0.83.0 fixup #9812 What does the hot-fix release address? Most of the type-system-related issues have been fixed, hopefully bringing most of the command set of Nushell back to its previous feature level with the nice addition of better input/output type checking and annotations. In a few places, the type system itself was fixed, as with the case of $rest args now type-checking correctly in a pipeline. What will the hot-fix release NOT address? Bring the let-env command back to life. Thankfully, the community helped by updating their Nushell integrations and releasing corresponding new versions. Please, check your tools like starship for updates. Fully fix the dataframe integration. When upgrading the type system for the 0.83, we removed a semi-working system that enabled the dataframe commands to run both in a lazy and eager mode, but only if the types were known at parse-time. Due to the complexity of reworking this and the dataframe support currently being a tier-two feature in Nushell, we won't be able to fully fix this with this patch release. Thankfully @ayax79 started work in #9858 which promises to make the dataframe commands work again within the general Nushell type system. Breaking changes for plugin authors With the type system changes in 0.83.0 any plugins that declared that their signature "vectorizes_over_list": true were not able to automatically broadcast their operation for a type T (e.g. number) over a list<T> input. With this patch release, we removed this field from nu-protocol. You need to add the list<T> signature if necessary. Also recompile your plugins using nu-plugin 0.83.1 or remove the vectorizes_over_list field from the signature information if you don't use nu-plugin (e.g. plugins not implemented in Rust). Breaking changes for plugin users You may need to recompile or update your plugins and then re-register your plugins.
shells/nushell: update to 0.83.0
Themes of this release / New features
Since last release, some commands have changed and some have been created,
here is a list of some changes and what they mean:
- amtoine in #9646
: which returns the type of the command instead of only whether it is
builtin or not and uses more explicit column names
- atahabaki in #9750
: str expand now allows empty member in brace expansion, e.g. A{,B,C} would
expand to [A, AB, AC]
- fdncred in #9669
: keybinding listen gives more information about keys like home and end,
namely their kind and state
- NotLebedev in #9453
: input listen allows to query for a single key press, e.g. the following
will take a 4-char input 1..4 | each { input listen } |
where key_type == char | get code | str join
- kubouch in #9687
: path commands lose the -c flag; instead, use update to update table columns
Command set refinement efforts
Again with this new release, we are continuing refining our set of core
commands. As part of this, another set of commands have moved to extra.
Thanks to folks who are helping our efforts on the road to 1.0!
Note
No command has been removed completely, they have just been moved in the
extra feature of Nushell. simply use cargo ... --features extra to reenable
them.
Math commands have been moved by @stormasm in #9674, #9657 and #9647 and the
following commands have been moved in #9404
: fmt, each while, roll, roll down, roll left, roll right, roll up, rotate,
update cells, decode hex, encode hex, from url, to html, ansi gradient,
ansi linkand format
Language improvements
Since last release, a few changes have happened to the Nu language itself.
Declaration and assignment of variables
Until now, declaration keywords such as let and mut have required the use of
parentheses around pipelines to assign the output of a chain of command to a
variable. Thanks to @jntrnr in #9658 and #9589, this syntax has been relaxed
for let and mut.
Another parser improvement has to do with the use of if and match in variable
assignment. In #9650, @Windsoilder
Input / output type checking and annotations (@jntrnr)
Nushell as a language is more strictly typed than other shell languages.
However, not everything was type-checked nor possible to annotate and this
new release tries to fill this gap a bit more.
First, #9686 makes the input / output type signatures clearer in the help pages
of commands. Then, #9690 and #9680 enable input / output type annotations on
custom commands and enforce a strong type checking on the input and output of
commands. This means a few things:
- the input / output of custom commands can be annotated
- some type-invalid calls to commands are now parsed as an error,
e.g. 123 | get foo gives the an error.
This is still a work in progress, so some commands might have incorrect or
missing input / output type annotations 😮 This is expected and we worked and
are working on this to fix all incorrect signatures (#9755, #9749, #9707,
#9706, #9695, #9683, #9775, #9741, #9742, #9739 and #9778)!
Shoutouts
In between the two releases, @1Kinoti has worked on some nice improvements to
the language
- match guards have been added to the match command in #9621
- table types can now have parameters, just as records and lists can, thansk
to #9613
- structural subtyping has been improved in #9614 and allow to match
structured types regardless of the orders of the fields
Configuration tweaks
Contributions have been made to give a more consistent and sensible default
experience in Nushell, both when using the default_config.nu config file or
when not having a config, e.g. with nu -n. A better right prompt has been
written in #9585 and #9581 and the default configuration has been polished
in #9676
The standard library
The biggest topic in this 0.83 release for the standard library has been the
test runner!
Thanks to @Yethal, the test runner of the standard library can now use
annotations to decide whether or not to run a command as part of the test
suite of a project: #9628, #9622, #9611 and #9406
and std testing run-tests would successfully run the addition test, no need to
define tests with test_ in their names!
Thanks to @Hofer-Julian (#9607), the standard library now also comes with a
pwd command that tells you were you are in the filesystem.
Breaking changes
PLEASE NOTE: there are some big breaking changes in this release. These include:
- Removal of let-env (now use the $env.FOO = "BAR" form instead)
- Stricter checking of input/output types
- Transitioning of a set of commands to now be avialable via extra feature
rather than default
shells/nushell: update to 0.82.0
Today, we're releasing version 0.82 of Nu. This release focuses on polishing
the user experience.
Note: Beginning with this release, Nushell is switching to a four-week release
schedule.
For details see, https://www.nushell.sh/blog/2023-06-27-road-to-1_0.html
NOTE: The optional dataframe functionality is available
using --features=dataframe
This feature is not enabled by default on pkgsrc.
To compile with this feature add 'dataframe' to the list of features defined
(CARGO_FEATURES+=) in the package Makefile.
As part of this release, we also publish a set of optional plugins.
Themes of this release/New features:
- Custom datetime format (@fnordpig)
Until now, Nushell did not allow changing the default format of dates and times,
leading quite often to undesired rendering, e.g. seeing 'A year ago' in the
output of ls when one wants to know the exact time.
#9500 introduces a new config option to change the default output of dates and
times.
- Support for comments in multiline pipes (@WindSoilder)
From now on, either in the REPL, in scripts or in modules, you can comment out
any line of a multiline pipe without breaking its execution. This hopefully
makes debugging and testing part of a pipeline much easier!
- Continuing cratification effort
On the road to 1.0, we have started moving commands around to make place for
those which really matter. As this process involves the creation of some new
Rust crates, e.g. nu-cmd-extra, we call it cratification 😃
With this new release, the bytes commands have been moved behind the extra
feature (use cargo build --features extra to activate them back).
Apart from moving less stable or common ocmmands behind flag, this should also
improve compile times for everyone.
- Splitting the $nu variable (@jntrnr)
Nushell 0.82 introduces a new familly of stat commands, the scope ... commands.
These commands allow you to access some information about the current Nushell
instance that were previously available in the $nu variable!
e.g. $nu.scope.commands now becomes scope commands.
On the other hand, $nu becomes much smaller and only holds simple paths and
constants.
- Entering Linguist support (@hustcer)
With the efforts of @hustcer, Nushell is now an official language of Linguist,
allowing for better language support in GitHub.
- REPL: Mark line entries as excluded from the history by leading with a space
(samlich)
In some situations you may want to avoid storing an entry inside your shell
history. For example if it includes a secret or running it again in a different
context could be dangerous. To stop nushell from storing a particular line in
its history you can now start with a space and it will be ignored. You can
still recall your last entry once by pressing the Up-Arrow but the command will
never be written to disk and disappear as soon as you submit another command.
- New commands
http options
scope aliases
scope commands
scope engine-stats
scope modules
scope variables
scope
- Breaking changes
#9509 Cratification moves the bytes commands to nu-cmd-extra. They are thus
only accessible with --features extra
#9496 Clean up config by removing legacy options that were previously
deprecated.
#9487 Split $nu variable into scope commands and simpler $nu
#9427 The filesize prefixes Z/Zi have been removed as their underlying
values where not correctly representable.
#9407 In the ls --long output the uid column has been renamed to user to be
consistent with group
#9368 Don't allow save command to save both stdout and stderr to the same
file
shells/nushell: update to 0.81.0 Themes of this release / New features Polishing the experience This release focuses on improving the user experience, fixing some long-standing bugs, and adding a few helpful features. One of the bugs that was fixed for 0.81 was a long-standing issue with reedline, Nushell's line editor. Now, Nushell will prefer to move to make room for text that had been output rather than risking writing over top of it. This maybe improve the general experience of working in the terminal, resizing, and more. There have also been fixes to table printing to make it work better for more cases. Startup time improvements Startup times have also been improved. Through a combination of various fixes to both how the standard library files were handles and how the parser worked, we've been able to see significant improvements, sometimes as high as 30-50% faster. Breaking changes We had to remove ARMv7 and RISC-V from this release due to a breaking change in one of the dependencies. We hope to resolve this for future releases. Exclude globs now need square brackets view source now works over rest arguments alias calls are now position dependent
shells/nushell: update to 0.80.0
Themes of this release / New features
- Record type annotations (@1Kinoti)
Starting with this release, you can add more information about the type of
a record your command expects. For example:
def okay [person: record<name: string age: int>] {}
The above will require two fields to be present, a name that's a string, and
an age that's an int. The current version requires that the record has
exactly these fields, though we may loosen this in future releases to allow
for structural subtyping.
- Modules from directories (@Kubouch)
It is now possible to create a module from a directory. The directory must
contain mod.nu and all other .nu files are added as a submodule of the
module. This allows some traditional shell patterns such as dumping
completion files into a directory to be loaded automatically. Check out the
newly updated book chapter for more details and examples.
The enabling feature for module directories was organizing modules into
submodule structure instead of solely relying on re-importing symbols with
export use. module and especially export module have been added as a result
of this change. While not immediately visible, the module update allows for
cleaner submodule oganization without relying on re-exporting symbols with
export use. Since modules are now aware of their submodules, in the future
we hope to improve discoverability of definitions within modules, enhancing
our IDE support (such as our LSP).
- Stdlib update ([@amtoine, @EmilySeville7cfg, @skelly37, @YummyOreo]
[std-lib PRs])
Breaking changes
- #8940 Change type of parameter default values to Option<Value>
- #9007 Fix unexpected flattening of data by par-each (Issue #8497)
- #9056 REFACTOR: remove deprecated commands (old-alias)
shells/nushell: update to 0.79.0
Themes of this release / New features
- Standard library (@amtoine, @bobhy, @fdncred, @presidento, ...)
This is it. We finally release the standard library with this 0.79!
It's been on the mind of the core team of Nushell for some time and it was
made real between the two releases.
But first of all... what is the standard library?
The nushell standard library is a collection of nushell scripts that are
automatically loaded in the nushell binary and reachable via the use command
without any additional setup.
Note: some of the commands from the standard library are used without human
intervention as part of what we call the prelude.
As said above, the other commands are available with the use command.
The goal of this library is, as its name suggests, to provide a standard
experience and a standardized set of commands and tools to any Nushell user.
In std, one can find things like:
- a test framework to write robust Nushell scripts, modules and libraries
- implementation of builtin commands once written in rust
- logging commands with several log levels
- ...
Note: yes, you heard right, in the future, the standard library might become
a sanctuary for non-time-critical commands that were once written in rust as
part of the built-in set of commands!
Right now, we are actively trying to move the help commands from the nushell
core implementation to the library.
With this release, the library comes with the following custom commands:
std assert, std dirs, std help, std iter, std log and xml module
See https://www.nushell.sh/blog/2023-04-25-nushell_0_79.html for a
description of these and a list of available sub-commands.
some other commands live under the std namespace, without any module: clip,
path add and run-tests.
- TL;DR
As there has been quite a lot of contributions already (see the 50 closed
PRs at the time i'm writing this), i'm just gonna give some hints and links
in this release note, leaving the rest to the amazing work of other
contributors who wrote parts of the lib and its documents
(shout out to @bobhy, @fdncred and @presidento)
- the library can be used and tested with or use direct imports, such as
use std dirs
- one can follow the activity of the library in the roadmap
- the library comes with a test framework; see the Testing your Nushell code
chapter of the book
- the long term information, changelog and updates shall be found in the
Standard library chapter of the Nushell book
- if you are a contributor willing to help out, everything happens in the
nu-std crate, especially the CONTRIBUTING.md document which explains all
there is to know about "developing with std" in great details.
If, for some reason, you want to load Nushell without the standard library,
start nu with the --no-std-lib. This can be the case if you find the startup
times much longer than before. We're aiming to improve the loading speed
in the future.
- enhanced IDE support in our VS code extension (JT, fdncred)
Nushell now has a first LSP (Language Server Protocol) implementation with a
VSCode integration. If you install the latest version of our VSCode plugin,
you'll see hovers, inlays, tooltips, error squigglies and other features.
We are still very early in the LSP development, but the extension is already
very usable and definitely moves the experience of writing Nu code to another
level!
While currently we have only VSCode integration, the server itself is
standalone and we welcome projects adding the LSP support to more editors.
- atuin now supports Nushell
Thanks to @stevenxxiu you can now use atuin with Nushell. We are happy to see
Nushell supported by more projects and we welcome PRs adding more
integrations.
- Relaxed parsing rules (JT)
We listened to your feedback around the syntax changes introduced with 0.78
and decided to revert to the old behavior around the parsing rules for
numeric literals as well as the compulsory || for closures.
- Removed old alias implementation (kubouch)
While there are still some missing pieces, we removed the old alias
implementation. This means that old-alias is no longer available. We decided
to remove it to clean up the code. It makes further fixes to aliases easier
as you do not need to remember which alias implementation a piece of code
belongs to.
There are two notable missing features from the old aliases:
- Missing completions with external completers.
- Most parser keywords (such as source) cannot be aliased but adding support
for aliasing them should be possible in most cases.
- Not possible to alias with environment shorthands
(e.g., alias foo = FOO=bar spam)
- Some presentation issues, such as the output of which and the alias usage
pointing at the aliased call instead of the alias itself.
- Changes to default files locations (ito-hiroki)
$nu.config-path and $nu.env-path are now set based on --config
and --env-config flags passed to Nushell and also use the path after
resolving symlinks. This means that they no longer guarantee pointing at the
default Nushell's config directory. To be able to refere to the default
config directory, $nu.default-config-dir was added and used in default env.nu
to always point NU_LIB_DIRS to the scripts directory under the default config
directory.
Related to that, $env.CURRENT_FILE was added to be able to show the currently
evaluated file.
- Breaking changes
#8797 old-alias is no longer available
#8724 str index-of -r now uses ranges
#8792 config nu and config env now open $nu.config-path and $nu.env-path,
respectively.
#8779 Aliasing math expressions now shows error immediately instead of
failing silently and showing a confusing error later.
#8917 exec inherits Nushell's environment variables
#8887 NU_LIB_DIRS definition in env.nu changed
shell/nushell: update to 0.78.0
Themes of this release / New features
- Pattern matching (jt)
With 0.78, Nushell now comes with the match expression, which allows you to
do pattern matching on a value. It supports a variety of different kinds of
patterns, which can be mixed and matched to create more complicated patterns.
- Alias changes (kubouch)
- Aliases now can shadow
We've updated the new alias command we introduced in 0.77 to work more
closely to the previous one.
- Alias can be named the same as the aliased command
- Old alias still keeps working
Since there are still some remaining issues to fix with the new alias
implementation, we still keep old-alias around for this release.
- Speed improvements (jt)
We've sped up the performance of tight loops like for and while considerably
in this release.
- Optional cell path members (rgwood)
In Nu 0.78, you can use ? in cell paths to suppress errors from missing data.
? is a more convenient+powerful version of the -i/--ignore-errors flag on
get and select.
- better error handling in error make (amtoine in #8511 and #8570)
The error make command now gives better hints about why the format is not a
valid error make format:
- with an empty format, error make {} will say that there is a "missing
required member $.msg"
- with an empty $.label, error make {msg: "message", label: {}} will say
there is a "missing required member $.label.text"
- finally, when $.label.start / $.label.end is not defined while the other
is, error make will give a hint as to add the missing one to the format!
The second change disallow the use of a $.label.start greater than
$.label.end as a span.
- Support for pretty output format in to nuon (amtoine)
The to nuon command can now output pretty NUON data with whitespaces for
better readability.
The default behaviour still is to output everything on a single line,
encouraging users to leverage the compactness of the NUON data format.
- New math exp command (lesves)
To complement the math ln command, we now include a math exp command for
exponentiation with the base e.
Breaking changes
- let requires surrounding parentheses for saving command output
let x = ls will not run the ls command anymore. If you need to save the
output of a command, you need to wrap it in parentheses: let x = (ls).
- || now required in closures
To help differentiate between blocks (which can mutate variables) and
closures (which can be used in a pipeline), we've changed the syntax of
closures to require ||. This means the simplest closure now looks like {|| }
- We no longer automatically print values as part of a script
We've changed the automatic-printing rules for scripts and the REPL to now
only automatically print the last value. This means two major breaking
changes:
- We no longer automatically print loop values
- We no longer print the results of every line automatically, requiring
you to do it manually
- Bare words can't start with a number
Words that start with a number or are in some way number-like must now must
be wrapped in backticks to be treated at a bare word or wrapped in quotes to
be a string
- Fields can only be defined once
You can no longer redefine a field in a record during initialization
- Thread configuration moves to par-each
Nushell no longer accepts the -t/--threads flag to the binary as it's now
part of par-each
- Ranges become the standard range specifier
str substring now only accepts ranges as does bytes at
- Alias recursion has been disabled
- Empty lists handled more consistently
[] | select foo now returns an empty list instead of null and sort, uniq,
sort-by, and uniq-by now return empty lists when given an empty list
(previously they would throw an error)
These changes make it easier to work with lists of unknown size.
- Comparison operators now allow null
Previously expressions like 1 < null would error; now they return null
shells/nushell: update to 0.77.1 The 0.77.1 release is a hotfix release of 0.77. It fixes an issue related to subexpressions not properly handling output values.
shells/nushell: update to 0.77.0
Themes of this release / New features
- Reworked aliases (Breaking changes!) (kubouch)
Aliases have been a constant source of panics and growing code complexity as
a result of trying to patch the panics. In this release, we re-implement
aliases from scratch. Instead of replacing spans of expressions, aliases are
implemented as another type of command, quite like extern is used to
implement known externals. Alias is a command that wraps another command
call. As a result, in some cases, aliases do not behave exactly the same as
before. Here are the key facts:
- Alias can only alias another command call. For example, alias la = ls -a
works, but the following does not:
- alias foo = "foo"
"foo" is not a command call, use alias foo = echo "foo" instead
- alias lsn = (ls | sort-by type name -i)
subexpression is not a command call, use a custom command instead
- Alias cannot alias command named the same as the alias. E.g., alias
ls = ls -a is not possible currently, and gives an unhelpful error message.
We plan to fix this as soon as possible and in the future we aim for this
to work.
- Some parser keywords are not allowed to be aliased. Currently, overlay
commands can be aliased but the other parser keywords can not. We can add
support for aliasing more parser keywords in the future.
If some of the above is too limiting for you, the old aliases are still
unchanged and available as old-alias. Just change alias to old-alias and it
should work the same as before. If there are no more problems with the new
alias implementation, and we manage to iron out the recursive alias issue,
we will remove old-alias in the next release, otherwise, we'll keep it around
longer.
- More consistent timestamp handling (bobhy)
Simplified conversion between Nushell date type and unix timestamps (#8244).
Nushell now standardizes on representing a Unix timestamp as a number of
nanoseconds relative to the unix epoch 1970-01-01 00:00:00 +0000 (UTC).
Since the timestamp is stored in a (64 bit signed) Nushell int type, this
limits the range of dates that can be represented to approximately 21-sep-1677
through 11-apr-2262.
In prior versions, Nushell attempted to extend the range of representable dates
by allowing multiple resolutions of timestamps (seconds, milliseconds as well
as nanoseconds) to be stored and relied on arbitrary range check heuristics to
disambiguate the value intended. However, there were bugs in the checks and
incorrect results could be produced.
With this change <int> | into datetime assumes the input is a number of
nanoseconds and can never produce a date outside this range.
The timestamp epoch is the standard unix epoch. Note the timezone is UTC/GMT.
<datetime> | into int can now produce an error if the input is outside the
supported range.
And finally, although not strictly required by the above fix,
<date> | date to-record and <date> | date to-table now have a nanosecond field
containing the subsecond residue of the input value (however it was produced).
- New XML format (NotLebedev)
New format for xml data created and accepted by from xml and to xml commands
(#7947).
Commands from xml and to xml now use format where each xml entry is represented
by a single {tag: <tag name> attributes: <tag attributes> content:
[<child entries>]} record. Special xml entries also use this record, replacing
irrelevant fields with null for easier use.
Creating a little html page. In case of to xml one can deviate from rigid
structure and omit empty fields of records.
- New additions to $nu (StevenDoesStuffs, amtoine)
The builtin $nu variable now contains new entries:
- is-interactive: Nushell was launched in interactive mode
- is-login: Nushell was launched in login mode
- startup_time: Nushell's startup time
- Reworked http subcommands (jaudiger)
The http command now has more subcommands and existing subcommands have been
reworked.
Make sure to browse the help messages of these commands. They contain fully
functional examples thanks to pointing at www.example.com.
- Breaking changes
- Alias changes, see above
- env command has been removed, use $env instead
(https://github.com/nushell/nushell/pull/8185)
- str trim no longer has --all, --both, and --format flags. str replace
should be an adequate replacement; please let us know if it is not (#8205)
- The changes to timestamp handling noted above (#8244) can require code
changes to existing scripts:
- Saved data containing the results of an old datetime-to-timestamp
conversion will not deserialize correctly when read back by the current
version of Nushell. In general, Nushell will produce incorrect datetime
values without noting an error.
- <int> | into datetime now assumes nanosecond scaling for all timestamps.
You must ensure all timestamps computed by your script or retrieved from
external sources are scaled appropriately.
- <date> | into int can now fail, as noted above. You cannot rely on this
operation to persist a arbitrary date.
- The change to from xml and to xml commands noted above (#7947) will
require to update scripts relying on old output/input format.
- mkdir, cp, mv and rm return nothing. Errors and actions with --verbose
flag are printed to stderr instead (#8014).
- Plugin authors relying on nu_protocol::Value may need to update their
code to account for a change to Value::Error (#8375 )
- Different types of lists can now be appended. This can break scripts that
were relying on the stricter behavior
(https://github.com/nushell/nushell/pull/8157)
shells/nushell: update to 0.76.0 Debugging We've added a few new commands to help with nushell debugging. - ast - The ast command works the same as before and produces an ast for any pipeline you give it. - debug - The debug command works the same as before and produces some output about nushell values. - explain - Provides detailed information about pipeline contents in a closure The explain command attempts to explain to you how the pipeline, in the passed in block, is going to be interpreted. It shows the pipeline and command index, the looked up and found command name, the command argument data type, and argument details, among other things. Note that spans are also included and can be used with view span. - inspect - Immediately prints out the contents of a pipeline The purpose of the inspect command is to help to debug pipelines. It works by allowing you to inject the inspect command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into inspect. With each step it prints this information out while also passing the value information on to the next step in the pipeline. - metadata - The metadata command works the same as before. - profile - Recursively profile pipelines and pipeline elements within a closure. Enables fine-grained profiling of individual pipeline elements and recursively stepping into blocks/closures. The recursion depth can be controlled (default is 1) and it can optionally collect the profiled source segments for easier orientation and value in each step for easier debugging. Note: There are known limitations that the profiler can't run. For example, it can't collect data from subexpressions and loop iterations. It is caused by profiling data being collected as pipeline metadata and a known bug that pipeline metadata is not preserved in some cases. - timeit (formerly known as benchmark, same functionality) - view files - Lists source code inputs loaded into Nushell since the beginning of the session view files lists the files and entries loaded into nushell's EngineState memory. Note the spans, for use with view span and the size of each file's contents stored. - view source (formerly known as view-source, same functionality) - view span - View contents of a span Spans are important to nushell. One of their uses is to show where errors are. For instance, in this example below, the leader lines pointing to parts of the command line are able to point to 10, /, and "bob" because each of those items have a span. In an effort to have a little more organization, we've assigned a category of Debug to all commands that participate in nushell script debugging. Here is a list of commands that are in that category now. -ast -debug -explain -inspect -metadata -profile -timeit -view -view files -view source -view span - "Multiplication" of strings and lists is now supported. (WindSoilder) Like in Python you can now use the multiplication operator * to create n concatenated copies of a string or list. Here n has to be an int value. This can be useful if you want to quickly build ASCII art 😃! Note that the operation is commutative. - Dataframe commands are again explicitly separated from core nushell commands. (#7998) - Dataframe commands have all been renamed in order to avoid confusion with nushell commands. It also makes our help commands less confusing. For instance, you can now do help select and understand how to use the traditional nushell select command and you can do help dfr select and understand how to use the dataframe specific select command. Previously this was a source of cryptic error messages that were confusing to users. -PATH vs Path (#8003) We fixed a PATH vs. Path bug in completions, so now you should be able to do commands like cod<tab> and get completions like code and code.cmd across all operating systems. - More commands become plugins and plugins get first-class help support (WindSoilder, #7984, #7942) In an effort to both make the core nushell binary smaller and to improve our plugins system along the way we moved the commands for several less common file formats to nu_plugin_formats. To make sure you still have a first-class experience while using these commands, our plugins can now support code examples in the help and F1 menu. As a result, plugin authors need to slightly update their command Signature to PluginSignature which supports the examples and recompile. - Improved error messages for int and string literals Nushell now gives more specific and helpful messages when it detects syntax errors. In this release we've improved errors for string and int literals but we hope to improve more in the future. #7952 Errors in the format of escapes within double-quoted strings are reported specifically. Invalid digits in radix-prefixed int literals are now flagged as a specific error. The old parser treated these invalid ints as bare strings. - General housekeeping in the Nu codebase (Hofer-Julian, fdncred, rgwood, sholderbach) We are very lucky that we recently had a number of new contributors starting to help out with bug fixes and improvements to Nushell. We want to thank you and want to welcome you all! In the background a number of contributors spent some time improving and refactoring the codebase to get us up-to-date and make it more approachable for newcomers. This includes work to break up less readable code in important places, and a significant effort to get us up-to-speed on some coding standards. We also updated a number of dependencies and want to continue to improve our dependency tree. We recently enlisted the relentless help of the dependabot. Furthermore, we enabled rudimentary tracking of test coverage through codecov.io. This should help us identify areas were additional tests are needed and can be a great contribution to the project. - Breaking changes - load-env can not accidentally set $env.PWD anymore (#7963) - The --numbered flag to enumerate entries has been removed from each, par-each, each while, and reduce. Use the enumerate command added in 0.75 instead. (#7777) - Plugin system: nu_plugin::Plugin::signature has changed from fn signature(&self) -> Vec<Signature> to fn signature(&self) -> Vec<PluginSignature> to support examples on plugin commands. Plugin authors have to update the relative structure to apply these changes. Normally you just need to perform a global search/replace from Signature to PluginSignature, then rebuild and run with the latest nushell version. (#7984) - benchmark renamed to timeit (#8018) - dataframe commands renamed with a prefix of dfr (#7998) - view-source renamed to view source (#7989) - Plugin commands can now include examples, which necessitated a change to the plugin signature, which causes all plugins to need to be recompiled for use. (#7984) - str lpad and str rpad have been superceeded by fill in order to provide alignment (7846) - from ini, from vcf, from ics, from eml commands are moved to plugin called nu_plugin_formats to reduce the number of commands in nushell core, you need to install and register the plugin manually to use these command. (#7942) - http get -t,--timeout parameter is now -m,--max-time (8088) - Filesystem commands now print to stderr when using --verbose flag (8014) - The parse command will now create 0 indexed columns instead of 1 indexed (7897)
shells/nushell: update to 0.75.0
Themes of this release/New features
- Changed Unicode escapes in strings (bobhy)
WARNING
Breaking Change: You need to update escapes like "\u0043" to "\u{0043}"
This format allows you to insert any Unicode code point into a string by
specifying its value as 1 through 6 hex digits (with or without leading
zeros, upper or lower case). The maximum value is \u{10ffff}, which is the
largest Unicode code point defined.
We've simply dropped support for the old format since we're pre-1.0 and
didn't want to carry forward redundant syntax. You will have to change any
unicode escapes in your scripts to the new format.
Why change? The old 4-digit syntax could not natively address recent
extensions to Unicode standard, such as emoji, CJK extension and traditional
scripts. There is a cumbersome workaround in the form of surrogate pairs,
but this is not intuitive.
Why this change? The new format allows you to specify any Unicode code point
with a single, predictable syntax. Rust and ECMAScript 6 support the same
syntax. (Full disclosure: C++, Python and Java don't.)
- -g grapheme cluster flags for str length, str substring, str index-of, split
words and split chars (webbedspace)
As you know, str length, str substring, str index-of and split words measure
the length of strings and substrings in UTF-8 bytes, which is often very
unintuitive - all non-ASCII characters are of length 2 or more, and splitting
a non-ASCII character can create garbage characters as a result.
A much better alternative is to measure the length in extended grapheme
clusters. In Unicode, a "grapheme cluster" tries to map as closely as
possible to a single visible character. This means, among many other things:
- Non-ASCII characters, such as ん, are considered single units of length 1,
no matter how many UTF-8 bytes they use.
- Combined characters, such as e and ◌́ being combined to produce é, are
considered single units of length 1.
- Emojis, including combined emojis such as 🇯🇵, which is made of the 🇯and
emojis plus a zero-width joiner, are considered single units of length 1.
(This is a property of "extended" grapheme clusters.)
- "\r\n" is considered a single unit of length 1.
The new --graphemes/-g flag can be used with str length, str substring, str
index-of and split words to enable these length/indexing measurements.
In addition, the flag has been added to split chars. Notably, this command
splits on Unicode code points rather than UTF-8 bytes, so it doesn't have
the issue of turning non-ASCII characters into garbage characters.
However, combining emoji and combining characters do not correspond to
single code points, and are split by split chars. The -g flag keeps those
characters intact.
These commands also have --utf-8-bytes/-b flags which enable the legacy
behavior (and split chars has --code-points/-c). These currently do not do
anything and need not strictly be used, since UTF-8 byte lengths are still
the default behaviour. However, if this default someday changes, then these
flags will guarantee that the legacy behaviour is used.
- New enumerate command (JT)
A new enumerate command will enumerate the input, and add an index and item
record for each item. The index is the number of the item in the input
stream, and item is the original value of the item.
Rather than relying on the --numbered flags of commands like each, with the
enumerate command we take more modular and composable approach than
hard-coding flags to our commands. (Note: The --numbered flags have not
been removed yet.)
- Breaking changes to the web-related commands (Kazuki-Ya,VincenzoCarlino)
We decided to move some of the important commmand for interacting with HTTP
under their own http subcommands for better discoverability. The common
fetch command is now http get.
- main command exported from module defines top-level module command (kubouch)
Defining and exporting a maincommand from a module allows creating a command
with the same name as the module.
The same thing works overlay use as well. Note that the main command
continues to work the same way as before when running a script.
Combined with a recent bugfix, this feature allows for nicer way of defining
known externals and custom completions.
It is also a stepping stone towards being able to handle directories which
in turn is a stepping stone towards having proper Nushell packages.
- Progress bar for save command (Xoffio)
To watch the progress when saving large files you can now pass the
--progress flag to save. It gives information about the throughput and an
interactive progress bar if available.
Breaking changes
- Unicode escapes in strings now use and extended format \u{X...}, any
scripts using the old syntax \uXXXX will have to be updated. See also #7883.
- The to url command has been renamed and moved to url build-query as this
better reflects is role as a nushell specific url command compared to a
conversion. (#7702)
- fetch has been renamed to http get (#7796)
- post has been renamed to http post (#7796)
- Quotes are trimmed when escaping to cmd.exe (#7740)
- parse -r now uses zero-indexed rows and uncapitalized columns (#7897)
- last, skip, drop, take until, take while, skip until, skip while, where,
reverse, shuffle, append, prepend and sort-by raise error when given
non-lists (#7623)
- to csv and to tsv now throw error on unsupported inputs (7850)
shells/nushell: update to 0.74.0
0.74.0
Themes of this release / New features
- Known externals commands and exec now have "fall-through" signatures
(merelymyself, WindSoilder, kubouch). A common pitfall in Nushell when
defining custom signatures using extern used to be that unrecognized
arguments passed to the command would throw an error. Now, arguments are
still checked against the extern signature but those that are not recognized
are simply ignored.
exec uses similar style which fixes errors with tools like ssh and gdb that
internally invoke exec.
- help is now more helpful (kubouch). For a long time, Nushell had the option
to provide custom help messages for commands via comments.
In this release, we allow user-defined help messages with aliases and
modules. This goes hand-in-hand with a handful of new help subcommands to
explore these help messages. The help messages now also treat the first line
followed by an empty line as a "brief" description displayed in summary
tables generated by help commands, $nu.scope.aliases, etc. The full
description is available when querying a particular command/alias/module
(e.g., help spam). This brief vs. full separation was already present for
built-in commands, like path, but now it is applied also to all user-defined
help messages. The current batch of improvements can still be taken further.
For example, custom help messages could possibly be defined also for
variables and environment variables (via comments adjacent to let and
let-env). We could also further improve the presentation of existing help
xxx commands.
- nitial support for parse-time constants (kubouch). This is a
proof-of-concept that we plan to expand in the future. Tip: We also addedd a
new book section with an in-depth explanation of Nushell's parsing and
evaluation, hopefully clearing up some confusion about things like
"Why can't I source a dynamic path?". It also touches on the concept of
parse-time constants. A new const keyword is added to Nushell to define
"parse-time" constants. Constants defined with const behave the same as
variables defined with let, but in addition, they are usable in some
contexts that require values known at parse-time. Currently, this applies
to files or names passed to use, overlay use, source, and source-env.
Only a limited subset of values is allowed to be a constant. In general,
"simple" values, like strings or integers, and their collections (lists,
records) are allowed but values requiring some evaluation (string
interpolation, subexpressions, environment variables) are not allowed.
The current selection is not set in stone, however, and might change in
the future.
Some future direction we can take this:
- Move parts of $nu to be constant to allow things like source
$nu.config-path
- Allow modules to have constants (module spam { const CONTENTS =
[ 'eggs', 'bacon', 'sausage', 'spam' ] })
- Some limited form of parse-time evaluation to allow static control flow
In general, we want to be very conservative with parse-time constants and
evaluation because it can be easy to introduce awkward side-effects and
performance pitfalls. We plan to extend this only where it brings some
tangible benefit to Nushell's user experience.
- New url encode command to percent-encode URLs (MehulG). To encode text that
is used as a path component in a URL we now provide url encode. By default
it preserves the structure of a URL and only replaces invalid characters.
With --all the whole string gets encoded.
- values command to programmatically interact with records (webbedspace).
This is a complement to columns, designed to allow the values of a record
to be easily filtered and iterated over using the standard list tools like
each and where. The name values is derived from similar functions in Ruby,
Python and JavaScript. It can also operate on tables to convert them to
lists-of-lists.
- get, select, cell path access on tables will now error when encountering
a hole (kubouch, webbedspace). Formerly, this would produce ['bar', null] -
converting the table hole into a null. Now, however, they will produce an
error. The original null-conversion behaviour can, as usual, be opted into
using the -i flag for get and select: [{foo: 'bar'}, {}] | get -i foo
produces ['bar', null]. (There are also plans for a future version of
Nushell to expand the cell path syntax to allow certain cell names to be
"nullable" - converted to null if they don't exist.).
- Behavior of -i/--ignore-errors flag for get and select when the entire
column is absent has changed. Formerly, if select -i or get -i couldn't find
any value for the given column, it would produce a single null. This has
been changed so that it now produces a table (or, in the case of get, a
list) of all nulls. This change was made to make this flag work more
consistently with default and compact.
- Certain misused punctuation in def definitions are now errors (webbedspace).
The following misuses of punctuation in def definitions now produce errors:
- Placing a comma between a long flag and its short alternative (e.g. def
a [--foo, (-f)] {})
- Consecutive commas, like def a [foo,,bar] {}
- Consecutive colons, like def a [foo::int] {}
- Using ^ in command names, like def ^a [] {}
- $in now works in catch closures.
$in in catch closures now behaves identically to how it does in other
closures, like those given to each (it's equivalent to what would be the
first named argument).
try { 'x' | math abs } catch { print $in } behaves the same as try
{ 'x' | math abs } catch {|e| print $e }.
- MIME-types are supported in ls with an additional flag. (fdncred). To find
out what application your operating system associates with a particular
file, you can now use the --mime-type or -m flag on our ls command.
This simplifies filtering for particular files and can help you dispatch
files to particular programs. When opening files with Nushell directly,
open will still follow the same heuristics using file endings and the
built-in from ... command parsers.
- Regular expression queries are cached for performance (rgwood). The primary
motivation for this is to make regex and =~ operator uses in hooks and
color_config closures more performant.
- All built-in commands now declare their pipeline input and output types
(sholderbach). A few releases back commands internally got the capability
to declare not only the types of parameters but also pairs for the input
and output on the pipeline. With this release we finally declare those
input and output types for all core nushell commands. This can help you as
user to see what a command expects from the pipeline and might return. We
are exploring how nushell can leverage that for more useful diagnostics
and completions. In the future we may introduce syntax for user-defined
commands to declare their input and output types explicitly.
- Breaking changes
- get and select now error when encountering a hole
- the behaviour of -i on get and select has changed columns will now error
for data that is not a table or a record (#7593)
- The dataframe specific command fill-na has been renamed to fill-nan to
better represent its capabilities (#7565)
- The requirements for the names of a nu command and a command alias have
been tightened to avoid some problems (#7392)
- to toml will only produce output for records now as the output for tables
is ambiguous and may be invalid to parse (#7597)
- exec and known externals don't throw errors when unknowns parameters are
passed to them
- help command has been thoroughly refactored and includes several more
subcommands. help <word> now matches commands, aliases, and modules.
- command names in help commands and $nu.scope.commands are displayed
correctly if they were imported from a module with a prefix
- hide command no longer hides environment variables. Use hide-env instead.
(#7687)
- math eval has been removed in favour of the direct math commands and
expressions (see help operators as well) (#7284)
- last, skip, drop, take until, take while, skip until, skip while, where,
reverse, shuffle, and sort-by are now stricter about which types of data
they accept (#7623)
0.73.0
Themes of this release / New features
PLEASE NOTE: Boolean && and || have changed
- The boolean && is now and and the boolean || is now or. These were deprecated
in the 0.72 release and have now been removed. Existing scripts will need to
be updated to the new syntax to run in 0.73.
- Experimental interactive explore command (zhiburt). This release includes a
new experimental command called explore for viewing Nu data in an
interactive UI. Some things to try:
- pipe a large table to explore (ex: ls | explore) and use explore as a
fancy pager
- run explore, then type :try and press the Enter key to enter a mode where
you can run commands inside explore
explore is highly experimental and we expect it to change in the future.
Please report any issues you discover.
- New math commands (sholderbach). With this release we include a larger number
of math commands for real valued math such as trigonometric functions and
logarithms. The goal is to remove the math eval command that operates on
strings instead of proper nushell expressions.
- Changes to commands with predicates (kubouch). any, all, skip until,
skip while, take until, and take while now accept a closure instead of a row
condition. This makes them slightly more verbose but it is a part of an
effort to refactor our parser to allow defining concrete grammar rules for
the Nu language. Row condition is currently accepted only in the where
command which becomes a parser built-in command (like use or let).
- New filter command and simpler where (kubouch). We found the -b flag of
where quite confusing and decided to remove it in favor of a new filter
command. Both filter and where have similar functionality but where now only
accepts a row condition and filter accepts a closure. Why is it useful to
have two commands doing the same thing? Because with the filter command,
you can store the closure in a variable. On the other hand, where is more
concise ([{a: 1} {a: 2}] | where a > 1) but you can't store its condition in
a variable. The choice is yours!
- New command uniq-by (raccmonteiro). To complement uniq which can identify
unique or duplicated values in a collection or report the number of
occurrences for a particular entry, we now have uniq-by. It supports
filtering a table by entries appearing in a particular column.
- Mutable data structures can now have their inner values mutated using
= (webbedspace). If a variable has been defined as mutable using the
recently-added mut keyword, you can now deeply mutate its inner values
using =. This syntax enhancement was added primarily to make modifying
$env.config during a normal session much easier. Now, $env.config is
considered inherently mutable. You can change a single config value.
- More sophisticated coloring of data values using closures (webbedspace).
The color_config config record has new functionality: instead of specifying
a single color name for all values of a given type, you may now alternatively
provide a closure that dynamically computes a color for each individual
value. The closure takes, as input, a single value of the given type, and
must produce either a string value representing a color, or a
{ fg, bg, attr } record (the same as what color_config already accepts as a
color value). This feature can be used to provide important visual
distinctions between ranges of values in data.
This causes all filesize values to be colored using dark_gray if they equal
0b, cyan_bold if they are less than 1mb, and blue_bold otherwise. This means
that, in ls output, empty files can be more easily distinguished from
non-empty ones. This colors true in light_cyan, and false in light_gray.
This can be useful when browsing a large table of booleans. The themes in
the default config.nu file have been updated with further examples of these
closures.
In certain situations (most notably, during a single ls call that isn't
piped to anything else) Nushell will parallelize the execution of these
closures. As such, you cannot expect that they will run in the same order
as each value appears in the output data.
WARNING
Currently, closures are only supported for output values - they do not work
with color settings that begin with shape_, such as shape_literal. They also
do not work with the color configuration for the new explore command. Only
values inside of tables are highlighted using closures.
Breaking Changes
- split row command will retain an empty string if splitted string is empty.
(#7413)
- split list now properly removes the separator in all positions (#7355)
- The --show-created-paths flag has been replaced by --verbose from mkdir.
- fetch removes --output, --bin, --append flags, use fetch with save to save
fetched page to a file. (#7468)
- changes to how get works with deep cell paths (#7480)
- mkdir's -s/--show-created-paths has been renamed to -v/--verbose for better
consistency (#7462)
- && is now and and || is now or
- any, all, skip until, skip while, take until, take while now take only a
closure as an argument.
- where now takes only row condition argument, -b flag removed.
0.72.1
- This is the 0.72.1 release of Nushell. It is a hotfix release of 0.72.0 that
changes how the Ubuntu release binary is built so that it does not change
glibc versions.
0.72.0
Today, we're releasing version 0.72 of Nu. This release includes many new
features: mutability, looping, early returns, changes to the core commands,
and much more.
NOTE: as part of this release, we are no longer including additional features
in --features=extra. With 0.72, SQLite features have moved into the main
Nushell installation and dataframe functionality is now part of
--features=dataframe.
As part of this release, we also publish a set of optional plugins you can
install and use with Nu. To install, use cargo install nu_plugin_<plugin name>.
Themes of this release / New features
- Try/catch
Starting with 0.72, it's now much easier to run a command that might fail
and then handle the failure if it happens.
The catch part of the try/catch is optional. Without it, the try block will
run, and any error that occurs will be ignored.
- Auto-expanding data views
Expanded data view
With the new default config, we now also detect the terminal width and will
automatically expand the data view to include more information if it's
available.
This uses an improved expanding data view capability from 0.70.
- Redirection
This release also includes a new way of redirecting the stdout and/or stderr
of external commands. This gives easier access to the output streams than was
previously possible.
You can also create a stream built from the above, allowing one stream to empty
and then be followed by the other stream.
- Closures/blocks
We have now split closures and blocks into two separate value types. A closure
can have parameters, can close over variables outside of its scope, and can be
passed as a value.
You can also think of creating a custom command like def foo [] { ... } as
creating a closure.
A block is much simpler and is used as the bottom of commands like if and loops.
Blocks don't close over (or capture) variables, don't have parameters, and
can't be passed as a value. Blocks, however, do have one special trick...
- Mutation
Starting in this release, you can create local mutable variables. You can
create mutable variables using the mut keyword.
A mutable variable can only live and change in the closure in which it's
created. Blocks, however, have access to the mutable variables in the parent
closure. For example, mutating a variable inside of the block used in an if
call is valid.
- Loop/while
The 0.72 release also includes a few new looping commands: loop and while.
The loop command runs a block forever.
The while command will run its block as long as a condition is met:
- Break/continue
Loops can now also use the break and continue feature common in many programming
languages. break will break out of the current loop. And continue will continue
the loop at the next iteration.
- Return
The 0.72 release also includes the ability to return early from a closure or
command.
- Command refinement, simplification, and elimination
This release contains many breaking changes to Nu's built-in commands (sorry!).
As we move toward version 1.0 we want to ensure that Nu ships with a small
curated set of consistent, well-designed "standard library" commands.
This requires taking a hard look at existing commands, and in some cases
breaking changes are unavoidable. We expect that this effort will span a
few release cycles.
- Dataframes no longer included by default - smaller binaries
Nu's dataframe support is extensive, impressive, and very useful to users who
rely on it. However, it comes at a high cost in terms of compile time, binary
size, and complexity. Starting with version 0.72, dataframe commands are no
longer included in the release binaries published on GitHub or the default
binaries published via package managers (like Homebrew, winget, Scoop).
As a result of this change, the main Nu executable is now about 50% smaller.
To continue using dataframe commands, you can build Nu from source using the
dataframe Cargo feature. For example, to install using Cargo: cargo install
nu --features=dataframe.
- Allow reloading overlay definitions (kubouch)
A common pattern in using overlays is shadowing an existing environment
variable, such as PROMPT_COMMAND. However, overlay use would keep loading the
value from the first activation.
Calling overlay use prompt for the first time changes the prompt to the current
time, however, subsequent calls to overlay use won't change the time. That's
because overlays, once activated, store their state so they can be hidden and
restored at later time. To force-reload the environment, we added a new --reload
flag: Calling overlay use --reload prompt repeatedly now updates the prompt with
the current time each time.
- virtualenv activation changes (kubouch)
Since the verion 20.17.0 of virtualenv, the new way to activate an environment
is to call overlay use activate.nu instead of the source activate.nu. This
change is in line with gradual deprecation of source and moving us towards
using modules as overlays in more cases. Please, check the activation script
itself for more details.
- Breaking changes
- As mentioned above, dataframe support has been removed from the default
Nu binaries.
- Nu's SQLite DSL commands have been removed. open foo.db and open
foo.db | query db "SELECT * ..." still work, but the commands which
mapped 1-to-1 with SQL clauses (ex: open foo.db | into db | select * |
from table some_table | order-by some_column) have been removed.
These commands were an interesting experiment but they didn't work out,
and we're removing them to simplify database access in Nu.
- The is_plugin, is_custom, and is_keyword columns in help commands have
been replaced with a single command_type column.
- date format now returns an error if not given an input. Previously it
would default to the current time.
- first and last will now return an error if given a negative index.
Previously the behavior was undefined and may have returned entries
due to an underflow.
- The --predicate flag has been removed from find. where can be used in
all situations where find --predicate was previously used.
- sort-by now requires a column name to sort by. To sort lists without
specifying a column name, sort can be used.
- seq, seq char, and seq date no longer have --separator and --terminator
flags (#7045, #7054, #7096). This helps ensure that the return type for
those commands is consistent, and str join can be used to accomplish the
same effect.
- The build-string command has been removed. To concatenate strings, use
the + operator, string interpolation, or str join.
- wrap now expands ranges. It works the same as with lists or seq.
- url parse url scheme, url host, url path, and url query commands have
been removed. We added the command url parse.
This new command returns a Record with scheme, username, password, host,
path, query, params (as a Record) and fragment.
- sort, sort-by, str contains and find have had their --insensitive flags
renamed to --ignore-case. --ignore-case is used by uniq, as well as
popular external commands like less, grep and wget, so it could be
considered a standard flag name.
- New boolean operator xor - Planned operator simplification
To complement our logical boolean operators and/&& and or/|| we added boolean
xor. This is consistent with bit-and, bit-xor, and bit-or.
We are currently considering to deprecate the C-style symbols &&/|| in favor of
the spelled out and/or to increase consistency and provide more actionable
error messages when trying to use &&/|| in a similar fashion to bash.
- Config options have been grouped together
The structure of $env.config (and thus the record used with let-env config =
statements in config.nu and other places) has been reorganised. Various options
are now grouped into subrecords (similar to table_trim) and had their names
shortened. This allows config.nu files to be better structured, and thus easier
to edit and read, while also allowing future options to be added without making
the,
WARNING
Your existing config.nu options WILL still work in this version!! However,
you will get a warning message if you use the old versions of the options
(as you might already be aware). Support for these old options will be dropped
in a future Nushell update, so take care to convert your config.nu files when
you can.
The changes are:
- use_ls_colors and clickable_links have been moved to into an ls subrecord.
- rm_always_trash has been moved into the rm record. Further rm config
options to accompany it may appear in the future.
- cd_with_abbreviations has been moved into a cd record. Further cd config
options to accompany it may appear in the future.
- history_file_format, sync_history_on_enter and max_history_size have been
moved to a history subrecord.
- filesize_metric and filesize_format have been moved to a filesize
subrecord.
- case_sensitive_completions, quick_completions, partial_completions and
completion_algorithm have been moved into a completions subrecord.
- The completions subrecord also contains an external subrecord.
- enable_external_completion, max_external_completion_results, and
external_completer have been moved into the aforementioned subrecord.
- table_mode, table_index_mode and the table_trim subrecord have been
moved into a table subrecord.
To output your existing options in the above format (that could be pasted into
your config.nu file before you delete the old options), run this code in your
copy of Nushell:
- Minimum Rust version has bumped to 1.65
Due to some breakage in dependencies, we've gone ahead and bumped the required
version of Rust to 1.65, which addresses the issue. Apologies to anyone who is
inconvenienced by the bump. We anticipate returning to the Rust-1 versions in
the future.
shells/nushell: review warning
shells/nushell: add update warning
shells/nushell: update to 0.71.0
- New ++ operator (merelymyself)
In this release, you can now use the ++ operator to append lists together.
For example, you can combine two lists into a new lists made up of the both
lists.
Note: Currently, this operator cannot be used to join two tables. This
functionality is still being worked on and will likely be present in the
next version.
- Improved consistency across commands and types
Nushell continues improve quality of the language and shell with a set of
consistency improvements in this release. These include:
- More iterating filter commands now support the $in variable consistently
(webbedspace)
- Lists now support upsert (fdncred)
- merge can now also operate on records (webbedspace)
- str substring can take ranges (rgwood)
- from and to now show help info (rgwood)
- Right prompts can now be on the last line (nibon7)
Previously the right prompt appeared only on the same line where the user
input started. Now you can choose to place the right prompt part on the last
line of user input. This feature is not enabled by default, you can enable
it using the config nu command to modify the config.nu file, just set
render_right_prompt_on_last_line to true.
- Configuring the default value viewer via display_output hook (perbothner)
You're now able to configure a new hook, called display_output, which will
become the default way that you view data.
Using this, you can for example, use table --expand to always see fully
expanded tables.
If your terminal supports it, you can this to render a more full-featured
output. For example, DomTerm could be used by setting the display_output
hook to: to html --partial --no-color | domterm hcat, sending html to the
terminal to be rendered when displaying values.
- Updated PR Review Process
Recently, we have been fortunate to see a rise in submitted pull requests
and we are super grateful for this growing desire to improve Nushell.
Unfortunately, in some cases, a well-intended PR does not match the
direction Nushell is going, forcing us to close it which leads to wasted
time and effort. To help focus PRs in the future, we kindly ask potential
contributors to first reach out to us before making a substantial change to
Nushell, especially if the change will affect user experience. We updated
our contributing guide as well as the PR template to reflect this policy.
- Completion actions now more familiar (dandavison)
We've also recently improved how completions work in Nushell to feel closer
to how other shells work. Specifically:
- Completion goes "as far as possible". So, the entire word if there's a
unique completion, or else up to the shared prefix of possible
completions.
- Removes the quick completion behavior whereby a word was completed
automatically as soon as the input came to have a unique completion.
- Tab now completes instead of selecting the next menu item (this can be
configured)
- Breaking changes
- New --force (-f) flag for the mv command. This change alters mv default
behavior. By default overwriting existing files is now prevented (You can
use alias mv = mv -f in you config to get the old defaults back). (#6904)
- The column name for the command name in $nu.scope.commands has been
changed from command to name. Thus, $nu.scope.commands | where name =~
zip would give you specific command info. (#7007)
- The str distance command now directly returns an Int instead of a record
{"distance": <Int>} (#6963)
- The argument order of format filesize was made consistent with other
commands that accept a CellPath to specify fields that should be affected
by it. Now the string specifying the format is the first positional
argument and the cell path is specified in the following positional
argument(s). (#6879)
- The --perf flag for Nu was removed as part of an effort to simplify
diagnostics logging #6834
shells/nushell: update to 0.70.0
Themes of this release:
- New table flags
--expand: changes a standard table view; expand the table structure so
internally all data will be displayed as inner tables
- NOTICE
The expand mode can be considered generally slower than a base table view.
So, if you have a large data set it may be slow.
--expand-deep {int}: set a limit after which table enlargement is stopped
--flatten: an --expand view option to return a set of values instead of
table for a simple lists
--flatten-separator {char}: a configuration of a separator for --flatten
--collapse: changes a standard table view; expand the table structure in a
squashed way
- NOTICE
collapse mode currently doesn't support width control, therefore if your
terminal is not wide enough the table might be broken. The collapse mode can
be considered generally slower than a base table view. So, if you have a
large data set it may be slow.
- Breaking changes
The command first 1 now returns a list with the single value rather than the
value itself. This brings it in line with the behaviour of last 1.
The dataframe command with-sql or query dfr has been renamed to query df for
consistency.
- Next Steps
We're continuing to work on language updates and hope to have more
information for you soon.
shells/nushell: update to 0.69.1
Today, we're releasing version 0.69 of Nu.
Note: this release is officially 0.69.1 because of a last-minute issue that was
found and fixed.
As part of this release, we also publish a set of optional plugins you can
install and use with Nu.
Themes of this release
Finishing the rework of modules and environment (WindSoilder, kubouch)
If you followed the development since the last release, you might have noticed
we successfully applied "the method of dead ends" pioneered by Jára Cimrman
"Somebody had to probe this dead end of human knowledge and announce to the
world: Not this way, friends!"
In short, the source-env experiment did not work out as planned. We hoped to
allow to call source-env with dynamic paths which, however, proved unfeasible.
Therefore, in this release, we remove all notions of source-env from Nushell
and instead use will be used activate the module's environment.
Any call to use will run the module's export-env { ... } block (if there is one)
and keep its environment. A positive side of it is that one call of use is
enough to import both commands/aliases and the environment, there is no need to
call two separate commands as we planned for source-env.
We're also keeping the source command for now, as well as the current config
file format. One reason is that we want to first investigate whether it is
possible to export also regular variables from modules and whether we can use
the module keyword inside modules. However, the use of modules is still
preferred over source as it will become the default way in the future.
Upcoming virtualenv activation changes (kubouch)
To reflect the recent changes to the module environment, we are changing the
virtualenv integration to use overlays. This will come in effect as soon as
this PR
gets merged. In practice, this means that instead of source activate.nu, you'll
use overlay use activate.nu, deactivate will work the same.
Under the hood, calling overlay use activate.nu will activate the activate
overlay and deactivate is just an alias for calling overlay hide activate.
If you wish, you can manually name the overlay, for example overlay use
activate.nu as spam, but then you'd need to remove it with overlay hide spam
instead of deactivate.
Grammar Experiments (JT)
We've recently also started working on some improvements to Nushell's syntax.
While these aren't part of Nushell 0.69, you can try this experimental syntax
in our new grammar
repo. Some experiments we're looking into:
Traditional function definition syntax
def foo(x: int) { ... }
Traditional function call syntax
foo(3)
And much more. We're hoping to talk more about these experiments as they mature.
Breaking changes
We found a regression in the correctness of the -d and -t flags of touch.
To get the release out, we've removed these flags, but hope to replace them
with correct implementations in the future.
We also removed support for duration literals above weeks, including month,
year, and decade literals. These were found to be confusing as it's unclear
what a duration of a month is (30 days? 31 days?)
The str collect command is now str join.
Next Steps
We've been progressing with our design towards 0.80 as outlined in this Notion
page.
Some time was spent trying out possible new syntax directions but we were not
confident to release them yet. In the next release we'll see a removal of
features deprecated in this release and we'll continue to push ahead for
the 0.80.
shells/nushell: update to 0.68.1 This is the 0.68.1 release of Nushell. It is a bugfix release of 0.68. This addresses a bug with blocks and source-env. For convenience, we are providing full builds for Windows, Linux, and macOS. These are the "all extra features" builds, so be sure you have the requirements to enable all capabilities: https://www.nushell.sh/book/installation.html#dependencies With this release, we have also statically linked OpenSSL into the binary to make it easier to use across a larger range of platforms. If you encounter any issue with this, please let us know.
shells/nushell: update to 0.68.0 This is a huge jump over several releases and it's impossible to list changes. Please visit https://www.nushell.sh/blog/ for the details of every release. Be aware that there are lots of changes across all aspects of Nushell. - There's a new engine, new line editor, and new commands. - Configuration files will not work and have to be re-written. - Previous scripts will need to be updated, and you'll need to learn some of the new ways of doing things in Nushell to get back to the same level of comfort. - Several shell improvements and behavior changes. - There's also a new plugin architecture and quite a number of breaking changes after fixing design flaws, cleaned-up the design, and rethought how commands should work. - New additional startup file (env.nu) which, sets up the environment that you'll run Nushell in. As a result, you're able to set up important environment variables like $env.NU_LIB_DIRS before 'config.nu' begins to run. - Deeper integration with SQLite, new completion logic, introduction of overlays, hooks, lazy dataframes, input overloading, input/output type, new variable naming convention ... So, please do read about the changes before.
shells/nushell: reset maintainer The new release of nushell, 0.60.0 has major breaking changes and currently does not build on NetBSD. Making it build again is over my head.
shells/nushell: update to 0.44.0 -Remove unused repo parts (#4271) -Drop with iter range (#4242)
shells/nushell: update to 0.43.0 What's New: -You can now learn about some of the upcoming changes in Nushell by reading the tutor e-q page. It will tell you about some of the new features and breaking changes, as well as link you to the full list of changes. Fixes: -Fix to the sample configuration file -Fix to a crate description -Bump to some dependencies in wasm support -Update to sysinfo support -Fix to build on latest Rust stable + clippy
shells/nushell: update to 0.42.0 What's New Fixes -Can optionally use an insecure SSL cert (nibon7) -Fixed a crash when viewing text files (nibon7) -Build fixed for NetBSD (0323pin) Breaking change -For naming consistency, into column_path is now into column-path
shells/nushell: update to 0.41.0 What's New -Features: -Add -l/--login flag for compat with other shells -Fixes: -save --append will now create a file if missing -Upgraded dependencies -Corrected spelling in crate docs and code docs -Fixed the markup in some of the crate docs -external arguments are now sanitized more -upx/strip has been removed after feedback from users -Clipboard capability via arboard removed -Removed some unnecessary allocation
shells/nushell: update to 0.40.0 Today, we're releasing 0.40 of Nu. This release is includes better table imports and much smaller release size. What's New -Detecting columns (jt) Nushell now supports a new command: detect columns. This command is intended as an easy way to handle tabular data that's written as text. Commands like ps, ls -l, netstat, df, and others commonly output their output as text. With detect columns, you can run the external command, and convert them into Nushell's tabular data format. -Smaller binaries (fdncred) The size of the Nushell release binaries has come up as regular feedback from Nushell users. "Why does the shell have to be so big?" And we've heard you! Today's release now uses a combination of strip and upx to bring considerable savings in binary size. The Linux release (plugins incl.) has dropped from 475mb to 58mb(!!), making it 88% smaller. We're seeing similar improvements in the sizes of the macOS and Windows releases.
shells/nushell: update to 0.39.0 Today, we're releasing 0.39 of Nu. This release is a bugfix release of 0.38. What's New: -History file is now removed when the history is cleared (fdncred) -HTML selector has a regression fixed (lucassmmg) -Unused dependencies were removed (lucassmmg) -Updated clippy warnings were fixed (jt) Engine-q progress You'll notice that this release is pretty light, only a set of fixes on 0.38. his is because our energy is now largely focused on engine-q. We're excited to get this in front of you. Just to tease a little of what will be possible, this week we added support for processing streams in parallel in engine-q using a new par-each command. We'll talk more about this as it develops.
shells/nushell: remove leftover
shells/nushell: remove arch restriction
shells/nushell: update to 0.38.0 Today, we're releasing 0.38 of Nu. This release includes polish to the user interface, improvements to how columns are passed, lots of bug fixes, and updates on the upcoming engine. What's New -Quickly jump to a shell (tw4452852) If you've used shells, you've no doubt used the n and p commands to quickly jump between them. This can be a big time saver when you're working in multiple directories. In this release, we've added a g command that helps you quickly jump to a particular shell. This helps in the cases where you end up with more than two shells open and you already know what shell you want to jump to. Additional improvements -Improvements in updated table cell values -update cells command now can take a list of columns -You can now also pass a list of columns to select -Improvements in how html table scraping works and also -Fix to compiling on nightly -Removed unused deps -Completions now can complete inside of an argument -We now expand tilde when reading plugin directories -We also turn off ansi colors when not in a TTY -Fixed some of the wasm deps -Fixed a leak of a let-binding -Use SIMD-enabled compiler flags -Updated polars dependency to 0.16 -Updates to how path join works -Moved nu-path tests into integration tests -New support for converting to column paths -Cleanup fixes to make tests more resilient -Internal improvement to make working with spans easier -Fix to gitpod -Fix to big int handling in to -Fixed a typo -Fixed some typos in the tutor -Removed the experimental scrolling support as it had broken
shells/nushell: enable nu_plugin_textview This is the last plugin belonging to core. I'll keep testing the other plugins after the freeze.
shells/nushell: enable nu_plugin_inc
shells/nushell: enable nu_plugin_tree
shells/nushell: update to 0.37.0 Today, we're releasing 0.37 of Nu. This release adds a new find function, improvements to the current engine, and updates on the upcoming engine. What's New finding data in tables In 0.37, you now have access to a new find command, which can help you quickly look for data across all columns in a table. You can still reach your system's find command using ^ by typing ^find. Additional improvements -fdncred added more support for ansi art, and more chars -aminya removed shelling out in some cases where it's not needed -jt made sys/ps/fetch/post core commands, moving them from plugins to internal commands. This allows for future capability to have nushell download its own extensions. -andrasio began adding support for creating errors inside of nushell code, extended tags to support basic command reflection -lily-mara added into filesize -tw4452852 added support to append when calling save -Pantoshire improved errors when bash-style alias was mistakingly used -tranzystorek-io did a lot of general code improvements -kubouch did some fixes to paths and the source command -elferherrera updated the prompt environment variable to PROMPT_COMMAND to show that it is nushell code that gets run
shells/nushell: update to 0.36.0 -This release fixes some long-standing issues with history, improves the help system, improves dataframes, and much more.
shells/nushell: update to 0.35.0 -Add the -s parameter to submit package to winget in pipeline (#3767) -corrected position of dataframes (#3776) -fixed show_hints option to allow hints to be turned off (#3780) -Updated polars version for faster CSV reader (#3781) -Fix docs for the config variable completion_type (#3804) -bat theme wasn't getting set properly (#3807) -Dataframe Shape command (#3805) -Support other variables than PATH in pathvar (2nd attempt) (#3828) -change describe so it doesn't output colored strings (#3832) -Read from standard input in rm (#3763) -use chrono_humanize for datetime formatting (#3834) -All is a DataFrame (#3812) -Add sha256 to the hash command (#3836) -added the ability to compare time units like 1hr < 2hr (#3845) -Update implementing_a_command.md (#3848) -Improve md5 and sha256 code (#3841) -Fix clippy lint and disable broken lint (#3865) -document compiling without openssl (#3862) -Add named positionals to all (#3863) -add performance metrics for measuring startup time (#3854) -fix interpolated strings when using unicode (#3866) -Support equals sign in shorthand environment variable values (#3869) -simple contains arguments (#3874) -Better representation in nested dataframes (#3875)
shells/nushell: simplify Makefile
g/c RUSTFLAGS from individual package Makefiles. Handled by cargo.mk.
shells/nushell: import package Hello, and welcome to the Nushell project. The goal of this project is to take the Unix philosophy of shells, where pipes connect simple commands together, and bring it to the modern style of development. Nu takes cues from a lot of familiar territory: traditional shells like bash, advanced shells like PowerShell, functional programming, systems programming, and more. But rather than trying to be the jack of all trades, Nu focuses its energy on doing a few things well: -Create a flexible cross-platform shell with a modern feel -Allow you to mix and match commandline applications with a shell that understands the structure of your data -Have the level of UX polish that modern CLI apps provide The easiest way to see what Nu can do is to start with some examples, so let's dive in, https://www.nushell.sh/book/