Just an idea

[randomwangran]

gptel/gptel.el

Line 376 in e61180e

;; TODO: Handle multiple requests(#15). (Only one request from one buffer at a time?)

If TODO -> DONE, things like sectional suggestions can be achieved:

https://youtu.be/MpK9PWo0lUw?t=115

[randomwangran]

#15 related

[karthink]

https://youtu.be/MpK9PWo0lUw?t=115

I'm not sure how this feature connects with the TODO item the code. Could you explain in a little more detail?

[psionic-k]

Fundamentally, since we can only edit on one dimension of a request at a time, I think what they mean is to map the user's command over either a list of data or using a list of contexts, prompts, or other request dimensions.

Multiple requests only makes sense when the things being mapped over do not provide context to each other or the goal is to eliminate context leakage from item to item. If the structure of output is difficult to generate correctly, that's another possibility.

If anything is needed, it's probably just the infrastructure to support multiple simultaneous requests. A plural API would be convenient, but really just front-loading some of the plumbing that users can / should do on their own.

[karthink]

If anything is needed, it's probably just the infrastructure to support multiple simultaneous requests.

gptel does not currently enforce any limit on the number of simultaneous requests (in a single buffer or across buffers), so you can fire off as many as you want. I often have 2 requests going at once.

• What is a "plural API"?
• By "infrastructure" do you mean a UI?

[psionic-k]

infrastructure: the Open AI API calling implementation code. (I didn't look at it yet)
plural API: one that handles lists of things instead of a thing