more typos and spelling.

This commit is contained in:
Gabe Venberg 2024-07-30 23:58:49 -05:00
parent 6b72cc3812
commit e7d4442af6
8 changed files with 39 additions and 40 deletions

View file

@ -44,7 +44,7 @@ Individual entries can be one of several built in datatypes,
including rich datatypes like datetimes, durations, and filesizes.
Nushell can also open many filetypes and turn them into nushell native datastructures to work with,
including csv's, json, toml, yaml, xml, sqlite files, and even excel and libreoffice calc spreadsheets.
including csv, json, toml, yaml, xml, sqlite files, and even excel and libreoffice calc spreadsheets.
Once you have your data in nushell datastructures,
you can do all sorts of manipulations on it.
@ -120,7 +120,6 @@ update time {into datetime -f '%d/%b/%Y:%T %z'} |
# parse into proper integer
update bytes_sent {into int}
{{</highlight>}}
(each line has a comment explaining what it does, for those unfamiliar with the nushell language)
Now that we have it in nushell tables, we can bring all of nushells tools to bear on the data.
For example, we could plot a histogram of the most common ips, just by piping the whole thing into `histogram ip`.
@ -156,7 +155,7 @@ You can optionally give the arguments a type
{{<highlight sh>}}
def recently-modified [cutoff: string] {
# show all files recursively that were modified after a specified cutoff
# show all files recurisively that were modified after a specified cutoff
# show all files recursively that were modified after a specified cutoff
ls **/* | where modified > (
# create timestamp from input
$cutoff | into datetime