Jupyter Notebook Markdown Font



Markdown is a way to format text. By default, Jupyter notebooks cells are formatted to display code, so without markdown, there is no easy way to include explanatory text in your notebooks. Of course, you can always include code comments, but those cannot be formatted. And what about links or images? In a markdown cell, displaying images as displays the image as expected. However, displaying images as does not display.

  1. Jupyter Notebook Markdown Font
  2. Jupyter Notebook Markdown Code Font
  3. Jupyter Markdown Font Size

Jupyter (formerly IPython Notebook) is an open-source project that lets you easily combine Markdown text and executable Python source code on one canvas called a notebook. Visual Studio Code supports working with Jupyter Notebooks natively, as well as through Python code files. This topic covers the native support available for Jupyter Notebooks and demonstrates how to:

  • Create, open, and save Jupyter Notebooks
  • Work with Jupyter code cells
  • View, inspect, and filter variables using the Variable explorer and Data viewer
  • Connect to a remote Jupyter server
  • Debug a Jupyter notebook

Setting up your environment

To work with Jupyter notebooks, you must activate an Anaconda environment in VS Code, or another Python environment in which you've installed the Jupyter package. To select an environment, use the Python: Select Interpreter command from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

Jupyter Notebook Markdown Font

Once the appropriate environment is activated, you can create and open a Jupyter Notebook, connect to a remote Jupyter server for running code cells, and export a Jupyter Notebook as a Python file.

Note: By default, the Visual Studio Code Python extension will open a Jupyter Notebook (.ipynb) in the Notebook Editor. If you want to disable this behavior you can turn it off in settings. (Python > Data Science: Use Notebook Editor).

Jupyter Notebook Markdown Font

Create or open a Jupyter Notebook

You can create a Jupyter Notebook by running the Jupyter: Create Blank New Jupyter Notebook command from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) or by creating a new .ipynb file in your workspace. When you select the file, the Notebook Editor is launched allowing you to edit and run code cells.

If you have an existing Jupyter Notebook, you can open it in the Notebook Editor by double-clicking on the file and opening with Visual Studio Code, through the Visual Studio Code, or using the Command Palette Jupyter: Open in Notebook Editor command.

Once you have a Notebook created, you can run a code cell using the green run icon above the cell and the output will appear directly below the code cell.

Trusted Notebooks

It's possible for malicious source code to be contained in a Jupyter Notebook. With that in mind, to help protect you, any Notebook that's not created with VS Code on your local machine (or explicitly set to Trusted by you) is considered Not Trusted. When a Notebook is Not Trusted, VS Code will not render Markdown cells or display the output of code cells within the Notebook. Instead, just the source of Markdown and code cells will be shown. The Notebook is essentially in read-only mode, with toolbars disabled and no ability to edit the file, until you set it as Trusted.

Note: Before setting a Notebook as Trusted, it is up to you to verify that the source code and Markdown are safe to run. VS Code does not perform any sanitizing of Markdown, it merely prevents it from being rendered until a Notebook is marked as Trusted to help protect you from malicious code.

When you first open a Notebook that's Not Trusted, the following notification prompt is displayed.

If you select Trust, the Notebook will be trusted going forward. If you opt not to trust the Notebook, then Not Trusted will be displayed in the toolbar and the Notebook will remain in a read-only state as described previously. If you select Trust all notebooks, you will be taken to settings, where you can specify that all Notebooks opened in VS Code be trusted. That means you will no longer be prompted to trust individual notebooks and harmful code could automatically run.

You can relaunch the trust notification prompt after reviewing the Notebook by clicking on the Not Trusted status.

Save your Jupyter Notebook

You can save your Jupyter Notebook using the keyboard combo Ctrl+S or through the save icon on the Notebook Editor toolbar.

Note: At present, you must use the methods discussed above to save your Notebook. The File>Save menu does not save your Notebook, just the toolbar icon or keyboard command.

Export your Jupyter Notebook

Jupyter Notebook Markdown Code Font

You can export a Jupyter Notebook as a Python file (.py), a PDF, or an HTML file. To export, just click the convert icon on the main toolbar. You'll then be presented with file options from the Command Palette.

Note: For PDF export, you must have TeX installed. If you don't, you will be notified that you need to install it when you select the PDF option. Also, be aware that if you have SVG-only output in your Notebook, they will not be displayed in the PDF. To have SVG graphics in a PDF, either ensure that your output includes a non-SVG image format or else you can first export to HTML and then save as PDF using your browser.

Work with code cells in the Notebook Editor

The Notebook Editor makes it easy to create, edit, and run code cells within your Jupyter Notebook.

Create a code cell

By default, a blank Notebook will have an empty code cell for you to start with and an existing Notebook will place one at the bottom. Add your code to the empty code cell to get started.

Code cell modes

While working with code cells a cell can be in three states, unselected, command mode, and edit mode. The current state of a cell is indicated by a vertical bar to the left of a code cell. When no bar is visible, the cell is unselected.

An unselected cell isn't editable, but you can hover over it to reveal additional cell specific toolbar options. These additional toolbar options appear directly below and to the left of the cell. You'll also see when hovering over a cell that an empty vertical bar is present to the left.

When a cell is selected, it can be in two different modes. It can be in command mode or in edit mode. When the cell is in command mode, it can be operated on and accept keyboard commands. When the cell is in edit mode, the cell's contents (code or Markdown) can be modified.

When a cell is in command mode, the vertical bar to the left of the cell will be solid to indicate it's selected.

When you're in edit mode, the vertical bar will have diagonal lines.

To move from edit mode to command mode, press the ESC key. To move from command mode to edit mode, press the Enter key. You can also use the mouse to change the mode by clicking the vertical bar to the left of the cell or out of the code/Markdown region in the code cell.

Add additional code cells

Code cells can be added to a Notebook using the main toolbar, a code cell's vertical toolbar, the add code cell icon at the bottom of the Notebook, the add code cell icon at the top of the Notebook (visible with hover), and through keyboard commands.

Using the plus icon in the main toolbar will add a new cell directly below the currently selected cell. Using the add cell icons at the top and bottom of the Jupyter Notebook, will add a code cell at the top and bottom respectively. And using the add icon in the code cell's toolbar, will add a new code cell directly below it.

When a code cell is in command mode, the A key can be used to add a cell above and the B can be used to add a cell below the selected cell.

Jupyter

Select a code cell

The selected code cell can be changed using the mouse, the up/down arrow keys on the keyboard, and the J (down) and K (up) keys. To use the keyboard, the cell must be in command mode.

Run a single code cell

Once your code is added, you can run a cell using the green run arrow and the output will be displayed below the code cell.

You can also use key combos to run a selected code cell.

  • Ctrl+Enter runs the currently selected cell
  • Shift+Enter runs the currently selected cell and, if a cell is not already present, inserts a new cell immediately below (focus moves to the below cell in command mode)
  • Alt+Enter runs the currently selected cell and inserts a new cell immediately below (focus moves to new cell in edit mode).

Jupyter Markdown Font Size

These keyboard combos can be used in both command and edit modes.

Run multiple code cells

Running multiple code cells can be accomplished in a number of ways. You can use the double arrow in the toolbar of the Notebook Editor to run all cells within the Notebook or the run icons with directional arrows to run all cells above or below the current code cell.

Run code by line

To help diagnose issues with your Notebook code, run-by-line lets you step through the code of a cell in a line-by-line fashion. While stepping through code you can view the state of variables at each step via the variable explorer or hover your mouse over variables to see data tips.

To start a session, just click the run-by-line icon to the right of the run cell icon on the cell's toolbar.

Once in a run-by-line session, you can run the currently highlighted line of code by pressing the icon again. To exit, just click the stop button next to the run-by-line icon in the cell.

Move a code cell

Moving code cells up or down within a Notebook can be accomplished using the vertical arrows beside each code cell. Hover over the code cell and then click the up arrow to move the cell up and the down arrow to move the cell down.

Delete a code cell

Deleting a code cell can be accomplished by hovering over a code cell and using the delete icon in the code cell toolbar or through the keyboard combo dd when the selected code cell is in command mode.

Undo your last change

You can use the z key to undo your previous change, for example, if you've made an accidental edit you can undo it to the previous correct state, or if you've deleted a cell accidentally you can recover it.

Switch between code and Markdown

The Notebook Editor allows you to easily change code cells between Markdown and code. By default a code cell is set for code, but just click the Markdown icon (or the code icon, if Markdown was previously set) in the code cell's toolbar to change it.

Once Markdown is set, you can enter Markdown formatted content to the code cell. Once you select another cell or toggle out of the content selection, the Markdown content is rendered in the Notebook Editor.

You can also use the keyboard to change the cell type. When a cell is selected and in command mode, the M key switches the cell type to Markdown and the Y key switches the cell type to code.

Clear output or restart/interrupt the kernel

If you'd like to clear the code cell output or restart/interrupt the kernel, you can accomplish that using the main Notebook Editor toolbar.

Enable/Disable line numbers

You can enable or disable line numbering within a code cell using the L key.

IntelliSense support in the Jupyter Notebook Editor

The Python Jupyter Notebook Editor window has full IntelliSense – code completions, member lists, quick info for methods, and parameter hints. You can be just as productive typing in the Notebook Editor window as you are in the code editor.

