Skip to content
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

UI: increase of keystrokes to increase previous command - feature request #358

Closed
drahnr opened this issue Apr 28, 2022 · 5 comments
Closed

Comments

@drahnr
Copy link

drahnr commented Apr 28, 2022

I tried atuin, and I it's helpful when investigating a command that's further back. For the immediate use case of re-running the previous command, it requires an additional keystroke and flashes the entire terminal twice which is a rather large visual overhead.

Feature request:

Allow to configure a number of ups before opening the full TUI.

@redsfyre
Copy link

redsfyre commented Apr 29, 2022

Actually, there is a configuration for this. It's not exactly what you want, but you can make it work with just the ctrl+R shortcut instead of both ctrl+R and arrow keys. Or vice versa. For detailed information https://github.com/ellie/atuin/blob/main/docs/key-binding.md#key-binding The number of ups setting can become even more annoying than its default state :/

@jirutka
Copy link
Contributor

jirutka commented May 18, 2022

…flashes the entire terminal twice which is a rather large visual overhead.

This exactly. I think that atuin shouldn’t bind the Up Arrow key by default, its UI is really not good fit for this.

@conradludgate
Copy link
Collaborator

Allow to configure a number of ups before opening the full TUI.

I'm not sure if it's even possible to register different up-key handling like this. My only suggestion would be to disable the default keybinding and create your own.

If someone better at shell than I knows of a way we can do this across all our currently supported shells, then I'd be happy to assist in getting that feature planned out

its UI is really not good fit for this

It's certainly not what you're used to. I found it intrusive in the beginning but now I struggle to use a terminal without it. So I would try to avoid stating personal opinions like this as fact

@ellie
Copy link
Member

ellie commented May 19, 2022

I'm going to be closing this one for now - it is very unlikely we will ever implement this, and if your workflow requires it then you can implement it in your own shell config

For the immediate use case of re-running the previous command, it requires an additional keystroke and flashes the entire terminal twice which is a rather large visual overhead.

If this is something that bothers you, then I'd suggest setting ATUIN_NOBIND and perhaps just binding to ctrl-R. I know some people prefer Atuin launching immediately on the up arrow, and some don't, so really it just comes down to configuring your shell to your preference.

Alternatively, you might prefer the compact UI mode.

@ellie ellie closed this as completed May 19, 2022
vimpostor added a commit to vimpostor/dotfiles that referenced this issue Aug 11, 2023
This is just terrible UX if you want to quickly fire up the previous
command again. Only bind atuin to Ctrl+r instead.

refs: atuinsh/atuin#798
refs: atuinsh/atuin#358
refs: atuinsh/atuin#51
@ZetaTwo
Copy link

ZetaTwo commented Aug 26, 2023

I just wanted to say that I also think something like this would be a great feature. For example adding an option to have the first up press simply go to the last command and then the second up press open the full Atuin UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants