markdown-mode VS markdown-here

My main authoring tool is then Emacs Markdown Mode (https://jblevins.org/projects/markdown-mode/). For data entry, it comes with some bells and whistles similar to org-mode, like C-c C-l for inserting links etc.

I seldom export my notes for external usage, but if it is the case, I use lowdown (https://kristaps.bsd.lv/lowdown/) which also comes with some nice output targets (among the more unusual are Groff and Terminal). Of cource pandoc (https://pandoc.org/) does a very good job here, too.

Even emacs has a markdown mode:

https://jblevins.org/projects/markdown-mode/

There is markdown-mode if you really prefer it over org. I use it to read markdown files sent by colleagues. It's very powerful, and very well documented, though honestly I don't use much of it's functionality. I use it mainly for it's ability to hide the markup (much like org) and follow hyperlinks.

As much as I love Emacs with markdown-mode, I agree that ghostwriter is the simplest for most users.

I can't find it here https://leanpub.com/markdown-mode/read#leanpub-auto-lists and here https://jblevins.org/projects/markdown-mode/

;; This is a workaround to a bug in markdown-mode: ;; See: https://github.com/jrblevin/markdown-mode/issues/377 ;; https://github.com/joaotavora/eglot/issues/333#issuecomment-913015564 (defun mpolden/gfm-unescape-string (string) "Remove backslash-escape of punctuation characters in STRING." ;; https://github.github.com/gfm/#backslash-escapes (replace-regexp-in-string "[\\]\([][!\"#$%&'()*+,./:;<=>?@\_`{|}~-]\)" "\1" string))

Emacs makes autosaves by default and supports markdown-mode. Usually though it's nicer to put them in a central location by setting backup-directory-alist instead of the default behavior of putting them in directory you're working in of the original file. I stuff them into a directory ~/.saves with (setq backup-directory-alist(("." . "~/.saves")))`.

markdown-mode by Jason Blevins seems not have this function.

You might wish to install the Markdown Mode package. If don't want to do that for some reason, you can tell Emacs that files with names ending in ".md" should be opened in Text Mode by doing something like

github better: https://github.com/jrblevin/markdown-mode

Markdown Cheat Sheet: Markdown syntax guide for creating rich text formatting.

# Heading 1 ## Heading 2 ### Heading 3 Emphasis, aka italics, with *asterisks* or _underscores_. Strong emphasis, aka bold, with **asterisks** or __underscores__. Combined emphasis with **asterisks and _underscores_**. 1. First ordered list item 2. Another item ⋅⋅* Unordered sub-list. 1. Actual numbers don't matter, just that it's a number ⋅⋅1. Ordered sub-list 4. And another item. [I'm an inline-style link](https://www.google.com) [I'm an inline-style link with title](https://www.google.com "Google's Homepage") 

It's definitely a workaround, but I use a Chrome extension to work around this a bit. I use "Markdown Here" to add a "turn Markdown text to formatted text" button to my Chrome bar:

https://markdown-here.com/

And then I use it on plain Markdown text in a GMail compose window. The rich formatted output it produces can then be pasted into a Google Doc, and it comes out really nicely, including support for headers, sub-headers, links, code blocks, and the rest. The main issue is that this is a one-way process, but so long as you keep the .md source somewhere else, lets you share a richly-formatted doc with others for final commenting/editing/etc.

Here is a reference guide for the basic syntax of Markdown. Experiment and enjoy!

Means I made changes to the post formatting using Markdown https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

markdown syntax Can be used to format your read me.

Proper formatting is key to ensure that your post is readable, helpful, and polished. Our post editor uses Markdown and Jekyll Front Matter to format posts.

You can also use more complex Markdown features like lists and tables. Check out the [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) from Adam Pritchard for more information. ### Other JSDoc tags 📚 There are a few other JSDoc tags that you may find useful: - `@function` or `@func`: Documents a function or method. - `@class`: Documents a class constructor. - `@constructor`: Indicates that a function is a constructor for a class. - `@extends` or `@augments`: Indicates that a class or type extends another class or type. - `@implements`: Indicates that a class or type implements an interface. - `@namespace`: Groups related items, such as functions, classes, or types, under a common namespace. - `@memberof`: Specifies that an item belongs to a class, namespace, or module. - `@ignore`: Tells JSDoc to exclude an item from the generated documentation. - `@deprecated`: Marks a function, class, or property as deprecated, indicating it should no longer be used. - `@since`: Documents the version when an item was introduced. And many more. You can find a full list of JSDoc tags [here](https://jsdoc.app/). Ok ok, enough of the theory. Let's see how we can use JSDoc in practice.  ## Using JSDoc in practice 🏄‍♂️ There are a few challenges when starting to use JSDoc in your project. So this section will focus on these challenges and how you can overcome them. ### How to get the most out of JSDoc In this post I'm going to stick with VSCode. If you're using another editor, you can still follow along, but you might have to look up how to configure things in your editor. VSCode has built-in support for JSDoc. This means that you can get a lot of the JSDoc benefits without having to install any additional extensions. But there are a few things that you can do to get even more out of JSDoc. Enabling the checkJs option in your `jsconfig.json` file will make the editor display errors for type mismatches, even in JavaScript files. Place it in the root of your project or in the folder where you want to enable type checking. This file can look like this: ```json { "compilerOptions": { "checkJs": true, } }

Reddit uses Markdown, it's a pretty ubiquitous markup for formatting text online. You'll find it's used in a lot of places. https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet