ata VS gpt-generated-commit-messa

> My main gripe with it though is that the actual interface is quite limited, and I don't like having to navigate to the site every time I want to use it.

https://github.com/rikhuijzer/ata. Written in Rust. Does streaming responses and supports Emacs keyboard shortcuts. That's it. All that's needed for quickly looking up things.

- Checkout definitions. I have a small tool (https://github.com/rikhuijzer/ata) available on a keyboard shortcut and use it to quickly checkout definitions for words when I come across a word that I don't know.

As a little side-note, it actually involved some hacking to get the output printing correct because it appeared that the API sometimes responds denotes a newline by two tokens (["\", "n"]) and sometimes by one token (["\n"]). In the playground (https://platform.openai.com/playground), they convert the two token version to a single token, so that's what ata does too (details in https://github.com/rikhuijzer/ata/pull/6). My guess is that this is basically a bug in the model which they manually fixed in the Playground and ChatGPT front ends.

ChatGPT made my work more productive, but I was having a bit of a struggle with the browser, timeouts and slow responses, and the lack of keyboard shortcuts. That's why I made a terminal application: https://github.com/rikhuijzer/ata. You can download it for free in the releases section or build it yourself from source. I'm using it daily and hope it is useful for people here too

The past week I used GPT for about 80% of my commit messages. I put it in a terminal command so all I type is 'commit' and that's equivalent to: git add . && git commit -m "message" && git push.

The message is generated automatically via the GPT API.

I made it public in case anyone else wants to try/use/fork it:

https://github.com/stevecondylios/gpt-generated-commit-messa...

It's very convenient for README and docs changes; small changes whose commit message really doesn't matter.