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

Delete Commands #3297

Closed
13 of 19 tasks
jmercouris opened this issue Dec 22, 2023 · 4 comments · Fixed by #3311
Closed
13 of 19 tasks

Delete Commands #3297

jmercouris opened this issue Dec 22, 2023 · 4 comments · Fixed by #3311
Assignees
Labels
command Core functionality: commands. ui/ux Nyxt User Interface: themes, appearance and usability.

Comments

@jmercouris
Copy link
Member

jmercouris commented Dec 22, 2023

After reviewing all Nyxt commands, I believe the following should be deleted:

@jmercouris jmercouris added the ui/ux Nyxt User Interface: themes, appearance and usability. label Dec 22, 2023
@jmercouris
Copy link
Member Author

Are there any reasons not to delete them?

@aadcg aadcg added the command Core functionality: commands. label Dec 22, 2023
@aadcg
Copy link
Member

aadcg commented Dec 22, 2023

In my view, some of these commands should be demoted to functions:

  • clean-configuration
  • enable-hook-handler
  • disable-hook-handler

History commands

From all history commands below you suggest deleting history-forwards-query alone. What motivates this choice?

  • history-forwards
  • history-backwards-query
  • history-forwards-direct-children
  • history-forwards-maybe-query
  • history-forwards-query
  • history-forwards-all-query
  • history-all-owner-nodes-query
  • history-all-query
  • buffer-history-tree

load-file

What motivates your view? The fact that we have load-config-file and load-file is too general? Right now, I believe it should stay.


nyxt-init-time

I believe it should stay. Nyxt users value tweaking their systems so it seems useful.


set-action-on-current-suggestion

If we delete this command, then the user isn't able to set it dynamically. I think it should stay. At least until we change the prompt buffer UI/UX with regards to actions (if we ever do).


@jmercouris I've edited your top post.

I can do it once we reach a decision.

@aadcg aadcg self-assigned this Dec 22, 2023
@aadcg
Copy link
Member

aadcg commented Jan 12, 2024

@jmercouris mode record-input-field-mode defines 3 commands, and all have been marked for deletion. I took a cursory look and I'd suggest deleting the mode completely. I don't think it's a core feature.

@jmercouris you marked go-up for deletion. What about go-to-homepage, go-next and go-previous?

@jmercouris
Copy link
Member Author

Firstly. I am OK with all of your suggestions about what not to delete that you've listed above.

With regards to record-input-field-mode, yes, we can fully delete it.

With regards to go-up, go-next et al., the problem is that it works on so /few/ pages, and thus presents to the user a degraded experience. If we could generalize it for websites that do not support this pattern, or provide the user with a helpful message, we could leave them in.

@aadcg aadcg changed the title Delete Functions Delete Commands Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
command Core functionality: commands. ui/ux Nyxt User Interface: themes, appearance and usability.
Development

Successfully merging a pull request may close this issue.

2 participants