From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Adam Porter <adam@alphapapa.net>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] CSS improvements
Date: Sun, 11 Sep 2022 10:55:09 -0400 [thread overview]
Message-ID: <jwvmtb6c6cv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y1uq2dpv.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 11 Sep 2022 14:22:04 +0000")
> I've looked around and found at least two examples (that should
> suffice for two patches):
>
> - https://elpa.gnu.org/packages/vertico.html
>
> Look for a code block that is followed by a paragraph. There is
> almost no space above a paragraph, but enough above.
Eww, yes that was poor.
> - https://elpa.gnu.org/packages/ement.html
>
> Section 2.1 has a h4 title that is about the same size as the
> paragraph that follows it. It appears at first as though the title is
> part of the paragraph, especially because the paragraph has a lot of
> space below it.
>
> Btw, Adam it seems there is some peculiar rendering just below the
> "2. Usage" title: On GitHub there appears to be a manual TOC, while
> on the elpa.gnu.org it appears as a list with three empty elements.
Great, thanks, installed.
BTW, regarding the second patch: I'm no fan of underline, so it'd be
nice to find some other solution (bold maybe?). Also, in that
ement.html page, I see now that the "2.1 Bindings" heading is
underlined, but the "2.1.1 Room buffers" is left unchanged whereas the
patch seemed to want to make it italics.
Is it a problem in the CSS or am I missing something?
Stefan
next prev parent reply other threads:[~2022-09-11 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 13:38 [ELPA] CSS improvements Adam Porter
2022-09-11 14:06 ` Stefan Monnier
2022-09-11 14:22 ` Philip Kaludercic
2022-09-11 14:55 ` Stefan Monnier [this message]
2022-09-11 15:04 ` Philip Kaludercic
2022-09-11 20:09 ` Adam Porter
2022-09-11 21:27 ` Stefan Monnier
2022-09-12 8:30 ` Adam Porter
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=jwvmtb6c6cv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).