scarf
scarf
> [jorgebucaran/nvm.fish#nvm_default_version](https://github.com/jorgebucaran/nvm.fish?rgh-link-date=2025-05-21T03%3A46%3A44.000Z#nvm_default_version) with these there's no need for `nvm alias default`. > > Look here: [#241 (comment)](https://github.com/jorgebucaran/nvm.fish/issues/241#issuecomment-2733129862) then `nvm alias default` could run `set --universal nvm_default_version`
I'm also interested in this.
yes, it still happens when i reload the window.
another approach: add an option `includePath: boolean` to config object in `parse` and `safeParse`. this way we can alter the message without causing breaking changes.
I suggest to re-open the issue, as this issue still persists: ``` (100 more above) ~/.config/fish/completions/poetry.fish (line 223): complete -c poetry -A -n '__fish_seen_subcommand_from 'source add'' -l default -d 'Set...
> How would that be different from `JSON.stringify()`? for starters it would support trailing commas (should be made an option): ```ts const foo = { a: 1, b: 2 }...
nope, could i get pointers on where to look?
I think the current behavior should be considered a bug. it's counterintuitive that `--ref` defaults to `main` when i'm on a `foo` branch.
> Can you pls provide a screenshot of the confirmation dialog you're seeing? when the popup appears, and i click it, to get focus into vscode, it's always auto-accepted. so...