search

lorniu / go-translate

Translator on Emacs. Supports multiple engines such as Google, Bing, deepL, ChatGPT, StarDict, Youdao and so on.
GNU General Public License v3.0
274 stars 37 forks source link

Using `gt-posframe-*-render` results in error "dead frame" #77

Open liar666 opened 2 months ago

liar666 commented 2 months ago

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 https://github.com/lorniu/go-translate/issues/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 the pop version, I couldn't copy the translation back to my working buffer, as moving the mouse or clicking inside the pop buffer made it disappear. I couldn't also switch the languages with t as it also made the pop buffer disappear. So I switched to the pin version. However, I often get the following error:

[output init error] (wrong-type-argument frame-live-p #<dead frame  0x5c6dcff9c5f0>)

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 !

lorniu commented 2 months ago

Strange. Can you provide more informations about your enviroment and your config?