Sidenotes (using HTML format)

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequatI'm a sidenote about that weird sentence over there. . Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborumI'm bold and I'm italic. 👍 Add text.

But I must explain to you how all this mistaken idea of denouncing pleasure and praising pain was born and I will give you a complete account of the system, and expound the actual teachings of the great explorer of the truth, the master-builder of human happiness. No one rejectsNew sidenote, dislikes, or avoids pleasure itself, because it is pleasure, but because those who do not know how to pursue pleasure rationally encounter consequences that are extremely painful.

This is a sentence. Following that sentence is this sentence. It's completely invetible that it would be that wayI'm a margin note with no number... Japanese Language. One cannot imagine it any other way. This sentence was left breathless by the previous one.

Nor again is there anyone who loves or pursues or desires to obtain pain of itself, because it is pain, but because occasionally circumstances occur in which toil and pain can procure him some great pleasure. To take a trivial example, which of us ever undertakes laborious physical exercise, except to obtain some advantage from it? But who has any right to find fault with a man who chooses to enjoy a pleasure that has no annoying consequences, or one who avoids a pain that produces no resultant pleasure?

Sed ut perspiciatisAnd this is much longer text, pushing the next note down. There once was a man from Nantucket who went down a well in a bucket. unde omnis iste natus error sit voluptatemI'm a sidenote that got pushed down by the previous, longer one. accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt.

Lorem ipsum dolor sit amet, consectetur adipiscing elitHey, check it out. This is an external link. Woah! , sed do eiusmod tempor incididunt ut labore et dolore magna aliquaThis is an Internal Obsidian link. So cool....

Footnotes Sidenotes Test

More Tests

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

Words and more words go here.

Yadda yadda yadda.

Stuff and more stuff.

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

This might also be a sentence and stuff.Hey check it out. This is an external link. Woah.
And this is much longer text, pushing the next one down. There once was a man from Nantucket who went down a well in a bucket. Add text. Testing. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test.

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

This might also be a sentence sometimes.Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Testing stuff more. Testing. Test. Test. Test. Test. This is some more stuff. If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

If you keep markdownEditHotkeys and the user also has Cmd+B bound to Obsidian’s bold command, you can get “double-bold” in theory. In practice, your CM binding uses preventDefault: true and should generally win, but if you want to fully respect user bindings, you’d remove markdownEditHotkeys and rely on Obsidian commands via activeEditor. (Most people keep the CM bindings because they’re deterministic.)

This might also be a sentence.Testing stuff more times. Test. Testing stuff more. Testing. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff. Test. Test. This is some more stuff.

Stuff.