Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain the update date when importing to evernote #13

Open
rmcgranaghan opened this issue Jun 18, 2024 · 2 comments
Open

Maintain the update date when importing to evernote #13

rmcgranaghan opened this issue Jun 18, 2024 · 2 comments

Comments

@rmcgranaghan
Copy link

Thank you for this function - it was extraordinarily useful!

Quick feature request (or request for a workaround you might already have): When I import the output .enex file to Evernote it keeps the date and time when I do the import as the last update for each note (so they all have the same date and time and sorting by 'last updated' is no longer helpful). Is there any way to maintain the last updated date and time of the note in the md2enex tool?

The tool as it works now keeps the date created, but not the date last updated.

@karloskalcium
Copy link
Owner

@rmcgranaghan Hmm this is strange. It was written to handle this case - I am grabbing the modification time of the markdown file as well as the creation time, and embedding this into the .enex. You can see this here for example:

https://github.com/karloskalcium/md2enex/blob/master/tests/test1/target.enex

If your markdown file itself was modified (e.g. if it was in some other tool, and was exported), then the modification time would be the moment you exported it.

If you can send a more detailed example I can look into it but it should do the right thing.

What OS are you using? There are some difficulties with Linux in getting the creation date for example.

@karloskalcium
Copy link
Owner

@rmcgranaghan I've updated the code to try one additional step to get creation dates in Linux. Please give the latest version a try and see if it is working properly - thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants