Markdown with Eclipse.
Markdown is not a replacement for HTML. Its small syntax is to make it easy to read, write, edit prose and address issues that can be conveyed in plain text. Unlike block-level HTML tags, Markdown syntax is processed within span-level tags.
The eclipse version with Aptana plugin colors even a smaller set of markdown coding. Still it is good enough for my use and here are the syntax I have tried:
- A paragraph is simply one or more consecutive lines of text, separated by one or more blank lines. Normal paragraphs should not be indented with spaces or tabs.
- # at the begin of a line indicates a header i.e. h1, h2...
- ' (single quote) and " (double quote) colors a quoted string.
- 1., 2., 3., ..., -, * and + at the begining of a line color it as a list item.
- A string enclosed by a * or _ on each side is italicised. I.e. *italic* and _underscore_
- A string enclosed by ** or __ (two underscores) on each side is bolded. I.e. **bold** or __two underscores__
- String enclosed by square brackets is a link. I.e [link]
There might be more but the above coloring is enough for me to put some coloring scheme on text and ease my scan for key words.
The markdown coloring was not set by default on my eclipse. I had to go to Preferences> Aptana Studio> Publishing> Themes to look for and change various Markdown settings. Once set, eclipse automatically colors any file of the type .md, for example myfile.md
To search, my first thougts were along setting up some type of database such as SQLite, MySQL... but they seemed like overkills and would need more maintenance than I wanted. I have been experimenting with keeping all my notes as .md files in a project. To seach for a word or phrase, I open any file, type and hilite what to be searched, click on eclipse's search button, select the project to be search and then pick the type of search. It is simple and works well.
Insights of the past for the present
ON THE BOOK SHELF
May your insights be worthy.