Henrik Ahlgren

Okay, I believe I finally figured it out. Of course can't promise some weird `transient-display-buffer-action`setup couldn't break things, but I think this is at least more correct than what we...

(Okay not quite there yet but after a good night sleep I'll get there. Turns out the horizontal use case is more tricky + need to check for window-live-p)

Things I've learned so far trying to get this working: 1. Using `window-width` is incorrect, `window-max-chars-per-line` should be used when calculcating layout. In practice, both of them return the same...

> Wow, thanks for the comprehensive investigation. I'll test when I can. My conclusion is that at least with transient.el 0.8.4 getting the correct window width is very hard if...

> If the default is set to `frame-width` it breaks like this if displaying transient in a window narrower than the frame: Okay, what kind of `transient-display-buffer-action` configuration would that...

One option is the default main menu be adjusted to two columns instead of three to better fit an 80-character width. However, this change would result in a taller layout...

> > Right now even the most common use case is broken > > What is the most common use case? I don't think many people are using > Emacs...

(And pushed a brown bag bugfix, never use setcar when tired :)

(Ah, added a check to actually not attempt to kill-region if read-only.) BTW, how the transient menu should behave in case the user selects a read-only buffer as a destination?

> Coincidentally, I pushed a read-only behavior change a short while before I saw this PR. There will be a merge conflict. Noted, will rebase. > > * gptel.el (gptel-read-only-response-buffer,...