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: Tue, 31 May 2022 08:51:20 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <87leujofzw.fsf@localhost> (Ihor Radchenko's message of "Mon, 30 May 2022 11:29:07 +0800")
Ihor Radchenko <email@example.com> writes:
> Should we create a help request for updates.orgmode.org?
Yes, although this is not a pressant issue IMHO.
> Should we create a dedicated project page in sr.ht to group everything
> together nicely?
There is such a SourceHut project: https://sr.ht/~bzg/orgmode/
The README for the project is that of https://git.sr.ht/~bzg/orgweb
because I had to select one, but it is not really what is needed here.
I could actually create a meta-repo with only a README that I would
use for this project.
Also, I could mirror org-mode.git on SourceHut as a read-only repo
that would be part of this project - I'm vary that this may confuse
users, though. WDYT?
>> 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.
I don't think we need to change the default value of
org-html-infojs-options yet - let's do it when org-info.js is made
available for everyone on another URL.
next prev parent reply other threads:[~2022-05-31 6:54 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
2022-05-31 6:51 ` Bastien [this message]
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).