Jump to content

markdown to evernote service

Recommended Posts

Hi - I wanted to try to make at least one significant contribution to the beta, so here's a workflow that allows you to send selected markdown formatted text to Evernote via a hotkey.


Not all my own work I'm sorry to say, but a flow I've wanted for a while and only investigated properly recently. (I spend a lot of time taking notes and writing up reports. Markdown support in Evernote would be ideal, but until then - Alfred comes to the rescue)


It requires the installation of multimarkdown - available here: http://fletcherpenney.net/multimarkdown

It reuses a script available here: http://nsuserview.kopischke.net/post/6223792409/i-can-has-some-markdown





Evernote note title, notebook and tags can all be specified via markdown metadata. All other text is then imported to Evernote as HTML. 


Workflow available to download here: http://d.pr/f/2pUe


Updated: Corrected issue with non-escaped double quotes

Link to comment
  • 11 months later...

I have some markdown that isn't being parsed correctly. It appears as though the back ticks ` are causing the code inside the back ticks to be executed instead of treated as a code block in markdown.


Here is the markdown:

## Git repo with existing sources

If you've got local source code you want to add to a new remote new git repository without 'cloning' the remote first, do the following (I often do this - you create your remote empty repository in bitbucket/github, then push up your source)

If your local GIT repo is already set up, skips steps 2 and 3

 1. Create the remote repository, and get the URL such as git@github.com:/youruser/somename.git or https://github.com/youruser/somename.git

 2. Locally, at the root directory of your source, `git init`

 3. Locally, add and commit what you want in your initial repo (for everything, `git add .` then `git commit -m 'initial commit comment'`)

 4. To attach your remote repo with the name 'origin' `git remote add origin [URL From Step 1]`

 5. Execute `git pull origin master` to pull the remote branch so that they are in sync.

 6. to push up your master branch (change master to something else for a different branch): `git push origin master`

I love the idea of this workflow! Do you think you can sort this out so that I can use it more often?



Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...