Trouble with gptel-post-response-functions hook

[Hamzehn]

Please update gptel first -- errors are often fixed by the time they're reported.

• I have updated gptel to the latest commit and tested that the issue still exists

Bug Description

I'm seeing the behavior below on versions 0.9.9 (latest package available in Doom Emacs) and 0.9.9.3 (installed manually using package-install):

I added the two recommended hooks in my config:

(add-hook 'gptel-post-stream-hook 'gptel-auto-scroll)
(add-hook 'gptel-post-response-functions 'gptel-end-of-response)

The issue I'm seeing is that when I do gptel-send, the cursor is moved to the end of the response instead of the placeholder for the next prompt. If instead of using the hook I call the gptel-end-of-response function manually, it moves to the correct location (after the three ###).

Backend

None

Steps to Reproduce

1. Add gptel-end-of-response to the gptel-post-response-functions hook like this in the config file:

(add-hook 'gptel-post-response-functions 'gptel-end-of-response)

2. Open a GPTel window to use an LLM (e.g. ChatGPT) and type a prompt and hit C-c RET (or gptel-send).
3. The cursor will not move to the next prompt and instead will move to the end of the response text.

Additional Context

Doom Emacs (Emacs 30)
Running on Ubuntu (WSL2)

Backtrace

Log Information

[karthink]

Thanks for the report. I've fixed this locally but it involved some deeper changes in gptel so I'm going to test this for a few days before pushing it to GitHub.

[KaratasFurkan]

I also realized that when using a model with reasoning, the cursor ends up at the reasoning block instead of the end of response. Works fine when called through M-x gptel-end-of-response, FYI.

[karthink]

@Hamzehn I have pushed the fixes, please update gptel and test.

@KaratasFurkan It should actually have failed both interactively and in the post-response hook, I don't know why it was working correctly when called interactively. After the fixes I've pushed, gptel-end-of-response should work correctly when called from gptel-post-response-functions. It will still fail when called interactively in the presence of reasoning blocks, but since it somehow worked for you before I expect it'll continue to work for you.