From: ian martins <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Cc: Org-Mode mailing list <firstname.lastname@example.org>
Subject: Re: [PATCH] org-manual.org: Remove languages list and update worg link
Date: Sun, 8 Nov 2020 07:47:38 -0500 [thread overview]
Message-ID: <CAC=rjb566cj5opQW8B73HWC-i+GswRZBanK=Zyo7nuNJN48--Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
I pushed two days ago, but the manual hasn't updated yet. I guess it
doesn't update on git hooks like worg. is there a scheduled process or is
there something that must be done?
On Thu, Nov 5, 2020 at 11:03 PM Kyle Meyer <email@example.com> wrote:
> ian martins writes:
> > Subject: [PATCH] org-manual.org: Remove language list and fix Worg link
> > * doc/org-manual.org: Remove the language list and fix the Worg link
> > since the languages page has moved. Renumber footnotes.
> > The language list in the manual is missing many languages. Rather
> > than trying to keep the list up to date in two places that link to
> > each other, this removes the list from the manual which is updated
> > less frequently. There were a few footnotes in the table, so this
> > also renumbers the remaining footnotes.
> Sounds like a good idea to me.
> > The languages page was moved in Worg to make it the index page in the
> > languages directory. This updates the link in the manual to point to
> > its new location.
> > ---
> > doc/org-manual.org | 103 +++++++++++++++++----------------------------
> > 1 file changed, 38 insertions(+), 65 deletions(-)
> > -[fn:160] Note that, for ~org-odd-levels-only~, a level number
> > +[fn:158] Note that, for ~org-odd-levels-only~, a level number
> > corresponds to order in the hierarchy, not to the number of stars.
> > [fn:161] If you move entries or Org files from one directory to
> Hmm, the 158 to 161 jump after your renumbering caught my eye, but it
> looks like it's orthogonal to your changes. There was a bad merge
> conflict resolution in 9410fbe06 that unlinked this definition from its
> reference (one of the two [fn:89]s). I'll clean it up after your
> changes land.
[-- Attachment #2: Type: text/html, Size: 2433 bytes --]
next prev parent reply other threads:[~2020-11-08 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 13:39 [PATCH] org-manual.org: Remove languages list and update worg link ian martins
2020-11-05 2:29 ` ian martins
2020-11-06 4:03 ` Kyle Meyer
2020-11-08 12:47 ` ian martins [this message]
2020-11-09 3:59 ` Kyle Meyer
2020-11-11 9:05 ` Bastien
2020-12-14 6:08 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).