From: "T.V Raman" <raman@google.com>
To: Jesse Millwood <jesse_m@fastmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: On the adoption of transient.el
Date: Wed, 04 Aug 2021 14:45:47 -0700 [thread overview]
Message-ID: <p917dh0evec.fsf@google.com> (raw)
In-Reply-To: <d581da2c-f581-cbd1-d4d2-7080c64b0f85@fastmail.com> (Jesse Millwood's message of "Wed, 4 Aug 2021 15:57:25 -0400")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 4774 bytes --]
Jesse Millwood <jesse_m@fastmail.com> writes:
I was more motivated to get it solved because where for you it was a
pain-point, for me it was a show-stopper:-)
Jonas' help got me over the hump.
Stepping back, yes, transient, especially when encountered first via
magit looks complex. But that complexity comes from how much more
complex git is --- what transient does well is to make the large
bucket-loads of git commandline options more tractable.
It's also a very good attempt at bringing features of "direct
manipulation interfaces" to the emacs world --- I use the term "direct
manipulation" intentionally, that is actually what people mean when they
jump to a GUI. But transient shows that it is possible to implement such
interfaces within the Emacs paradigm by stretching the boundaries a
little, and where we do feel discomfort with respect to over-stretching
those boundaries (losing isearch is an example), we can claw it back.
Note that things like dired in emacs are also direct-manipulation
interfaces --- they just preserve *all* of the goodness of Emacs.
The other package that is similar to transient with many advantages is
hydra --- though I haven't seen any hydras as complex as the transients
that Git forces magit to require.
> Oh wow, not being able to search that buffer has been my main pain
> point of transient. Thank you so much!
>
> On 2021-08-04 2:56 p.m., T.V Raman wrote:
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>
> I recently discovered thanks to the transient/magit author that once you
> enable navigation via arrows in transient popups, it also gives you
> isearch of the transient. We then discovered a bug where using isearch
> to find a transient option and pressing enter wasn't working, but
> Jonas has since fixed that and it works.
> transient-enable-popup-navigation is a variable defined in ¡®transient.el¡¯.
>
> Its value is t
> Original value was nil
>
> You can customize this variable.
> This variable was introduced, or its default value was changed, in
> version 0.2.0 of the transient package.
>
> Whether navigation commands are enabled in the transient popup.
>
> While a transient is active the transient popup buffer is not the
> current buffer, making it necessary to use dedicated commands to
> act on that buffer itself. If this non-nil, then the following
> features are available:
>
> - "<up>" moves the cursor to the previous suffix.
> "<down>" moves the cursor to the next suffix.
> "RET" invokes the suffix the cursor is on.
> - "<mouse-1>" invokes the clicked on suffix.
> - "C-s" and "C-r" start isearch in the popup buffer.
>
>
> Rudolf Adamkovi00 <salutis@me.com> writes:
>
> 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?
>
>
> I am not sure if this is something specific to modern interfaces, or
> rather an overreaching when it comes to binding. After a while I managed
> to "pin-point" what was irritating me, and it was the missing ability to
> search (something that I seem to do so passively that i didn't even
> notice it). Having C-s work is especially useful when there are a lot of
> transient options. This cannot be solved by binding C-s manually,
> as just because that might work for me, there is some other behaviour
> someone else is expecting (eg. your example of selecting and copying
> text).
>
> What I understand transient and certain other packages do is basically
> override most keys, even those it doesn't use. This is more invasive
> than special-mode, that just doesn't bind self-insert-command to most
> keys. What I wonder is why this is done/why it might be necessary.
>
> R+
>
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2021-08-04 21:45 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 21:13 On the adoption of transient.el Gabriel
2021-07-05 14:24 ` Philip Kaludercic
2021-07-05 16:09 ` Gabriel
2021-07-05 17:00 ` Stefan Monnier
2021-07-05 19:16 ` Lars Ingebrigtsen
2021-07-05 16:50 ` Yuri Khan
2021-07-05 17:06 ` Eli Zaretskii
2021-07-05 17:29 ` Yuri Khan
2021-07-05 17:49 ` Stefan Monnier
2021-07-05 18:09 ` Philip Kaludercic
2021-08-01 20:19 ` Rudolf Adamkovič
2021-08-01 21:08 ` T.V Raman
2021-08-01 21:24 ` Arthur Miller
2021-08-03 13:07 ` Jonas Bernoulli
2021-08-03 20:00 ` Arthur Miller
2021-08-14 3:17 ` Arthur Miller
2021-08-14 12:54 ` Óscar Fuentes
2021-08-14 20:45 ` Arthur Miller
2021-08-15 21:57 ` John Yates
2021-08-16 1:05 ` Arthur Miller
2021-08-16 1:35 ` Stefan Monnier
2021-08-16 2:36 ` Arthur Miller
2021-08-01 21:25 ` Arthur Miller
2021-08-04 11:22 ` Philip Kaludercic
2021-08-04 15:56 ` Óscar Fuentes
2021-08-04 18:56 ` T.V Raman
2021-08-04 19:57 ` Jesse Millwood
2021-08-04 21:45 ` T.V Raman [this message]
2021-08-05 7:01 ` Arthur Miller
2021-08-05 8:59 ` Eric S Fraga
2021-08-05 9:23 ` Tim Cross
2021-08-05 10:37 ` Eric S Fraga
2021-08-05 11:01 ` Eli Zaretskii
2021-08-05 14:45 ` Óscar Fuentes
2021-08-05 16:17 ` Eli Zaretskii
2021-08-05 23:17 ` Juri Linkov
2021-08-06 6:11 ` Eli Zaretskii
2021-08-06 2:13 ` Phil Sainty
2021-08-05 23:20 ` Juri Linkov
2021-08-06 12:39 ` John Yates
2021-08-06 14:42 ` Stefan Monnier
2021-08-06 17:20 ` Omar Polo
2021-08-10 7:22 ` Juri Linkov
2021-08-10 10:32 ` John Yates
2021-08-08 1:21 ` Dmitry Gutov
2021-08-10 7:15 ` Juri Linkov
2021-08-10 12:40 ` Dmitry Gutov
2021-08-11 6:58 ` Juri Linkov
2021-08-13 3:06 ` Dmitry Gutov
2021-08-08 1:42 ` Alfred M. Szmidt
2021-08-10 7:18 ` Juri Linkov
2021-08-10 8:16 ` Alfred M. Szmidt
2021-08-11 6:56 ` Juri Linkov
2021-08-05 9:38 ` Arthur Miller
2021-08-05 9:51 ` Jean-Christophe Helary
2021-08-05 14:33 ` T.V Raman
2021-08-05 14:55 ` Eric S Fraga
2021-08-05 15:05 ` Arthur Miller
2021-08-06 23:02 ` Rudolf Adamkovič
2021-08-07 2:03 ` T.V Raman
2021-08-07 3:15 ` Phil Sainty
2021-08-07 10:19 ` Jonas Bernoulli
2021-08-07 15:42 ` T.V Raman
2021-07-05 19:51 ` Jim Porter
-- strict thread matches above, loose matches on Subject: below --
2022-07-31 9:08 Manuel Uberti
2022-07-31 13:25 ` T.V Raman
2022-07-31 20:03 ` Juri Linkov
2022-08-21 16:04 ` Juri Linkov
2022-08-01 3:32 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p917dh0evec.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=jesse_m@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).