karthink

> Now, with tools, I see these things in my interactions often: That makes sense. I'm assuming from your description that in your branch (where you include the full path...

> On a related note regarding a different kind of security ("How can I sandbox gptel tools?") I have found a solution that works great for me and have documented...

@munen Let's merge the one-line change of using `(abbreviate-file-name ...)` instead of `(file-name-base ...)` first, as that's the original purpose of this PR. I can make this one line change...

I made the change to use `abbreviate-file-name`. That satisfies the original purpose of this PR. I'll have to come back to the rest of this when I have more time...

Thanks for the PR. The line you changed just removes the check to disable streaming when using tools with Ollama. There is no actual logic in `gptel-ollama.el`for parsing streaming tool...

@timfel Did you have any luck getting streaming + tools to work with Ollama?

This is best done using function advice around `gptel-request` that checks using your preferred whitelist/blacklist method. ``` emacs-lisp (define-advice gptel-request (:before (prompt &rest args) gptel-blacklist) "Possibly cancel this gptel request"...

Sorry, I don't follow the issue. The menu that opens when you run `C-u M-x gptel-send` is not the minibuffer, it is a transient menu in its own buffer. "Transient...

> I think there are several issues. > > One is that I have no clue that a transient menu appears, but this I think is really not a real...

> No worries. There is no emergency about this issue so just put it aside > and let it come back when the circumstances make it possible without > damaging...