Have people looked at sourcehut (https://sourcehut.org)? While it's still in
alpha, and so has a number of rough edges, it seems pretty promising. Sourcehut
is trying to build a platform with accessible web uis that is backed by mailing
lists. Just annother option to consider, though there is no ur
Here are a number of fixes to ob-C.el. There is still probably a bunch
of general cleanup to do in this file, but these changes make it work
for me.
0001-ob-C.el-Fix-a-number-a-bugs-related-to-table-paramet.patch
Description: Binary data
I have collected below some quotations to try to represent the general
sentiments expressed so far in the conversation, upon which I would like to
express some thoughts. Most of these have been repeated several times in spirit,
so they are not just the opinions of the listed authors.
Daniele Nicol
Dr. Arne Babenhauserheide wrote:
> Why should this be in a separate document? The obvious place for a
> standard is worg, and the way forward is to improve what’s there.
It does not necessarily need to be in a separate file, and if it is it should be
in worg or another communally owned place, an
Hi all,
Thank you for your comments on my post "Thoughts on the Standardization of Org."
I appreciate all the feedback you have given me, I feel that, based off of the
responses, there have been a number of miscommunications as to my intention.
First, I did not mean the post to be primarily an ar
rg-mode is a
very large beast to standardize, and it can only be done incrementally, or it is
doomed to fail.
> On Sat, Oct 31, 2020 at 8:22 PM Asa Zeren wrote:
> > this is impossible. If org catches on before it is standardized, we end up
> > in the situation of Markdown, with many c
acs. It should become a
universal markup format, which just happens to have had many tools first
implemented for Emacs (even if Emacs still will probably remain the best way to
edit org files).
Best,
Asa
On Sat, Oct 31, 2020 at 8:40 PM Dr. Arne Babenhauserheide
wrote:
>
>
> Asa Zeren writ
nments,
such as "Source Blocks" or "Standard Header Properties" (specifying
#+title, #+author, etc.)
I would appreciate thoughts on these ideas about how to develop and
org specification.
Thanks for reading,
Asa Zeren
