I mainly intended to say I think Org is much more standardized than Markdown because there is at least a unique reference implementation and a unique reference document describing the format. Whereas for Markdown, you do have many slightly different implementations and attempts at standardization, despite Markdown being an order of magnitude simpler.
In places like GitLab, people are taking advantage of this by running Emacs in batch mode inside a container to effectively use the reference implementation for export-to-other-formats purposes.
It's not an ideal situation, though. And I hope someone creates a truly independent library. There is a Ruby parser employed by GitHub and GitLab which covers a decent subset of Org. Furthermore, Orgzly and vim-orgmode are pretty much closer to implementing a much bigger subset of Org.
At this point, Markdown does have a real standard, CommonMark. GitHub-Flavored Markdown was modified to become an extension to CommonMark (it's literally just a few extra features on top of CommonMark at this point). There are of course non-CommonMark-based implementations still (such as MultiMarkdown) but at this point anyone adding Markdown support to a project should be using CommonMark or GFM.
As a side-note: As a regular emacs and org-mode user, not a fan of the date format and lack of flexibility in picking repeating schedules.
I haven't used repeaters that much, but I was under the impression that they were very, very flexible. At least much more flexible than a typical todo app. What don't you like about them?
For reference, here's some documentation about them:
https://orgmode.org/manual/Repeated-tasks.html
https://orgmode.org/manual/Timestamps.html#Timestamps
https://www.gnu.org/software/emacs/manual/html_node/org/Time...
https://www.gnu.org/software/emacs/manual/html_node/emacs/Se...
I agree that it could be better, but I'd be surprised if it was something that was typically expressible in other programs. So the fact that it's doable at all seems great, and does indicate that it's flexible.
Since you said it lacked flexibility, I was wondering if you had an example of something that was not expressible in Emacs org-mode but that was expressible elsewhere.
> Moreover, diary-float sexp expressions are most definitely not helping the argument of usability outside emacs.
Well, it's not elisp, is it? It's just sexps. It may as well be JSON, but more concise.
Just to clarify, I am not criticizing org-mode for not implementing in comparison to others. The lack of flexibility I suggest is the date format itself, which does not even allow specifying 2nd Thursday of the month for example. diary-float allows it, but is not intuitive.
I intend to write an interactive scheduling tool for org-mode when I can spare the time. Like regex-builder, but for dates.
&%%(let ((dayname (calendar-day-of-week date))
(day (cadr date)))
(or (and (= day 21) (memq dayname '(1 2 3 4 5)))
(and (memq day '(19 20)) (= dayname 5)))
) Pay check deposited
I don't know if this is doable from org-mode but it seems to me like this could be a viable, more readable alternative to diary-float.For your example of 2nd Thursday from every month, instead of:
%%(dairy-float t 4 2)
you could have: &%%(let ((day-of-week (calendar-day-name date))
(day (cadr date)))
(and (= day-of-week "Thursday")
(> day 7)
(<= day 14)))
That's seems more readable to someone that hasn't read what the parameters of dairy-float mean. For your second example of every 2nd and 4th Thursday: &%%(let ((day-of-week (calendar-day-name date))
(day (cadr date)))
(and (= day-of-week "Thursday")
(or (and (> day 7) (<= day 14))
(and (> day 21) (<= day 28)))))
It being a programming language might make it unintuitive to use by a non-programmer, but I don't think you can get anymore flexible than this. Also, org-mode's attractiveness being that everything is in plain text, I'm not sure there is a syntax that would be more readable than properly written code.[1] https://www.gnu.org/software/emacs/manual/html_node/emacs/Se...
But I wish we had something like Remind [1] where you can define events based on e.g. Easter dates, skip recurring events if they fall into a holiday or move them according to a rule.
In particular, I hate I have to change all bank holidays every year. Remind got this right. There's some added complexity, though.
A nice thing about Org is the pragmatic way it deals with recurring events. You clone them and adjust at will, manually. So you can deal with really odd ways of re-scheduling meetings.
[0] https://www.timeanddate.com/calendar/determining-easter-date...
However, I'd prefer if all these things were merged into mainline.
If I did, I'd be eager to correct them. What were they?
> I love Markdown, but Org does a lot more
I agree. Org is great, as I said above.
I don't think I criticise Org anywhere in my comment, I was purely questioning the points in the article about non-Emacs use.