Variable explorer and data viewer

Within the Python Notebook Editor, it's possible to view, inspect, and filter the variables within your current Jupyter session. By clicking the Variables icon in the top toolbar after running code and cells, you'll see a list of the current variables, which will automatically update as variables are used in code.

For additional information about your variables, you can also double-click on a row or use the Show variable in data viewer button next to the variable to see a more detailed view of a variable in the Data Viewer. Once open, you can filter the values by searching over the rows.

Note: Variable explorer is enabled by default, but can be turned off in settings (Python > Data Science: Show Jupyter Variable Explorer).

Plot viewer

The Plot Viewer gives you the ability to work more deeply with your plots. In the viewer you can pan, zoom, and navigate plots in the current session. You can also export plots to PDF, SVG, and PNG formats.

Within the Notebook Editor window, double-click any plot to open it in the viewer, or select the plot viewer button on the upper left corner of the plot (visible on hover).

Note: There is support for rendering plots created with matplotlib and Altair.

Debug a Jupyter Notebook

If you need additional debug support in order to diagnose an issue in your code cells, you can export it as a Python file. Once exported as a Python file, the Visual Studio Code debugger lets you step through your code, set breakpoints, examine state, and analyze problems. Using the debugger is a helpful way to find and correct issues in notebook code. To debug your Python file:

  1. In VS Code, if you haven't already, activate a Python environment in which Jupyter is installed.

  2. From your Jupyter Notebook (.ipynb) select the convert button in the main toolbar.

    Once exported, you'll have a .py file with your code that you can use for debugging.

  3. After saving the .py file, to start the debugger, use one of the following options:

    • For the whole Notebook, open the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) and run the Jupyter: Debug Current File in Python Interactive Window command.
    • For an individual cell, use the Debug Cell adornment that appears above the cell. The debugger specifically starts on the code in that cell. By default, Debug Cell just steps into user code. If you want to step into non-user code, you need to uncheck Data Science: Debug Just My Code in the Python extension settings (⌘, (Windows, Linux Ctrl+,)).
  4. To familiarize yourself with the general debugging features of VS Code, such as inspecting variables, setting breakpoints, and other activities, review VS Code debugging.

  5. As you find issues, stop the debugger, correct your code, save the file, and start the debugger again.

  6. When you're satisfied that all your code is correct, use the Python Interactive window to export the Python file as a Jupyter Notebook (.ipynb).

Connect to a remote Jupyter server

You can offload intensive computation in a Jupyter Notebook to other computers by connecting to a remote Jupyter server. Once connected, code cells run on the remote server rather than the local computer.

To connect to a remote Jupyter server:

  1. Run the Jupyter: Specify local or remote Jupyter server for connections command from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

  2. When prompted to Pick how to connect to Jupyter, select Existing: Specify the URI of an existing server.

  3. When prompted to Enter the URI of a Jupyter server, provide the server's URI (hostname) with the authentication token included with a ?token= URL parameter. (If you start the server in the VS Code terminal with an authentication token enabled, the URL with the token typically appears in the terminal output from where you can copy it.) Alternatively, you can specify a username and password after providing the URI.

Note: For added security, Microsoft recommends configuring your Jupyter server with security precautions such as SSL and token support. This helps ensure that requests sent to the Jupyter server are authenticated and connections to the remoter server are encrypted. For guidance about securing a notebook server, see the Jupyter docs.

Latest version

Released:

noTeXbook is a Jupyter notebook theme for Latex lovers ❤

Project description

The Jupyter notebook theme for lovers

The theme aims at combining the flexibility and interactivity of Jupyter notebooks with the unique elegance and sobriety of a LaTeX article.

noTeXbook in a Nutshell

  • Computer Modern fonts for Markdown typesetting;
  • Fira Code (open source) font for Code editor (with ligatures support);
  • Hack (open source) font for Markdown editor (slightly better for text writing, ed.);
  • Multiple Colour Syntax highlighting themes;
  • Extra CSS classes for additional LaTeX-ish formatting use cases (e.g. footnotes, dropcap);
  • Full support for Jupyter Notebooks and JupyterLab (version 2.0x).

Sneak Peek?

Here is a Preview of how [a] noTeXbook looks like!

Setup noTeXbook Theme

The noTeXbook theme is available on PyPi as a Jupyter Notebook(Python) extension:

Once installed, just load the notexbook extension into a Jupyter notebook cell:

The theme can be activated via the %texify IPython magic 🔮:

%texify IPython magic

