Evernote Note File Extension

[nfarrar]

I'm currently saving notes as with a .md extension in sublime text, then manually adding meta data, then sending to evernote. Prior to "sending to evernote" the file type is listed as markdown. After sending to evernote, the file type is "Evernote Note".

In my Evernote.sublime-settings file I set the following option:

"update_on_save": "true"

When I close the note and reopen it, it opens as a markdown file, not an "Evernote Note".
If I update the file, the changes are not automatically synchronized. If I reissue "send to evernote" they are, but again I have to do this every time.

I assume this is because I'm using the standard .md extension (which sublime automatically detects as a "Markdown" filetype, rather than an "Evernote Note." My guess is that there is an evernote note filetype specific file extension that I could use, but I am unsure what it is - I looked through the source, but was unsure where to look for this bindings and did not find it.

[bordaigorl]

The "predefined" extension is .enmd (it's hardcoded in the Evernote.tmLanguage file) but you can make up your own and then associate it to the Evernote note syntax by using the syntax menu of ST.
This is a workaround until I find some time to improve the support for workflows based on local copies of the notes (see #1 )

[nfarrar]

Thank you. :) I'm still trying to figure out my workflow with this tool. I read through the notes on that link and it raised several questions about how sublime-evernote works now and how it will work in the future.

My workflow has typically been to maintain a store of .md notes synchronized with dropbox and then a separate set of notes synchronized with evernote.

At the moment, I've added a separate directory in my dropbox notes directory - then started moving some notes into that folder with a .enmd extension, defining the front matter using the snippet (title, notebook, tags), and then sending it to evernote.

I've noticed the following behaviors that are identifying to me that the workflow I'm trying to use probably isn't going to work ...

1. If the notebook I'm trying to add the note to doesn't exist, it won't be sent. I have to go and create the notebook first on the web client.
2. If I open the note on a different computer (the sync'd .enmd file using dropbox) and modify the note, the sync is broken.
3. If I make changes to the note in the web client and in sublime, the sync appears to be broken. If I resend the note from sublime, a new note is created.
4. If I rename the note in sublime, the sync is broken. If I resend from sublime, a new note is created.
5. If I rename the title in the frontmatter, the sync is broken. If I resend from sublime, a new note is created.

The issues with syncing simultatenously via dropbox and sublime-evernote indicate that I will not be able to store the local notes in a dropbox synchronized folder.

There doesn't appear to be anyway to sync notebook to a local directory. I was hoping it would be possible to pull down an entire notebook to the local computer and have the 2-way sync set up on all those notes downloaded (or automatically set on any local notes created in that directory) such that all notes in that directory would be kept in sync.

Anyway, thanks for this plugin. I'm still just trying to figure out how to use it effectively. :)

[bordaigorl]

Thanks for the feedback @nfarrar !
The reason why this has not been already implemented is that it is tricky to get this right from a usability point of view. I haven't got much feedback on which features users would like to have apart from the discussion in #1.

Currently the guid (an id uniquely identifying a note) of a note is not stored in the metadata so if you save your note in a file and later edit it there is currently no way to tell the plugin which note it should update.

So the fully supported workflow for existing notes is: open-from-cloud, edit in ST, update-to-cloud.
Local copies can be used but if you open one it will essentially be treated as any markdown document and not linked to a cloud-stored one.

However I intend to integrate some sort of support for this in the next version (no known time-frame). If you have any ideas I'd be glad to know (either here or in the related issue).
I could also start a wiki page where we keep track of the progress.

The idea so far is: store the guid in the metadata and offer a command to re-retrieve the note from the cloud. I do not intend to implement any conflict-resolving-synch command, unless somebody comes up with a neat way of doing so.

[MaokaiLin]

A simple solution might be to add a "replacement" command. Basically, one can open a local md file, replace the same file on the cloud, then keep working locally.