karthink

@dojt and @Esnos33, does the Curl command in your log work if you run it at the command line?

PR #456 recently addressed some gptel issues with Windows + Curl. Could someone experiencing this problem try it with the latest gptel commit?

> @karthink I just upgraded and now its working! I'm on linux, so I don't know if pr 456 resolved this issue If you're on Linux, PR #456 is not...

See #317 and #301

Yup, I think that's too hacky. Technically you want ```elisp (equal transient-display-buffer-action (apply #'eval (get 'transient-display-buffer-action 'standard-value))) ``` but this is the kind of "fix" that feels mighty clever in...

> Isn't this just a fancy way of saying `(default-value 'transient-display-buffer-action)` No, these are completely different things. `default-value` returns the global value of buffer-local variables. > But what if tarsius...

Wow, thanks for the comprehensive investigation. I'll test when I can. gptel currently requires a minimum transient version of 0.7.4, so we don't need to worry about the peculiarities/bugs in...

> I'd say the sensible thing is to hard code the width of the system message to be roughly the same as the transient is at the default state If...

> window-width is still wrong in terminal mode, window-max-per-chars-per-line should be used at lest. It doesn't make a difference since we don't use `window-width`, but some number less than that...

Coincidentally, I pushed a read-only behavior change a short while before I saw this PR. There will be a merge conflict. > * gptel.el (gptel-read-only-response-buffer, gptel--handle-pre-insert): Introduce a new defcustom...