I do see a handful of people using non-ASCII identifiers in their code, but that's rare. Much more common is explanatory comments, docstrings, etc. in the local language. To require those to be ASCII would be a non-starter.
> If, in the context of cooperating together, you say "should I go ahead?" and they just say "no" with nothing else, most people would not interpret that as "don't go ahead".
I think Orgro's parser[0] is pretty complete at this point. If you can find an Org syntax that Orgro doesn't support, please let me know.
However I should be very clear here:
> they can't support any of the features that require the rest of emacs to be present which is a lot of of the value
This is absolutely true and unlikely to change anytime soon. As I'm sure you know, parsing the syntax correctly is not at all the same as supporting all of the features built on top of the AST.
This is the modern-day equivalent of asking the genie from the magic lamp for something, and getting something else that meets the letter but not the spirit of the request.
The smart thing to do is realize you don't know what you're doing, and don't rely on the genie at all. Or hire someone who knows how to tame the genie. Or whatever; someone else put it better: you fucked around and you found out. lol
I publish an app to the App Store, Google Play, and F-Droid. For years, F-Droid took absolute ages to reflect a new release.
People used to criticize the walled gardens for having capricious reviewers and slow review times, but I found F-Droid much more frustrating to get approval from and much slower to get a release out.
So this development is much appreciated. In fact I had an inkling that build times had improved recently when an update made it out to F-Droid in only a day or two.
reply