-
-
Notifications
You must be signed in to change notification settings - Fork 417
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
Add option to navigate line-wise #177
Comments
Don't see a reason why we couldn't add a configuration option for this. |
This issue will be mostly resolved once vim like navigation arrives. I'm working on it right now. #31 |
Vim-like navigation is more than I was hoping for, thanks!
|
@humenda |
I would like to avoid installing all the required dependencies. Can I use docker
to build from source as well? If so, how would that work? The README only
details the general development workflow.
Thanks
|
@humenda |
@tobimensch
I now tried several times to build Browsh on my machine, but I'm hitting too
many errors with NPM for which I don't have the time to figure out the cause
for, sorry.
|
@tobimensch x86_64 GNU/Linux. Thanks
|
What's the state of this (and the vim-navigation branch)? |
I'm not actively working on Browsh at the moment. But as ever, I do to still have plans for Browsh, and I very much hope to fix those things. |
Blind users are using a screen reader with synthetic speech and optionally a
braille display to read the contents of the terminal. The navigation happens
line-wise and the synthetic speech reads text from left to right.
It would be therefore very beneficial if the arrow keys (and
j,k
in the futureVi mode) would only move the cursor position by a line. This could be a
configuration option, if changing the default behaviour is not desired. As a
reference, this behaviour is default in w3m.
Additionally, the cursor should be positioned at the beginning of the text
buffer.
Thanks
The text was updated successfully, but these errors were encountered: