-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transient menu annoyingly introduces extra window when Helm mode enabled #656
Comments
Also occurs with model selection. I truly don't remember this happening before. This could be a Transient-specific bug, but Magit works without issue for me. |
What is your value of transient-display-buffer-action?
…On Wed, Feb 19, 2025, 11:49 PM daedsidog ***@***.***> wrote:
Also occurs with model selection. I truly don't remember this happening
before.
—
Reply to this email directly, view it on GitHub
<#656 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBVOLGJJYET56J4PHGWSPL2QWCI5AVCNFSM6AAAAABXQBNIF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZQG4YDSNJSGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
[image: daedsidog]*daedsidog* left a comment (karthink/gptel#656)
<#656 (comment)>
Also occurs with model selection. I truly don't remember this happening
before.
—
Reply to this email directly, view it on GitHub
<#656 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBVOLGJJYET56J4PHGWSPL2QWCI5AVCNFSM6AAAAABXQBNIF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZQG4YDSNJSGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
> What is your value of transient-display-buffer-action?
`(display-buffer-in-side-window (side . bottom) (dedicated . t) (inhibit-same-window . t))`
That looks fine. My guess is that Helm doesn't respect display-buffer settings then? The best way to test if this is a gptel issue would be to use a magit command that invokes (Helm's) completing-read and see if the problem occurs.
|
I've tried lots of Magit commands and couldn't recreate it (e.g. |
Can you try (and suggest) a command that isn't a suffix, i.e. it doesn't end the transient session? |
Also please try this transient: (transient-define-prefix test-pre ()
"TODO"
["Test"
("r" "read" "r"
:class transient-option
:prompt "Pick: "
:reader (lambda (p i h)
(completing-read p '("one" "two" "three")
nil nil i h)))]) Use the This is almost definitely a Helm + Transient issue, not gptel. You can track the status of this report at magit/transient#358 |
Yes
I suspected as much. Closing as it is not gptel-related. |
Bug Description
Exiting out of the
gptel-menu
transient menu after invoking something that relies on completing read that was rerouted to Helm mode creates a buffer that stays after the transient menu has been closed.Backend
None
Steps to Reproduce
helm-mode
andgptel
(helm-mode 1)
M-x gptel-menu -i C-g C-g
to introduce the aforementioned buffer (sometimes, just a singleC-g
is enough to exit out ofgptel-menu
, but other times you need two: one to exit the-i
menu and another to exitgptel-menu
M-x gptel-menu
:-i
:C-g
(orC-g C-g
):Additional Context
Emacs version: GNU Emacs 29.4 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.43, cairo version 1.18.2)
OS: WSL2 Arch Linux
Helm versions:
Transient version:
Bug can be recreated using both the latest gptel master and v0.9.7.
The text was updated successfully, but these errors were encountered: