Rudolf Adamkovič <salutis@me.com> writes:

I think some of this stems from the fact that transient displays the
choices in a window that is actually not the "current window/buffer" in
the common Emacs sense  --- it does take some getting used to --- at
least in the beginning.

I've gotten used to it over time, but only after writing some of my own
Emacspeak wrappers --- on the positive side, the   transient author has
been very helpful in that process.

So on the plus-side, magit/transient does go somewhat outside the
"vanilla emacs box", but it's also a good opportunity to experiment with
new/newer interaction paradigms. I dont think this will cause Emacs to
go the Apple/Microsoft way since as a community, Emacs will never lock
itself down to one single  frozen way of doing UI.

(Or at least I hope so):-)
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> On the other hand something has always felt off about transient, in
>> the sense that it is breaking some expected behaviour or couldn't
>> pin-point yet, but just unconsciously stumble over. 
>
> This is exactly how I feel about the "modern" interfaces in Emacs. I
> reported a bug in Embark recently, and because I could not select and
> copy the text, I ended up re-typing the text that was right in front
> of me in Emacs. Say what? For me, Emacs is a program where I expect to
> never waste time re-typing anything. Magit has a similar feel to it,
> and I can never be sure if the program will allow me to select text in
> the diverse parts of its user interface. In my opinion, such
> uncertainty is bad for power users. I would expect this from Apple or
> Microsoft software, because their latest “UX designers” surely know
> better than anyone, but in Emacs?
>
> R+

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♈ Id: kg:/m/0285kf1  🦮