The %texify IPython magic embeds the noTeXbook theme directly into the current notebook.This results into the following three unique features:

  1. on-demand activation: the theme is enabled only for selected notebooks, without having tochangethe (global) default Jupyter notebook theme.

  2. portable: the theme is embedded directly into the notebook (as the output of a single cell).Therefore, whenever the notebook will be shared and/or exported (e.g. in HTML or PDF via webpdf),the theme will continue to be available, with no extra installation required.Similarly, disabling the theme becomes as easy as clearing the output of the %texify cell.

  3. customisable: the theme allows for an easy customisation (e.g. enabling multiple editor themes)via IPython magic line arguments.

Magic Line Arguments and Theme settings 🪄

The %texify IPython magic 🔮 supports the following arguments:

Examples:

In these settings: (1) the Monaco font will be used for code editor; (2) notebook font size will be set to 18px,and the line height will be 1.3.Note: To actually use the Monaco font for code editor, the font must be available and installed on your local machine.If that is not be the case, the default code mono font (i.e. Fira Code) will be used as a fallback.

In these settings, the newgithub Code Editor theme will be used for code syntax highlighting, substituting thedefault Material Design theme. This theme is inspired by the current code theme on GitHub.

To see the full list of configuration options :

There's more...

The noTeXbook theme is also available as a full-fledgedcustom Jupyter notebook theme (HTML/CSS).This is useful in case you would prefer to enable the theme as the global custom default Jupyter theme.

The noTeXbook theme package is available for download,along with its corresponding documentation.The documentation also contains details on the original CSS design, and instructions on how to defineyour own CSS Editor Colour theme.

Last but not least, Experimental theme integration for Google Colaboratory Notebooks (via theStylus browser extension)is also available. See herefor more information.

noTeXbook shall by thy name

When I had to think to a name for this project, I aimed almost immediately at finding a single word that wouldconvey the idea of integration between LaTeX and notebooks I had in mind.So seemed quite an obvious choice.Moreover, this name itself is also a unique portmanteau(port·man·teau | pȯrt-ˈman-(ˌ)tō) that blends together the words noTeXbook, andnoTeXbook, that is the name of Donald E. Knuth'sbook on TeX.

That was the omen... 🤩.

One!... Two!... Five!

(from: The Holy Hand Grenade - Monty Python and the Holy Grail)

The project wishes to pay a tribute of gratitude (in the name, and in the content) to two of the technologies I do use(and love) the most as a researcher and as a data scientist.

Project Links

  • 📦 PyPi package
  • 🖌 Official GitHub Repo
  • 🚀 Documentation and GitHub Page

Credits

  • The spinzero jupyter theme has been inspirational in the design of the early version of this theme;
  • The idea of overlay of selected cells has been inspired from this custom theme.
  • Inspiration on the choice of Monospace fonts for code and markdown has come from this article
  • Original versions of colour themes for code and markdown editors:

References

(Some links I found useful along the way):

  • Jupyter Server Extension (Particularly useful in earlier version of this project in which fonts where handled as local resources)

Acknowledgments

Special thanks to cdesio, ninadicara, and alanderex for testing earlier versions of the theme!

Release historyRelease notifications | RSS feed

2.0.1

2.0.0

2.0.0rc0 pre-release

1.2.0rc0 pre-release

1.1.5

1.1.5rc0 pre-release

1.1.4

1.1.3

1.1.3rc0 pre-release

1.1.2

1.1.2rc0 pre-release

1.1.1

1.0.0

1.0.0rc0 pre-release

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for notexbook-theme, version 2.0.1
Filename, sizeFile typePython versionUpload dateHashes
Filename, size notexbook_theme-2.0.1-py3-none-any.whl (48.1 kB) File type Wheel Python version py3 Upload dateHashes
Filename, size notexbook-theme-2.0.1.tar.gz (33.3 kB) File type Source Python version None Upload dateHashes
Close

Hashes for notexbook_theme-2.0.1-py3-none-any.whl

Hashes for notexbook_theme-2.0.1-py3-none-any.whl
AlgorithmHash digest
SHA2562cc9d5f991bc0f9ab257196b010eba5a5a3d4b36156f735e1e02bb1cd678c050
MD54c87c633624a4ba622d0c15aa7e9f83d
BLAKE2-256980930148266bfe49129e8fa854618f9701ed2ad0ee18a0c6e3d7cbde2d2607f
Close

Hashes for notexbook-theme-2.0.1.tar.gz

Hashes for notexbook-theme-2.0.1.tar.gz
AlgorithmHash digest
SHA2560a1d01507201959a55291af94d0827790af019d0268c0c9bc539f9125812eb38
MD5e5d18fcdf48f095f0ceffb55a9ddebc4
BLAKE2-256f391dde8fd3eef9f59f542fa2e54e9344d52a6303e90802fe207c13cfba61f14