emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: "Rudolf Adamkovič" <salutis@me.com>, Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)]
Date: Mon, 02 May 2022 18:08:11 +0800	[thread overview]
Message-ID: <87y1zktfg4.fsf@localhost> (raw)
In-Reply-To: <m2sfpse1r8.fsf@me.com>

Rudolf Adamkovič <salutis@me.com> writes:

> I followed the instructions at ...
>
> https://orgmode.org/manual/JavaScript-support.html
>
> ... adding the following line to my Org file:
>
> #+INFOJS_OPT: view:info toc:nil
>
> The HTML now contains ...
>
> <script src="https://orgmode.org/org-info.js">
> // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&amp;dn=gpl-3.0.txt GPL-v3-or-Later
> // @license-end
> </script>
>
> ... but https://orgmode.org/org-info.js gives 404.

Confirmed.

The script is now hosted at
https://orgmode.org/worg/code/org-info-js/org-info.js

Apparently nobody touched this for a very long time. The last change in
this area was 9 years ago.

Bastien,

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?

> 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.

Best,
Ihor


  reply	other threads:[~2022-05-02 10:08 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 [this message]
2022-05-29 10:08   ` Bastien
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

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=87y1zktfg4.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.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 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).