karthink

> Keep the current single-context mechanism exactly as is > Add ability to: > > - Save current context with a name > - Switch to a previously saved context...

> I agree. The need for a context buffer, that shows all the context regions together, even if enhanced to be collapsible like Magit does, does not make as much...

> One quick question for the mean time, though. > > What is the best way to ignore context in one-off requests? > > This is especially important for privacy...

Thanks. When I try using the dispatch keys I get ``` Error during redisplay: (eval (tab-line-format)) signaled (wrong-type-argument stringp nil) [14 times] ```

> gptel should probably produce a better error message in this case, as this happens despite providing instructions with -d. What should the error message be? Note that the contents...

The user prompt is allowed to be empty by other models/backends.

> Yeah, I think gptel-menu currently funnels people into -d via the double "instructions" phrasing. Certainly that happened for me, as my goal was indeed to generate some code based...

> I think it's good for gptel to support a prompt-based workflow to funnel people into a way to write instructions, and imo that way should ideally work always and...

Here is a patch for solution 1 that does _not_ account for the edge cases. You can try it out and let me know. (Use the "d" option in an...

I've added initial support for presets on the `feature-presets` branch. You can select a preset from the transient menu after defining it.  You can use the `= Scope` option...