shell_gpt VS fnm

https://github.com/TheR1D/shell_gpt?tab=readme-ov-file#shell...

I would like to stay in the terminal, and am using https://github.com/TheR1D/shell_gpt, my format is simply to send GPT a file to discuss:

ShellGPT https://github.com/TheR1D/shell_gpt does pretty well for a lot of use cases. I mostly use it in REPL mode, switching topics as needed. I have wrappers around the `sgpt` command to, say, start a REPL with a particular topic, say, Python, which loads my previous history on that topic as part of the prompt.

I also have an alias to save existing chats as text files so I can go back and review history.

Finally, there is an alias to load a question up in an editor if I need to enter multiline text, e.g. to discuss code fragments, etc.

I expect command-line workflows to be pretty individualized and I'm curious what others do. For me (old programmer), using a command line REPL feels much more natural (and blissfully noise-free) than going to a Web page to talk to, say, ChatGPT.

The API still works. I've been using https://github.com/TheR1D/shell_gpt/ in my workflow.

I recommend shell-gpt[1] for anyone with access to the OpenAI API. It works surprisingly well considering how simple it is. Be sure to browse the examples in the README.

[1] https://github.com/TheR1D/shell_gpt

Nice idea. You may want to mention in the docs that it requires https://github.com/TheR1D/shell_gpt ;)

I honestly bought the device just to play with the wearable version of my android app: a voice controlled ssh client that let me also pass voice input to shell_gpt. Other pre installed apps won't really work on this device, including google assistant, so I had to switch to google cloud speech to text APIs for speech recognition. I can still sideload compatible apps via bluetooth debugging tho

Maybe this can help : https://github.com/TheR1D/shell_gpt

I'm not really following these but they tend to get released every other day, like https://github.com/nlml/YoCLI/ and https://github.com/TheR1D/shell_gpt

Install nodejs: (I highly recommend using a node version manager like fnm) and to install a recent node version (current long term support is 16+)

I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.

I switched from nvm to fnm a few years ago and have never looked back. Zero performance issues and it supports .nvmrc files.

https://github.com/Schniz/fnm

Are you using some kind of node version manager like fnm?

If it's your terminal that's slow in general and not neovim specifically I found that switching from nvm to fnm for managing node significantly faster at starting up my shell. I don't know whether this is what your issue is but I thought I'd share it regardless. https://github.com/Schniz/fnm

fnm is a fast and simple Node.js version manager. It's really easy to use and is much faster than nvm.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

Install something like Fast Node Manager from https://github.com/Schniz/fnm and install your Node from there. I work in the software field and tend to use the LTS releases for the TypeScript/React projects I work on.

fnm!

You’ll need pnpm and Node.js installed on your machine + some tool for switching node versions (e.g. fnm or nvm will work fine);