From: Ihor Radchenko <yantar92@gmail.com>
To: c.buhtz@posteo.jp, Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy (was: Multiline list entries / Is auto-fill-mode in org(roam) usual?)
Date: Mon, 04 Apr 2022 20:31:57 +0800 [thread overview]
Message-ID: <87o81hf2rm.fsf@localhost> (raw)
In-Reply-To: <9ab81ac1c7c4a2e26187cf50ee8f3000@posteo.de>
Dear all,
We currently have two versions of Org syntax in WORG:
1. https://orgmode.org/worg/dev/org-syntax.html (old, not always accurate)
2. https://orgmode.org/worg/dev/org-syntax-edited.html (new, being
discussed in https://orgmode.org/list/871r1g936z.fsf@gmail.com)
The old syntax page is apparently ranked higher by search engines,
creating confusion among users (see the above discussion and the below
message sent off-list).
Maybe we can move org-syntax-edited in place of org-syntax at this
point? I personally think that Tecosaur's version is strictly superior
to the old draft, even though is can still be further improved.
WDYT?
Best,
Ihor
c.buhtz@posteo.jp writes:
> Am 04.04.2022 09:44 schrieb Ihor Radchenko:
>> WORG is also official, though serves more like a wiki and not as
>> official as the manual. In your particular case, we are currently in
>> the
>> process of updating the WORG syntax page.
>> https://orgmode.org/worg/dev/org-syntax.html is an old page explicitly
>> stating that it is a draft ("Org Syntax (draft)"). I recommend using
>> https://orgmode.org/worg/dev/org-syntax-edited.html#Items if you want
>> to
>> check more up-to-date formal syntax description.
>
> For newbies (and for me) it is unclear why there are two "version" of
> syntax documents exist. The is confusing.
>
> Minimally the worg-version should point to the "official" org-version
> and back. When googling org things the worg pages are on top most of the
> time.
next prev parent reply other threads:[~2022-04-04 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 20:28 Multiline list entries / Is auto-fill-mode in org(roam) usual? c.buhtz
2022-04-03 21:02 ` c.buhtz
2022-04-04 13:25 ` c.buhtz
2022-04-04 15:49 ` Tim Cross
2022-04-04 18:13 ` c.buhtz
2022-04-05 1:02 ` Tim Cross
2022-04-04 3:42 ` Kaushal Modi
2022-04-04 4:06 ` Ihor Radchenko
2022-04-04 4:26 ` Kaushal Modi
2022-04-04 7:16 ` c.buhtz
2022-04-04 7:44 ` Ihor Radchenko
[not found] ` <9ab81ac1c7c4a2e26187cf50ee8f3000@posteo.de>
2022-04-04 12:31 ` Ihor Radchenko [this message]
2022-04-04 16:08 ` Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy Nicolas Goaziou
2022-04-04 17:06 ` Timothy
2022-04-05 6:24 ` Ihor Radchenko
2022-04-05 6:56 ` Timothy
2022-04-05 7:26 ` Ihor Radchenko
2022-04-05 7:46 ` Timothy
2022-04-04 14:32 ` Multiline list entries / Is auto-fill-mode in org(roam) usual? c.buhtz
2022-04-04 15:02 ` Kaushal Modi
2022-04-04 15:54 ` Tim Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o81hf2rm.fsf@localhost \
--to=yantar92@gmail.com \
--cc=c.buhtz@posteo.jp \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tecosaur@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.