From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Markus Triska <triska@metalevel.at>
Cc: 58196@debbugs.gnu.org
Subject: bug#58196: Trivial update to ediprolog
Date: Fri, 28 Oct 2022 13:01:44 -0700 [thread overview]
Message-ID: <CADwFkmkXsqw3nNHNa44g1yqG_aUz3GdgmEjH6k9KNxNPMmZG0A@mail.gmail.com> (raw)
In-Reply-To: <jwvbkpvn8jw.fsf-monnier+emacs@gnu.org>
Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
>> 3) The image in line 101 of README.md is not shown.
>
> I think it's the same problem that the relative link to `factorial.png`
> fails. The case is a bit different in the sense that I can't argue this
> time that the link is redundant anyway :-)
>
> Maybe we could try and recognize those links and redirect them to something like
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/factorial.png?h=externals/ediprolog
> but going through `cgit` is rather inefficient (and recognizing those
> links reliably is not completely trivial either).
We could just copy any image files to the web directory, and add some
heuristics to change any <img>-tags in the HTML (exported from
markdown2, org-mode, etc.) to point there.
For example, we could put factorial.png in
/images/<package-name>/factorial.png. The only cost is a bit of
diskspace, but it shouldn't be a lot as there is already some incentive
to keep down file sizes.
next prev parent reply other threads:[~2022-10-28 20:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 16:59 bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Markus Triska
2022-10-01 12:56 ` Lars Ingebrigtsen
2022-10-01 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01 17:01 ` Markus Triska
2022-10-01 18:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 19:49 ` Markus Triska
2022-10-02 20:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 20:24 ` Markus Triska
2022-10-02 21:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03 0:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 14:34 ` bug#58196: Trivial update to ediprolog Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 21:11 ` Markus Triska
2022-10-28 2:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 3:06 ` Stefan Kangas
2022-10-28 3:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 6:35 ` Eli Zaretskii
2022-10-28 12:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 3:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 16:49 ` Markus Triska
2022-10-28 18:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:01 ` Stefan Kangas [this message]
2022-10-28 20:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:51 ` Stefan Kangas
2022-10-28 21:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-22 16:20 ` Markus Triska
2022-10-22 16:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-23 7:29 ` Markus Triska
2022-10-25 19:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 10:54 ` bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Stefan Kangas
2024-01-10 22:11 ` Markus Triska
2024-01-10 23:18 ` Stefan Kangas
2024-01-14 7:40 ` Markus Triska
2024-01-14 10:17 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkXsqw3nNHNa44g1yqG_aUz3GdgmEjH6k9KNxNPMmZG0A@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=58196@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=triska@metalevel.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.