Feature contexthinter #8087
Open
Feature contexthinter #8087
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mkonig
force-pushed
the
feature_contexthinter
branch
from
bce6339
to
dc9368e
Compare
|
I did use black to format. Will change this asap and update the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new hint mode "context".
This mode tries to make hints based on the text used in links, buttons, image elements etc.
The advantage to existing modes is that the hints are easier to predict and therefore faster to type. In addition hints for the same or similar elements in different webpages are most of the time the same. E.g. buttons with "accept" will almost always have the hint "acc".
Or menu elements in pages like gitlab, github etc will almost always have the same hint no matter the project you are in.
Another example if one hints filenames in repos, the hints will most likely be the same as the start of the filename. So it is easier to type the hint, because one already had the filename in mind.
You might have noticed that I use "almost always" a lot, because the hint mode does not guarantee that the hints are the same every time. But it is most likely they are.
I also added a feature to set the wm_class name. I use this to run multiple different instances of qutebrowser in i3 and want to be able to diffirenciate.
But I have no problem if that feature would be removed for this pull request.