emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "Rudolf Adamkovič" <salutis@me.com>, 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, 30 May 2022 11:29:07 +0800	[thread overview]
Message-ID: <87leujofzw.fsf@localhost> (raw)
In-Reply-To: <87czfw4pnd.fsf@bzg.fr>

Bastien <bzg@gnu.org> 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.

Should we create a help request for updates.orgmode.org?

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

This reminds me that Org does not actually consist of a single repo. At
this point, we at least have org, org-contrib, worg, and orgweb.

Should we create a dedicated project page in sr.ht to group everything
together nicely?

> I think this nice js hack should live in a dedicated repository, along
> with a dedicated HTML exporter that enables it.

What about backwards compatibility?

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

Should we change the default value of org-html-infojs-options then?
Alongside with possibly changing the relevant ox-publish code.


  reply	other threads:[~2022-05-30  3:29 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
2022-05-30  3:29     ` Ihor Radchenko [this message]
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:

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


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