-
-
Notifications
You must be signed in to change notification settings - Fork 405
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 modes and commands #3311
Conversation
@@ -169,35 +169,6 @@ Important pieces of functionality are: | |||
"Scroll to top if no input element is active, forward event otherwise." | |||
(call-non-input-command-or-forward #'scroll-to-top :buffer buffer)) | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you deleted all of the go-* functions. Yes, why not. I don't think anyone will miss them. Plus they need some reworking to consider /all/ cases, to be more reliable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go-to-homepage
and go-up
aren't hard to get right so heuristics would be needed. Should do engage in such endeavors when we have so many concrete and properly defined issues at hand? Probably not.
go-next
and go-previous
seemed to misbehave. I tried them out and a JS warning was raised if I'm not mistaken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've gone through commit by commit. I've tested it on my local system. All appears well. Thank you Andre!
The functionality isn't paramount.
The way the mode implements the feature is subpar.
cdf1fd5
to
81a9ac9
Compare
Description
Fixes #1633
Fixes #3297
Checklist:
(asdf:test-system :nyxt/gi-gtk)
)