Grunt Futuk

19 hours ago, harrismarkc said:

I've exported my own content to a local repository shared by Obsidian.md and Ulysses and backed up via Obsidian backup to GitHub. 

Now it's mainly some domestic files I share with my spouse that are still important in Evernote. I'm going to migrate those somewhere else, probably OneDrive, since we have that anyway. Wife would NEVER use markdown. 😅 But markdown works best for my writing projects and for capturing highlights and notes from multiple sources. 

Tomorrow marks my 12th anniversary with Evernote, so it's a sad time for me. It has served me so well in so many ways. I do see improvements trickling out fairly regularly, but they're just not the one I need. If Evernote would work natively with my locally or web hosted markdown files, I would stay with it. Since the feature request is 8+ years old, I'm giving up. 

 

Thanks for sharing. I think PinkElephant has made a good point in terms of people are free to do whatever they wish to suit their needs.

That said, given the topic, I think it is of benefit to others who are interested in this feature for those that are moving on to share what they are doing instead. No one else needs to follow the same path. Completely free choice.

For me personally, I'm inclined to use obsidian as you do. Used it in anger for a few months now and am very happy with it. Similarly, I already have Onenote as part of a discounted family account. I'm very used to the application from work.

I renewed with Evernote for a year recently. I don't anticipate renewing again.

My biggest challenge is apathy. Going through the effort involved in migrating. No doubt there are other threads covering this topic well.

3 hours ago, PinkElephant said:

We agree in the observation that a better markdown support would be good.

We disagree that your slash /  - way of writing things up would be the standard. I use iaWriter for Markup, one of the major apps for markdown, at least for Mac and iOS.

They use some commands the same way EN does, like hashtags # for the headers, 3 - for a horizontal line or 3 backticks for code.

They just use more commands, and some are more refined, like the possibility to add a programming language to the code block command.

So what you are asking for is not markdown, it is a specific branch of markdown, driven by your individual user experience with other apps. I don’t think if you ask the users in this thread we could agree on which markdown we want - and leave the devs (hypothetically) on their own what to implement.

Not clear who you are replying to. I didn't ask for slash - not part of markdown but a UI feature.

I think that there is a common enough core for markdown for the devs to be able to satisfy the requirement but I recognise one cannot satisfy all of the people all of the time. Academia seems to have embraced markdown well enough for sharing of technical papers (especially including Python and R code, as well as general content, in Jupyter Notebooks).

It seems most of the people on this post asking for markdown want it as a native format standard, preferably as an option over the long-standing format but otherwise (and also)  as an option for document attachments with full preview and edit support.

I recognise the challenge of having built a product on a base format, xhtml, and not wanting to support round-tripping. However, using markdown purely for rapid text entry (lightly supported on the web interface I believe) is possibly useful for some but I expect that would frustrate most experienced markdown users who generally want to be able to focus on rapid note content entry and edit rather than formatting. When I am in note taking mode, I don't want to take my fingers away from main keys to mess with control/command-somekey or menu clicks, it breaks my flow. Markdown is like (X)HTML rather than CSS in this regard.

I and the various teams I am in are not about to cancel our Evernote subscriptions. I value the product for its many features and have not yet found an alternative that fills my use cases despite the markdown frustration. I have looked and will continue to look though.

My experience of using the md file attachment approach, not having a good preview and having to use an alternative editor is not ideal. For me, it somewhat undermines the key note taking focus that I think Evernote has at its core and which is certainly central to be usage.

4 hours ago, PinkElephant said:

Maybe you need to go to the gym, to retrain your muscle memory.

Some small degree of compatibility is more disruptive to my workflow than no compatibility.

I don't want to have to try to retain muscle memory variants for the same challenge and don't really want to compromise the efficiency of entry of an established formatting standard I've used for years and continue to use on a daily basis.

It is also inconvenient not being able to paste markdown content to a note and have it correctly format.

Full support for markdown attachments would be helpful.

Markdown support as an option rather than a default would avoid problems for users not biased to the format.

Another vote for an option to:

• enter content using the full markdown syntax
• RETAINING markdown syntax
• exporting in markdown syntax

Long term subscriber here. Use markdown daily and exploring option for myself and my teams.