-
Notifications
You must be signed in to change notification settings - Fork 5k
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 the Ability to Remove Some Toolbar Buttons #2294
Comments
Let's see if this works: @meeseeksdev, migrate to jupyter/notebook |
|
I'd like to +1 this, or a slightly different variant: PS. |
Unfortunately Github doesn't make it possible to migrate an issue and preserve the identity of people making the comments, but meeseeksdev does record who opened the original issue:
|
It will be added after clicking on Settings > Settings Editor |
thanks ! so I have been able to use the UI in order to remove the last 2 items:
and have observed the change to be stored in file
now, in the perspective of deploying ready-to-use containers for students, what would be in your experience the best way to have this as a default ? I can pre-populate this file of course, but are there other more programmatic ways to achieve the same result ? to give some background, we used to achieve this kind of UI customization in the context of classic using sorry for the flood of questions ;-) and thank you for all the work and the valuable insights ! |
Apologies if this is the wrong place to post this.
It would be nice to be able to remove some buttons from the toolbar. After adding some extensions my toolbar is overcrowded and spans two rows, but some of the buttons I never ever use. In particular the 'CellToolbar' button, presentation buttons, and 'Code/Markdown/etc' button use a lot of real estate for no useful functionality for me personally. It would be great to have a little config menu to deselect active buttons.
Originally opened as jupyter/jupyter_client#246 by @MikeDacre, migration requested by @Carreau
The text was updated successfully, but these errors were encountered: