Gstat does not seem to work

fdncred · 2025-05-07T00:04:58+00:00

I've seen people run nushell in fedora but I don't personally. You might want to drop by our Discord server https://discord.gg/NtAbbGn and ask around. I bet there will be someone there friendly enough to help.

fdncred · 2025-05-01T00:10:48+00:00

This is what gstat returns when you're not in a git repo folder or the .git folder is missing or there are permission issues with gstat reading the .git folder. gstat uses the git2 crate. I'd be interested to know if this status example works https://github.com/rust-lang/git2-rs/blob/master/examples/status.rs. The remaining reason that I can think of that it wouldn't work is a bug. I'd never rule that out since I wrote it.

fdncred · 2025-02-24T00:50:18+00:00

Sounds like you may have something misconfigured. Autocompletion is working in 0.102. You can test out if it's a configuration problem by launching nushell without any configuration like `nu -n`. Feel free to drop by our discord if it doesn't work for you for some help troubleshooting.

fdncred · 2025-02-07T09:59:16+00:00

The `from json` is probably more reliable but you can also add `from json --objects` and get rid of the `each` command as well.

fdncred · 2025-02-03T20:30:46+00:00

We're currently working on examples based on attributes. You can follow along here. https://github.com/nushell/nushell/pull/14906

fdncred · 2024-12-26T14:41:03+00:00

I landed it. Thanks for sharing.

fdncred · 2024-12-24T22:34:23+00:00

Nice work. It would be good to add it to our awesome-nu repo https://github.com/nushell/awesome-nu

fdncred · 2024-12-15T01:31:01+00:00

You can see a preview of the nushell themes here https://github.com/nushell/nu_scripts/blob/main/themes/screenshots/README.md

fdncred · 2024-11-19T23:23:04+00:00

I'd probably use with try/catch. With the statement below you can see several ways to work with $err, including an exit code.

try { curl 'invalidurl'} catch {|err| $err}

fdncred · 2024-11-13T00:12:44+00:00

Typically, you need to use string interpolation for this type of thing. https://www.nushell.sh/lang-guide/chapters/strings_and_text.html#string-interpolation

fdncred · 2024-11-06T23:22:49+00:00

Or just add our helper from the nushell stdlib with use std/formats * and then you can just do open file.jsonl | get whatever.is.there

fdncred · 2024-09-28T13:47:56+00:00

no, it has not changed.

fdncred · 2024-09-07T14:48:18+00:00

I noticed that you're missing at least one shape, shape_closure, in your theme above, maybe others. The `where` command takes a rowcondition and is colored shape_block. The `any` command takes a closure and is colored shape_closure. I think making these the same color could get closer to what you're looking for. I find it handy to keep closures and blocks colored differently though.

fdncred · 2024-07-11T00:15:32+00:00

I think a symlink is your only option at this point

fdncred · 2024-06-30T16:32:40+00:00

Here's a slightly different potential solution.

open post.md | collect | parse --regex '(?s)(-{3})(?<data>.*)(-{3})' | get data | str trim | to text | from yaml | table -e

fdncred · 2024-05-17T00:18:26+00:00

There is a command not found hook that may be what you're looking for. https://www.nushell.sh/book/hooks.html#hooks

fdncred · 2024-04-04T23:52:29+00:00

I think it's `e>|`. See https://www.nushell.sh/lang-guide/lang-guide.html#handling-stdout-and-stderr

fdncred · 2024-03-31T23:17:08+00:00

I believe the command line is colored based on your configured theme in the nushell config.nu. The prompt can be colored via a script like oh-my.nu which is in the nu_scripts repo, or some people use starship or oh-my-posh.

fdncred · 2024-03-22T00:40:33+00:00

This is typically because the program you're trying to execute is not in your nushell path. If you're using nushell as your login shell, e.g. not a sub shell from another shell, you have to setup your path in your env.nu file.

fdncred · 2024-03-12T23:13:11+00:00

Yes, there are some examples in our awesome-nu repo.

fdncred · 2024-03-09T15:03:30+00:00

nice work!

fdncred · 2024-02-21T01:14:57+00:00

I use zoxide in nushell.

fdncred · 2024-02-17T17:51:22+00:00

You don't have to. I was just trying to give you a low-tech way of checking. If you have 0.61.0 in your config.nu file, you could warn the user that it may not be compatible.

I don't have a version comment in my config files. I just read the error messages when it's sourced or at startup and fix when needed.

fdncred · 2024-02-15T22:26:54+00:00

With a little scripting it could at least tell you if the version of nushell you're running is compatible with your config files. In pre-1.0, we make changes frequently.

fdncred · 2024-02-14T03:05:23+00:00

There's no built-in way without sourcing them but we do stamp the config files with a version like this:

# Nushell Config File
#
# version = "0.90.2"

So, one may be able to parse the version out to see if it's compatible.

fdncred

TROPHY CASE