@jntrnr "Finally, a command
line shell for the 90s" is irony! It is a joke to emphasize that shells like Bash are too old and #FishShell has modern features.

Indeed, the first release of Fish was 2005.

@gim I have not seen a more pleasant interactive experience like #fishshell provides (and not just great completion system), at least not without any configuration at all, and the language is a step forward compared to posix shells (more consistent, more clean)

@victorhck Este tema de configuración de emuladores de terminal básicos sigue siendo misterioso.

En mi caso, me gustaría saber cómo configurar los emuladores VTn (los que se accede mediante ctrl-alt-Fn). Cuando uso un gestor de terminal sofisticado como #fishshell, con prompts complejos (en mi caso "tide"), entonces en las VTn se ve bastante mal.

Creo que el "truecolor" no es configurable, pero la fuente de caracteres sí debería serlo.

¿Sabes cómo podría hacerlo?

Wild idea...
Replacing my #fishshell setup with #oilshell + #carapace 🤔

@swflint Thanks. #StarshipPrompt doesn't seem to notice this shell change though, while it does for 'nix-shell -p git-extras --run fish'. Shouldn't be a :fish_shell: #fishShell issue though.

UPDATE: nix-shell sets the IN_NIX_SHELL=[im]pure environment variable (and a whole bunch of others) while nix shell only touches the PATH. Hard to detect for any program that this change happened!

There is an alias for bash to use cheat.sh and receive the cheatsheet for a command while inside your terminal.

For fish users use function:

function h
curl -s -L cheat.sh/$argv | less -R
end

Then type: function h cat

You will get the cheatsheet to cat within your terminal session.
#terminal #fishshell #linux

Does anyone know if there's a way in #FishShell to have text printed via STDOUT colored differently? Or maybe a way in #iterm2 or Kitty ?

(I've been pondering switching to Kitty, but don't want to deal with configuring everything.)

#fishshell rewrite-it-in #rust progress, 2023-08-14

48025 rust lines added
23299 / 77063 C++ lines removed
▓▓▓▓▓▓░░░░░░░░░░░░░░ 30 %

#riir #rustlang

--

The path and functions builtins have been ported, as well as some of the spawn machinery and the last pieces of the killring.

Overall I'm really happy after moving to #fishshell. The one thing I miss from #zsh is zmv. What approach do people use for zmv-like batch renaming in fish?

#fishshell rewrite-it-in #rust progress, 2023-08-07

46458 rust lines added
21679 / 77063 C++ lines removed
▓▓▓▓▓░░░░░░░░░░░░░░░ 28 %

#riir #rustlang

--

Not a lot of movement this week, with some of our committers on break. Personally, I decided it is more important (but less interesting) for me to work on getting a release of the old codebase out than porting little builtins.

Ok, I have to say, the difference in speed moving from #zsh to #fishshell is really noticeable. I now regret putting this off for so long.

#TIL : #fishshell #argparse

"
This command makes it easy for fish scripts and functions to handle arguments.
"

Example from docs:
```
function mybetterfunction
argparse h/help s/second -- $argv
or return

if set -ql _flag_help
echo "mybetterfunction [-h|--help] [-s|--second] [ARGUMENT ...]"
return 0
end

if set -ql _flag_second
echo $argv[2]
else
echo $argv[1]
echo $argv[3]
end
end
```

https://fishshell.com/docs/current/cmds/argparse.html

Porting a corner of the #fishshell codebase to #rust has identified one five-year-old mistake and an effectively-unused codepath.

Has anybody an alternative for managing ssh keys to #keychain. Program is killing me in conjunction with #fishshell.

#fishshell rewrite-it-in #rust progress, 2023-07-31

46368 rust lines added
21685 / 77063 C++ lines removed
▓▓▓▓▓░░░░░░░░░░░░░░░ 28 %

#riir #rustlang

--

The string builtin port has been merged, which has seen the removal of a lot of C++. There's PRs in for another few builtins but no review as yet. There's work being done on the port of the parser but there's a huge chunk of interlinked code.

I think the string builtin is interesting when you look at fish's history. Under the 1.x design goals it would never have been added - there's already enough string manipulation tools in the standard Unix toolkit. Under the newer guidelines, there's clearly a place for a unified command with consistent UI and the improved performance in loops that comes from builtins.

Anybody experience with dotfile manager like #chezmoi and #fishshell? Which files/directories should I exclude from syncing across machines?

@zanchey

How does the code-base continue working if you progressively replace C++ with Rust? Are you going class-by-class, module-by-module and have some inter-language communication? Or are these separate services? Is there more information about this process?

#CPP #Rust #Rustlang #opensource #FishShell #riir #development

#fishshell rewrite-it-in #rust progress, 2023-07-24

43444 rust lines added
18729 / 77063 C++ lines removed
▓▓▓▓░░░░░░░░░░░░░░░░ 24 %

#riir #rustlang

--

The function module and its accompanying builtin have been ported. The string builtin PR edges ever closer to being merged (and currently removes nearly 3000 lines of C++).

fish shell 很奇怪。写

while true; read v ; echo $v ; end

发现没办法用ctrl-c 终止。

#fishshell #shell

#fishshell rewrite-it-in #rust progress, 2023-07-17

42206 rust lines added
17911 / 77063 C++ lines removed
▓▓▓▓░░░░░░░░░░░░░░░░ 23 %

#riir #rustlang

--

No new areas ported this week but some refactoring and cleanup, including some unused C++. Any claims that I went looking for unused C++ just to enlarge my progress bar are unfounded.