From: Max Nikulin <manikulin@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>, Bastien <bzg@gnu.org>
Subject: Re: Some links in online manual do not work
Date: Wed, 12 Oct 2022 10:06:14 +0700 [thread overview]
Message-ID: <b7c8d23b-79d1-b864-cdc5-a2f0afc4e811@gmail.com> (raw)
In-Reply-To: <871qrei938.fsf@gnu.org>
On 12/10/2022 00:06, Bastien Guerry wrote:
> Max Nikulin writes:
>> More:
>
> Fixed, thanks!
Unfortunately some redirection targets still respond with 301
301 https://orgmode.org/manual/Dates-and-Times.html
301 https://orgmode.org/manual/Deadlines-and-Scheduling.html
301 https://orgmode.org/manual/Emphasis-and-Monospace.html
301 https://orgmode.org/manual/Export-in-Foreign-Buffers.html
301 https://orgmode.org/manual/HTML-export-commands.html
301 https://orgmode.org/manual/Properties-and-Columns.html
If redirection directives were included as separate files then it would
be possible to just check them by a command like
awk '{ if ($NF >= 3) print $3; }' /tmp/manual.txt |
xargs --replace -- \
curl --head --write-out '%{http_code} %{url_effective}\n' \
--silent --show-error --output /dev/null \
'https://orgmode.org/manual/{}'
and the same for the guide.
Original proposal to add redirections contained an s-expression with
mappings. I would consider tracking it in the main Org repository. I
believe, list of info nodes in the released manual should be added to it
as known names. The idea is to make it easier to add redirections before
new release. With such list as an input, a simple script could detect
nodes absent in new release but existed in the earlier one. Another case
is names appeared again making redirection rules obsolete.
next prev parent reply other threads:[~2022-10-12 3:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 20:00 Some links in online manual do not work Tim Landscheidt
2022-10-02 21:04 ` Tim Cross
2022-10-03 3:52 ` Ihor Radchenko
2022-10-05 17:48 ` Tim Landscheidt
2022-10-06 4:17 ` Ihor Radchenko
2022-10-06 12:14 ` Tim Landscheidt
2022-10-07 15:33 ` Bastien Guerry
2022-10-07 19:50 ` Tim Landscheidt
2022-10-08 6:28 ` Ihor Radchenko
2022-10-08 12:37 ` Max Nikulin
2022-10-11 5:37 ` Bastien
2022-10-11 6:57 ` Max Nikulin
2022-10-11 7:57 ` Bastien
2022-10-11 8:33 ` Max Nikulin
2022-10-11 9:09 ` Bastien
2022-10-11 16:51 ` Max Nikulin
2022-10-11 17:06 ` Bastien Guerry
2022-10-12 3:06 ` Max Nikulin [this message]
2022-10-12 4:11 ` Bastien Guerry
2022-10-12 5:14 ` Max Nikulin
2022-10-16 12:11 ` Tim Landscheidt
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7c8d23b-79d1-b864-cdc5-a2f0afc4e811@gmail.com \
--to=manikulin@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).