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

Feature Request: Support for different modes for vim bindings #72

Open
guruor opened this issue May 12, 2024 · 2 comments
Open

Feature Request: Support for different modes for vim bindings #72

guruor opened this issue May 12, 2024 · 2 comments
Labels
enhancement New feature or request good first contribution Good for newcomers

Comments

@guruor
Copy link

guruor commented May 12, 2024

Being a vim user I was using rest.nvim, it covers my day to day usage except for few cases like file upload. So was always looking for a lightweight alternative of Postman. Thank you so much for a lightweight client.

I tried using the vim bindings provided in the repo, it unfortunately didn't work as expected, it usually causes conflicts when editing values. For example the default binding used to display help is H, Now when editing the URL, if I were to type variable name HOST, I am not able to do so because the moment I type H it opens up the help menu.

Screen.Recording.2024-05-13.at.9.04.23.AM.mov

As a workaround I can remap the help binding but that would cause conflict with some other key which I will need to remap.

So I am suggesting to implement vim modes like NORMAL and INSERT, where in INSERT mode no keys will trigger the binding action and ESC key can change the mode back to NORMAL.
Similar implementation can be found in this terminal file manager yazi

Sample clip from their demo:

Screen.Recording.2024-05-12.at.5.52.52.PM.mp4

OR

We can add an option to open the content in preferred editor using $EDITOR where user can edit the content and edited content can be conveyed back to ATAC, this will provide more flexibility and user can utilise the syntax highlighting of the editor as well.

@guruor
Copy link
Author

guruor commented May 13, 2024

After testing for a while I could see that for body textarea we have vim emulation available, but it is not available for input boxes.
I could find the input component in yazi source: yazi-core/src/input
We can utilise this components.

@Julien-cpsn
Copy link
Owner

Hello @G0V1NDS

thanks for your issue and your investment on the project

The big problem with the text area is that it remains unmaintained and is plainfull to use. Concerning the main issue you are talking about, I personnally think that it would a great thing the improve the vim config file. Since it works great with most use case.

If you have any more ideas, tell me

Have a great day

@Julien-cpsn Julien-cpsn added enhancement New feature or request good first contribution Good for newcomers labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first contribution Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants