Gabe/techWebsite
1
0
Fork 0
Code Issues 8 Pull requests Projects 1 Releases Wiki Activity

typos and spelling.

Browse source
This commit is contained in:
Gabe Venberg 2024-07-29 17:57:54 -05:00
parent fb44be7ee5
commit 3d4349710b
8 changed files with 48 additions and 47 deletions
Download patch file Download diff file Expand all files Collapse all files

12
content/posts/nushell.md
View file

@ -3,7 +3,7 @@ title = "Nushell first impressions"
date = 2024-03-01T11:34:04-06:00
+++
Ive been experimenting with the tools I use on a regular basis lately -- switching
I've been experimenting with the tools I use on a regular basis lately -- switching
up my shell, terminal multiplexer, and even trying out other editors.
Today, Id like to focus on my experiments with my shell.
@ -32,7 +32,7 @@ give myself enough time to really use it,
see not only how it felt with ordinary usage,
but to give myself time and opportunity to construct a few pipelines and scripts in it.
All that said, the month is up, and Ive been collecting examples,
All that said, the month is up, and I've been collecting examples,
thoughts, and some criticisms along the way.
## Piping structured data
@ -69,7 +69,7 @@ ls **/* | where modified > (
ps |
# convert the name of the called process into a path
update name {|process| (which $process.name).path.0?} |
# join with the list of all files in the current directory, recursing down subdirectories.
# join with the list of all files in the current directory, recurring down subdirectories.
join (ls -f **/*) name
{{</highlight>}}
@ -93,7 +93,7 @@ explanatory comments.
## Parsing non-nu tools
But what if our tool/text file isnt in a format nushell understands?
But what if our tool/text file isn't in a format nushell understands?
Thankfully, for most formats parsing is relatively straightforward.
Lets take this NGINX server log, for example (not a log of real traffic, just a
sample log I found)
@ -330,7 +330,7 @@ invoking them from within nu treats them as external commands,
meaning they take in and pass out plain text,
rather than the structured data that you would get with a proper custom command
or nu builtin.
The best workaround Ive found so far is instead of making scripts that you run
The best workaround I've found so far is instead of making scripts that you run
directly, you define a custom command in the script file, `use` that file, and
then run the custom command, like this:
@ -362,6 +362,6 @@ but seems to be the best way at the moment to make 'scripts' that are integrated
## So, overall, is it worth it?
Nushell is certainly an promising project, and I will almost certainly be continuing to use it as my daily shell.
It cant do everything, but dropping into zsh for a task or two every once in a while isnt that big a deal for me,
It cant do everything, but dropping into zsh for a task or two every once in a while isn't that big a deal for me,
and having access to such a powerful shell by default has made other tasks much easier.
If you regularly use pipelines in your default shell, consider giving Nushell a try.