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

quit-prompt-buffer and prompt-buffer-canceled naming inconsistency? #27

Open
aartaka opened this issue Jan 24, 2023 · 3 comments
Open
Labels
question Further information is requested

Comments

@aartaka
Copy link
Contributor

aartaka commented Jan 24, 2023

Since atlas-engineer/nyxt#2655, the function that used to be called cancel-input is called quit-prompt-buffer. But the condition that used to be related to this function is still called prompt-buffer-canceled, which may confuse someone using Nyxt's prompt buffer.

I see two ways out of this inconsistency:

  1. Return the cancel as a verb to relate to this operation. Thus, have cancel-prompt-buffer or something similar.
  2. Rename prompt-buffer-canceled to refer to "quit"-ting.

I am personally in favor of (1), because

  • I like how clear and actionable "cancel" is: quitting is much more neutral of an action that does not fully express the unwillingness to terminate the prompt normally, while cancelling is doing something against the expected scenario and bailing out of the prompt altogether.
  • It's more backwards-compatible and breaks less user configs with no clear way to fix them.
@aartaka aartaka added the question Further information is requested label Jan 24, 2023
@aadcg
Copy link
Member

aadcg commented Jan 24, 2023

No strong opinion.

@Ambrevar
Copy link
Member

No strong opinion either, however slightly leaning towards being conservative with the previous naming, so option (1).

@lansingthomas
Copy link

I like cancel.
canceling is stopping something in progress, while quitting is like leaving. And there are other similarly named things with quit.

@aadcg aadcg transferred this issue from atlas-engineer/nyxt Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Development

No branches or pull requests

4 participants