Best markdown editor for windows and linux

#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX HOW TO#
#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX CODE#
#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX MAC#

On a different note, IMO using Electron for an app is not a bad choice per se. I'll definitely be following the project! :) (By the way, I can't find the 'install' button on that is mentioned in the FAQ.)

Other than that, it looks pretty promising.

#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX CODE#

Since you're the author of Bangle.io and it seems the latter is based on v which in turn is based on ProseMirror(?), why did you decide to make Bangle's interface look like that of VS Code / Monaco? At first I thought this was just VS Code running in the browser.

#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX MAC#

I'm not really advertising Mac support beyond having some files merged from people who did get it to work (. To nitpick a little, I also didn't say I don't think that those who care about licensing issues would use rather, I think that those who don't care about licensing issues and are on Windows would not use it, because there is a Windows-only product that is closed-source which I am unlikely to be able to compete with on that ground. As I see it, in the most natural sense of support, I do have support for Windows, even though it is what I guess you would call Tier 2 support. If someone reports a bug on Windows, I will look into it, and/or spend some time walking them through a workaround (since I do in fact have access to Windows setups). Well, it's not exactly unsustainable - the Github CI continues producing those builds without me having to do anything for it (it in fact didn't break even once in the past year, compared to several breakages on the 'backwards-compatible' Ubuntu 18.04 deb which happened whenever Github changed something about the package bundle available to that image).

#BEST MARKDOWN EDITOR FOR WINDOWS AND LINUX HOW TO#

I just have no idea how to package the result to make it easy to install.) (Regarding Mac, I unfortunately don't have a Mac and neither does anyone who I know well enough to ask to borrow theirs, though someone did in fact contribute homebrew-based build scripts that supposedly work at some point. If you are using Windows, and don't care for 'free (speech and beer)', why would you even want to use anything other than OneNote? I'm somewhat wary of repeating the mistakes of Firefox (and GNOME) of snubbing a likely target demographic to court an unlikely one. The thing is, at least in my eyes, Gtk generally feels terrible on platforms where it is not native (I would in fact even avoid using it in a Qt-based Linux desktop setup, just as I avoid Qt-based applications as far as possible in my Gtk-based one), and at any rate the ports are often lacking even in features (for instance, last I checked, Windows Gtk would not allow me to read tablet pressure information). Thanks for the feedback! I can certainly try to improve the structure of the README, though I'm not sure if I agree with some of your points about giving more priority to non-Linux users. ThatвЂ™s true, and itвЂ™s a great USP for those that require it, but personally I would avoid assuming that itвЂ™s the USP that convinces the masses. You mentioned in this thread that some people donвЂ™t want Electron. You could still keep this technical (and potentially alienating) language in your documentation, but simplifying the README to make it easier for the 90% of your potential audience could make it more popular. You could replace it with a Windows or Mac screenshot, to get people to understand it works on their platform. The Ubuntu screenshots make it look like вЂњLinux onlyвЂќ. Windows binaries mention вЂњењ†4вЂќ, which is very technical and might scare users away. There are no Mac binaries, but Macs are wide-spread among developers. Your installation instructions make it hard for users to pick which one they should choose. You use Linux-lingo, like вЂњfree (speech and beer)вЂќ which many users are unfamiliar with and donвЂ™t know why they should care. You mention why you created it, not what it enables the user to do. What I immediately noticed looking at the README, is that the communication is centered around you and your values, rather than on the end-user: I mean the following as feedback to help you find more users, not as critique I understand where youвЂ™re coming from and this is just how I would personally approach it:

Best markdown editor for windows and linux