From: Bastien <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: "Rudolf Adamkovič" <firstname.lastname@example.org>, email@example.com
Subject: Re: [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)]
Date: Sun, 29 May 2022 12:08:38 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <87y1zktfg4.fsf@localhost> (Ihor Radchenko's message of "Mon, 02 May 2022 18:08:11 +0800")
the https://orgmode.org/org-info.js file is available again, thanks
for reporting this.
Ihor Radchenko <email@example.com> writes:
> Apparently nobody touched this for a very long time. The last change
> in this area was 9 years ago.
Indeed, it would be good to have someone as a maintainer. I suspect
the code is stable is still useful to some users.
> I do not fully understand why it is hosted in worg. We mention it in the
> manual and support in the core. The script is licensed under GPL.
> Is there any reason to keep it out of the main Org repo?
I'd like the main Org repository to focus on Org's core, i.e. what is
sync'ed with GNU Emacs core.
I think this nice js hack should live in a dedicated repository, along
with a dedicated HTML exporter that enables it.
>> P.S. If someone decides to fix this, please consider adding a test. Without
>> it, sooner or later, someone will waste their time again.
> It is a good idea, though I am not sure if it is appropriate to add
> network staff into Org tests directly.
I'm sure it's not a good idea to add network-dependent tests :)
Also, we don't want everyone to use https://orgmode.org/org-info.js as
the source for the script, as this would put the server under too much
load pressure, people should rather host the script themselves.
next prev parent reply other threads:[~2022-05-29 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:12 [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)] Rudolf Adamkovič
2022-05-02 10:08 ` Ihor Radchenko
2022-05-29 10:08 ` Bastien [this message]
2022-05-30 3:29 ` Ihor Radchenko
2022-05-31 6:51 ` Bastien
2022-06-12 11:50 ` Bastien
2022-06-14 4:20 ` Ihor Radchenko
2022-06-14 7:20 ` Bastien
2022-06-21 14:26 ` Ihor Radchenko
2022-06-22 3:41 ` Bastien
2022-06-22 4:11 ` Ihor Radchenko
2022-09-18 8:13 ` Bastien
2022-09-20 8:31 ` Ihor Radchenko
2022-09-20 9:01 ` Bastien
2022-09-20 9:26 ` Ihor Radchenko
2022-09-21 20:23 ` Tim Cross
2022-09-22 15:32 ` Bastien
2022-10-01 12:24 ` Bastien Guerry
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).