shell-bling-ubuntu VS etc

Personally, I only really got into working at the shell once I started exploring all of the wonderful new programs that people have been writing to make it easy as pie to work with. I ended up collecting them all together into scripts I can `curl | bash` on any new Ubuntu machine: https://github.com/hiAndrewQuinn/shell-bling-ubuntu

Obviously these scripts won't work on Mac. But I do list the programs I install in it right in the README, including what I consider the "Holy Trinity": `rg` (really fast line searching), `fd` (really fast file finding), and `fzf` (best described with examples: see https://andrew-quinn.me/fzf). These all work on my wife's Mac identically to how they work on my own Linux box, and they make the experience of working at a shell much more pleasant.

Finally, install fish! https://mmazzarolo.com/blog/2023-11-16-my-fish-shell-setup-o... You can get back to Bash once you've gotten used to using the shell and find a reason to. Fish is much more pleasant, IMO, and I try to use it wherever I can these days.

Yes! This is why I pair the two up in https://github.com/hiAndrewQuinn/shell-bling-ubuntu.

These context clues are especially important for newcomers to the command line. A CLI newbie who sticks with it might eventually progress to the point where they decide to ditch Starship, or to ditch fish, or to ditch both, but until they get to that point, the solid defaults and OOTB features of these two have a lot going for them.

Alternatively, if you simply wish to occasionally bring Copilot into your shell, you should know that Ctrl+X Ctrl+E (on bash) / Alt+E (on fish) will open your current shell line up in $EDITOR, which you may set to Vim or Neovim.

From there, :wq will drop the text back into your command line. If you have Copilot set up in either of those, then it will also work here.

I know from working on https://github.com/hiAndrewQuinn/shell-bling-ubuntu that Neovim's LazyVim setup now supports Copilot out of the box now. I never had much trouble setting up the Vim plugin either. YMMV.

https://lnav.org/ has a feature that single handedly sold me on trying out the fantastic software: An SSH-reachable playground. It's right there above the fold on the first page: ssh://[email protected]

I want to build a similar playground for people who want to get familiar with the tools my Shell Bling Ubuntu repo provides ( https://github.com/hiAndrewQuinn/shell-bling-ubuntu ). Ideally it consists of a series of very simple tasks to get one's feet wet with each tool provided: Using fish's autocompletion, then using fzf's shell keybindings, then using rg instead of grep to search an enormous number of files for a single needle character in a million lines of wheat , and so on.

I have no clue how to do this safely. I've never seen how anyone else does it either. Can anyone provide me some pointers?

Alternatively, if you just want to integrate Copilot into Neovim and get on with your day, I recently discovered that the latest LazyVim integrates it as an extra.

I actually discovered this while working on Shell Bling Ubuntu, which is a couple of easy scripts to get you a bunch of modern command line tools nice and configured in one go, but you can just scroll down to "Add Copilot to Neovim" to see. It's refreshingly user friendly for NV configs.

https://github.com/hiAndrewQuinn/shell-bling-ubuntu

Since this is now a share your prompt thread, here's mine:

https://github.com/rollcat/etc/tree/master/cmd/prompter

It's quite portable (didn't test on Windows though); ~170 lines of Go; no dependencies outside of stdlib; calls no external commands; supports SSH, git, Docker, nix, and virtualenv; extremely simple to hack on.

It's fairly easy to grab info from .git for your own purposes. For example, the program that generates my PS1 peeks there (without wasting precious cycles on shelling out to the git command) to find the current branch we're on:

https://github.com/rollcat/etc/blob/b2fd739/cmd/prompter/mai...

Depends on what you're trying to do. If you're shelling out to git(1) or docker(1), rather than e.g. recursively checking for the presence of .git in parent directories, or inspecting ~/.docker/config.json, then the fork+exec overhead is already quite significant. Next if you're parsing ~/.docker/config.json in shell, you're most likely either asking for trouble or (again) shelling out to jq. Writing it all in an interpreted language means you're paying the cost of interpreter startup, which on underpowered systems can take hundreds of milliseconds even when idle. OTOH loading a static binary to memory happens only once, and with Go you can trivially cross-compile.

I also have a fallback shell one-liner, without any of the fanciness like displaying the current git branch:

https://github.com/rollcat/etc/tree/master/cmd/prompter#i-li...