-
Notifications
You must be signed in to change notification settings - Fork 39
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
Using gt-posframe-*-render
results in error "dead frame"
#77
Comments
Strange. Can you provide more informations about your enviroment and your config? |
Sorry for the delay. Happened to me again today.
I'm working with emacs client/sever... Yesterday I used gt-do-translate, in a popup, yanked the results, then escaped the popup. Then I closed the emacs client. Today I re-opened emacs (client) and called gt-do-translate and got the error |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
With the "old" go-translate, I had configured the rendered to show the results in a new buffer (which is now
gt-buffer-render
), but I had the same problem as #66 , where the buffer had sometimes switched to read-only (maybe due to the use of DoomEmacs in client/server mode?).With the "new" version, I decided to switch to
gt-posframe-*-render
. With thepop
version, I couldn't copy the translation back to my working buffer, as moving the mouse or clicking inside thepop
buffer made it disappear. I couldn't also switch the languages witht
as it also made thepop
buffer disappear. So I switched to thepin
version. However, I often get the following error:I've verified, I quit the pop-up frame correctly (according to included pop-up doc), by hitting
q
. I'm not sure if the problem is also due to the use of DoomEmacs in client/server mode?But in the end I cannot manage to find a configuration that works for
gt-do-translate
, which is very painful because the extension is VERY useful !The text was updated successfully, but these errors were encountered: