The most obvious WYSIWYG competitor for novelWriter is Scrivener, which is similar to Ulysses -- and also shares the limitation that it can only export to Word rather than import. Nevertheless, its testimonials page is filled with praise from people who arguably write more than I do. :)
Some people may need "special characters" they can't type, but I have keybindings for the characters I use.
Grammar checking and corrections is my proofreaders job, not mine. It happens after I've converted my document and sent it off.
Macros are supported in pretty much every editor I've ever used for plain-text. I use lots of macros, but exactly zero of them for my novels.
I don't need to send and receive documents with no conversion needed. I do one export when I'm done with my first draft, and then I edit and do one more export before handing it over to my proofreader. Then, sure, I review those changes in Librewriter. The proportion of my time that takes is tiny. It'd be nice not to have to, but I'd take that over having to work in a word processor during writing any day.
> No offense but you don't sound like someone who writes a lot?
As someone who has written several novels, that's how your comment came across to me. At the same time I know novelists range from the pen and paper type (e.g. Gaiman, King to give two examples discussed in this thread) up to wanting word processors with all bells and whistles - it's very much down to taste.
* Inserting special characters: personally I don't find those "character choosing" windows to be very convenient. Hunt and peck is a slow way to type! Anyway, you can do this in Markdown with either Unicode (if you have the right keyboard) or you can write HTML escape codes (&tm; etc.)
* Automatic (grammar/spelling). I don't like check as I type, but sure. Anyway, Emacs provides this if I want it.
* Macros. Hello? Emacs? (Also, Pandoc has a scripting interface.)
I may not be published yet but I've written my own book. I've also published books for other people. I did both of those with a Markdown-based toolchain. It works.
Edit: Just to prove the point: https://www.amazon.com/dp/0692553916 . Go see for yourself how the book is formatted.
(Also, I wrote a Markdown-to-ePub script, too! Although I don't think anything I've got up online uses it anymore.)
I'm a Markdown fan, but really there _are_ better solutions for book writing that maintain the ease that Markdown brings. Things like ASCIIDoc.
Also, if emacs was good enough for Neal Stephenson, I'm sold...though I hear he uses Scrivener now!
No offense but you don't sound like someone who writes a lot?