-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Usability papercuts on keyboard shortcut help page #603
Comments
cc @ellisonbg @captainsafia @willingc for user-facing help. The case issue will likely change, as we are going to switch to a different system where the label will be the actual text typed, instead of the key cap ('A ≠ a', etc.). |
Yes, I agree that it's great terminology! I learned it from Ubuntu. |
As @minrk mentioned, we are working on a new keyboard shortcut that will On Wed, Oct 14, 2015 at 8:37 AM, Peter Williams [email protected]
Brian E. Granger |
Just a bump for the capitalization issue. I know you all have bigger fish to fry, but after spending two months thinking my browser extensions were breaking the |
Adjusted the issue tags for visibility, @ChrisKeefe |
Thanks for the label update @willingc. I'm a little confused though regarding the combination of "enhancement" and "help wanted" on a repository in which we've been trying to convey is in maintenance mode for well over a year now. It seems like the direction this enhancement should take is relative to Jupyter Lab since our "bigger fish" will be based on that codebase. Perhaps Lab already handles this condition? If this is something trivial and zero risk (I have no idea) then perhaps it can be viewed as a usability bug rather than an enhancement. That said, the same functionality should then be added to Lab (or RetroLab) so a regression issue is not introduced when moving to Notebook V7. |
@kevin-bates Thanks! I removed the enhancement label. If anyone is interested in this issue, please discuss with the JupyterLab team. |
As a new user who was recently viewing the Notebook help page on keyboard shortcuts, I encountered two usability papercuts:
The text was updated successfully, but these errors were encountered: