@the_soulmen @cwage :-) @ScrivenerApp does get this right, which is why I’ve gone back to it, but there’s no markdown syntax highlighting…
-
-
Replying to @Meaningness
@Meaningness I know@ScrivenerApp does this. I was referring to other Markdown editors – these have enough issues with the "one" syntax. ;)1 reply 0 retweets 0 likes -
Replying to @the_soulmen
@the_soulmen@ScrivenerApp Oh, yes, I agree. Could there be a process to standardize the syntax across companies/apps?2 replies 0 retweets 0 likes -
Replying to @Meaningness
@the_soulmen@ScrivenerApp Standardization would be painful in the short run, but a big benefit in the long run.3 replies 0 retweets 0 likes -
Replying to @Meaningness
@Meaningness And a lot of stuff won't work in markup, plain and simple.@ScrivenerApp1 reply 0 retweets 0 likes -
Replying to @the_soulmen
@the_soulmen@ScrivenerApp Well, that’s why having HTML pass through seems important to me.1 reply 0 retweets 0 likes -
Replying to @Meaningness
@the_soulmen@ScrivenerApp But, HTML is my only target, and I understand that LaTeX and others are important for many users.2 replies 0 retweets 0 likes -
Replying to @Meaningness
@Meaningness It's not that. It's notes, goals, keywords, export settings by document etc. – the stuff that makes the *app*.@ScrivenerApp1 reply 0 retweets 0 likes -
Replying to @the_soulmen
@the_soulmen@ScrivenerApp Yes, those are very important—but aren’t they per-file metadata that can be external to the markdown syntax?2 replies 0 retweets 0 likes -
Replying to @Meaningness
@Meaningness Sure. And then good-bye compatibility, and good luck with standardizing the meta-data. ;)@ScrivenerApp1 reply 0 retweets 0 likes
@the_soulmen @ScrivenerApp Hmm… well… content compatibility would still be a significant step in the right direction… but I see your point.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.