admin2/manual_teachbooks
1
0
Fork 0
mirror of https://github.com/TeachBooks/manual.git synced 2026-11-13 23:05:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

equation error

Browse source
This commit is contained in:
Julie Kirsch 2024-11-04 22:05:56 +01:00
parent 82606d0c5b
commit 2bf5f39ead
3 changed files with 13 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

8
book/basic-features/equations.md
View file

@ -1,6 +1,8 @@
# Equations # Equations
Equations can be included in two ways: inline or display mode. To make an inline equation, just put the LaTeX equation between \$-signs. For example, `$F = m \cdot a$` produces: $F = m \cdot a$. Equations can be included in two ways: inline or display mode.
To make an inline equation, just put the LaTeX equation between \$-signs. For example, `$F = m \cdot a$` produces: $F = m \cdot a$.
Display mode equations (the ones that take up a whole line), can be inserted using double \$-signs, like this: Display mode equations (the ones that take up a whole line), can be inserted using double \$-signs, like this:
@ -35,9 +37,9 @@ Resulting in:
$$ $$
F = m \cdot a F = m \cdot a
$$ (newtons_second_law) $$ (newtons_second_law_2)
Equation {eq}`newtons_second_law` can now be referred to. Equation {eq}`newtons_second_law_2` can now be referred to.
> **Note** > **Note**
> >

6
book/workflows/edit_book.md
View file

@ -158,7 +158,8 @@ Demonstration, video available [here](https://youtu.be/bThimdDRXTc)
1. Make some changes to a file in for example VS Code and save them. 1. Make some changes to a file in for example VS Code and save them.
2. Select the files ready to be added to Git-timeline (staging) <br> 2. Select the files ready to be added to Git-timeline (staging).
For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu: For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu:
```{figure} ../images/git-new-file.png ```{figure} ../images/git-new-file.png
@ -167,7 +168,8 @@ The new file appears in the Source Control menu.
``` ```
Notice that there is a green letter U placed besides the file, meaning that our file is untracked. To add a file to the *staging area*, click on the + that appears when you hover over the file. Notice that there is a green letter U placed besides the file, meaning that our file is untracked. To add a file to the *staging area*, click on the + that appears when you hover over the file.
3. Adding changes to the Git-timeline (committing) <br> 3. Adding changes to the Git-timeline (committing)
Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this: Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this:
```{figure} ../images/git-file-added.png ```{figure} ../images/git-file-added.png

BIN
book/workflows/figures/Push_GitHubDesktop2.PNG
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 22 KiB