![]()
Just create a new document, give it a title and away you go.” Before the web arrived, using a desktop text processor to format rich text was the norm. Markdown: “Oh, this one’s easy – open a new document in the text editor and start typing.” Or use an online markdown editor such as dillinger.io that supports synchronization with Dropbox, Google Drive and Github. ![]() Mark and Rich will flex their muscles to see who can create and publish content faster and easier. Supported by: the Atlassian Confluence collaboration platform and wiki, and other cloud-based content creation tools such as Google Docs. Rich’s strengths: advanced content formatting skills, editor shortcuts (and he’s not afraid to use them), and immediate availability of the resulting document. Rich doesn’t see many advantages in separating editing from viewing: “Juggling markup syntax? What is this, the ‘90s?” In the right corner: Richard “Rich Text” Formatting – used by millions of casual writers who want to see their results instantly. Emacs), and file repositories such as Github. Supported by: Jekyll, your favorite text editor (e.g. #WRITE LINES OF YOUR FAVORITE TEXT EDITOR CODE#Mark’s strengths: code handling, offline availability, minimalism and something he likes to call “bringing it down.” md, but you don’t need an MD to understand it – the syntax is so simple that any developer in the world can adapt to it with ease. You can recognize Markdown easily by his file extension. Mark “Markdown” Down, lightweight champion of the world for writing web content into plain text files. #WRITE LINES OF YOUR FAVORITE TEXT EDITOR UPDATE#Update : If you use Visual Studio Code as your main editor, the setup is even more simple and this is actually is the more recommended setup now since this post was published (Visual Studio Code can be downloaded from the link at the bottom of this post).Today, we’re going to settle the question once and for all – which is superior? Documentation in a plain-text editor using Markdown, or creating content in a rich-text editor the WYSIWYG (what you see is what you get) way? How will it be decided, you ask? A good, clean head-to-head fight! Mr. ![]() You can certainly substitute the path or program name with whatever text editor you have. Sublime Text is used as an example just because it’s available on Windows, OSX, and Linux. Now, if you want to see if the text editor is set correctly, just type in this command: git config -global -listĪnd you should see the core.editor value listed to look like this: macOS / Linux git config -global core.editor "subl -n -w" ![]() (i.e., "'C:\Program Files\Sublime Text 4\sublime_text.exe' -w" works the same way as in the example above). You can use single quote or double quotes interchangeably as long as they’re consistent You want to enclose the whole path of your editor within the quotes, then wrap the whole argument with the flag with the other. Pay attention to the placement of single quote (‘) and double quotes (“). #WRITE LINES OF YOUR FAVORITE TEXT EDITOR WINDOWS#Windows git config -global core.editor '"C:\Program Files\Sublime Text 4\sublime_text.exe" -w' ![]() The -w basically is to tell Git to wait until all operations within the text editor is done before Git can continue to do its thing afterwards. What you need to do is set the value of core.editor to the program file of your editor and add a flag -w at the end. After installing Git and initially configuring it, you can further configure it to use your favorite text editor as the default. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |