karthink

Talk about timing, I fixed this 10 minutes ago.

Also it doesn't cause any bugs in gptel's request, since this clean-up is done before the request is constructed. It's only the visual indicators (in the transient menu and now...

> I'm on the latest master and I'm still getting it. https://github.com/karthink/gptel/blob/master/gptel-context.el#L169

> So, outside of commandeering the default string generation functions, is there any risk of the alist being polluted? What do you mean by polluted?

> > I'm on the latest master and I'm still getting it. > > https://github.com/karthink/gptel/blob/master/gptel-context.el#L169 This fix is incomplete, I guess I need this check in other places in this...

> In such a case executing (gptel-context--string gptel-context--alist) results in an error. Ah, this is what you meant by "commandeering the string generation". I'll fix it, but it's a low...

@hrehfeld thanks for the PR. While I'm okay with placing these in a variable, you can achieve the effect you want more easily via ```emacs-lisp (setq org-use-property-inheritance "^GPTEL_") ``` Any...

@hrehfeld You're right, this function combines property names with separate logic for handling each corresponding property value. So adding or removing topics from the defconst won't be enough, you'll also...

> So we'd actually need another defconst just for that destructure, or hardcode it anyways and just ADD the constant. Or just give up on this? I'm leaning towards closing...

This restriction doesn't make sense to me. gptel is intended to be used freely in any buffer in Emacs. - If you are unsure about what will be sent, you...