From: Lars Ingebrigtsen <larsi@gnus.org>
To: Y. E. <yet@ego.team>
Cc: 53205@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#53205: 28.0.90; [PATCH] GNU ELPA: Provide more control over linked documentation
Date: Thu, 08 Sep 2022 15:55:32 +0200 [thread overview]
Message-ID: <87fsh2ynqj.fsf@gnus.org> (raw)
In-Reply-To: <m2r19a1hyx.fsf@ego.team> (Y. E.'s message of "Fri, 14 Jan 2022 16:59:18 +0200")
Y. E. <yet@ego.team> writes:
> (with-temp-buffer
> (elpaa--call-sandboxed
> - t "makeinfo" "--no-split" "--html" docfile "-o" tmpfile)
> + t "makeinfo" "--no-split" "--html" docfile
> + "-c" (format "AFTER_BODY_OPEN=<div id=\"pkg-%s\">"
> + (car pkg-spec))
> + "-c" "PRE_BODY_CLOSE=</div>"
> + "--css-ref" "../../html/doc-html.css" ; TODO: Use robust path.
> + "-o" tmpfile)
> (message "%s" (buffer-string)))
> (rename-file tmpfile html-file t)
> ;; FIXME: Use `push' in Emacs≥28
> #+END_SRC
>
> '<elpa>/html/doc-html.css' then could contain:
>
> #+BEGIN_SRC css
> #pkg-company img {
> /* Until images output is fixed, hide them. */
> display: none;
> /* max-width: 360px; */
> /* margin-bottom: 0.8em; */
> }
> #+END_SRC
>
> Would it be fine to follow this route?
This was half a year ago, but there was apparently no followup here.
Stefan, do you have any comments?
prev parent reply other threads:[~2022-09-08 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:47 bug#53205: 28.0.90; [PATCH] GNU ELPA: Provide more control over linked documentation Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 6:23 ` Lars Ingebrigtsen
2022-01-13 13:20 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 15:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 11:11 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 14:59 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:55 ` Lars Ingebrigtsen [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsh2ynqj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53205@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yet@ego.team \
/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.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).