❯ let before = (sys).mem.used
❯ $before
9,382,694,912
❯ mut csv = open ~\OneDrive\vdi\DBScripts\Output\violations-20220731-20230801.csv
❯ $csv | length
1046339| # emulate the python rich print | |
| # test case 1: pr "hello world" | |
| # test case 2: pr "hello world" --style bold | |
| # test case 3: pr "hello world" --style 'bold underline' | |
| # test case 4: pr "hello world" --style 'dim italic red' | |
| def pr [ | |
| msg, | |
| --style: string, | |
| ] { | |
| let style = if $style == null { |
default_config.nuanddefault_env.nurefer to the files that are compiled inside of the nushell executable and are also located in our repo.personal env.nu/config.nu/login.nurefer to the files that are in the$nu.default-config-dirthat you have personally edited.specified config.nu/env.nurefer to files that are specified on the command line with the--configand--env-configcommand line parameters.
- ✅ Always reads the nushell standard library
- ✅ Always reads
personal plugin.msgpackzfile if it exists
OSC 4 ; -2; ? ST //bg
OSC 4 ; -1 ; ? ST //fg
OSC 4 ; -2 ; rgb : [red] / [green] / [blue] ST
OSC 4 ; -1 ; rgb : [red] / [green] / [blue] ST
OSC 6 ; 1 ; bg ; red ; brightness ; [N] ST
OSC 6 ; 1 ; bg ; green ; brightness ; [N] ST
OSC 6 ; 1 ; bg ; blue ; brightness ; [N] ST
| # Language support configuration. | |
| # See the languages documentation: https://docs.helix-editor.com/master/languages.html | |
| [language-server] | |
| awk-language-server = { command = "awk-language-server" } | |
| bash-language-server = { command = "bash-language-server", args = ["start"] } | |
| bass = { command = "bass", args = ["--lsp"] } | |
| bicep-langserver = { command = "bicep-langserver" } | |
| bufls = { command = "bufls", args = ["serve"] } |
Originally when I wrote the $db PR, I went in knowing that other commands would be needed. The concept is to have an in-memory sqlite database available to you at any time to store anything you want. I just chose $db because it was very nushell-y and easily accessible.
An alternative that I came up with was to have a command named stor with subcommands. stor without and e because you don't get groceries from it. :) We can name it whatever, but for now, it's stor. The idea behind the stor family of commands is that they provide a way to interact with the in-memory database.
The `input_output_types`` are parsed from top to bottom instead of matching on the appropriate ones. This makes some thing fail because the first one succeeds gets output versus the right one.
Example:
❯ http get https://index.crates.io/ba/se/base64 | lines | last | from json
Error: nu::parser::input_type_mismatch