From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: HTML display in Gnus
Date: Tue, 05 May 2020 10:24:10 +0200 [thread overview]
Message-ID: <87o8r2vlg5.fsf@gnus.org> (raw)
In-Reply-To: <87eery2417.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Tue, 05 May 2020 10:13:08 +0200")
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> After an hour fiddling with shr-width and gnus-html-frame-width to no
> avail, I realized that the latter is only used with the gnus-w3m
> renderer, while mm-shr let-binds the former to
>
> (if shr-use-fonts
> nil
> fill-column)
>
> This is surprising (to me), since shr-width's docstring says that an
> integer value works just fine even when shr-use-fonts is set:
Yeah, that looks like a bug, I think... fill-column should either be
used in both cases or none?
> I've modified the snippet above to bind shr-width to fill-column
> unconditionally, and it works wonders for me. Maybe this condition
> makes no sense anymore? As things stand, if shr-use-fonts is set, the
> user loses control over the line width.
>
> WDYT?
The problem is that the user may have a window that's narrower than
fill-column, so I think it may be a misfeature to rely on that variable
in any case. See bug#40909 -- I think the solution here may be to
introduce a max-width variable for shr instead of having a shr-width
variable.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-05-05 8:24 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 18:28 Add some aliases for re-related functions Yuan Fu
2020-05-02 18:39 ` Eli Zaretskii
2020-05-02 18:43 ` Yuan Fu
2020-05-02 21:21 ` Stefan Monnier
2020-05-02 22:27 ` Drew Adams
2020-05-03 8:33 ` Michael Albinus
2020-05-03 19:07 ` Drew Adams
2020-05-02 19:29 ` Alan Mackenzie
2020-05-02 19:48 ` Yuan Fu
2020-05-02 20:10 ` Philippe Vaucher
2020-05-02 20:13 ` Philippe Vaucher
2020-05-03 14:16 ` Eli Zaretskii
2020-05-04 3:09 ` Richard Stallman
2020-05-04 14:28 ` Eli Zaretskii
2020-05-04 17:12 ` Dmitry Gutov
2020-05-04 17:35 ` Eli Zaretskii
2020-05-04 17:42 ` Dmitry Gutov
2020-05-04 17:46 ` Eli Zaretskii
2020-05-04 17:53 ` Dmitry Gutov
2020-05-02 21:09 ` Alan Mackenzie
2020-05-02 21:51 ` Philippe Vaucher
2020-05-03 9:43 ` Alan Mackenzie
2020-05-03 15:00 ` 조성빈
2020-05-02 22:41 ` Stefan Monnier
2020-05-03 17:14 ` Alan Mackenzie
2020-05-04 10:07 ` João Távora
2020-05-03 14:16 ` Eli Zaretskii
2020-05-03 16:20 ` Yuri Khan
2020-05-03 16:42 ` Eli Zaretskii
2020-05-03 16:50 ` Dmitry Gutov
2020-05-02 21:33 ` Stefan Monnier
2020-05-02 22:10 ` Dmitry Gutov
2020-05-02 22:18 ` Eric Abrahamsen
2020-05-02 22:49 ` Stefan Monnier
2020-05-02 23:13 ` Dmitry Gutov
2020-05-03 3:55 ` Stefan Monnier
2020-05-04 0:29 ` Dmitry Gutov
2020-05-04 3:11 ` Stefan Monnier
2020-05-02 22:44 ` Drew Adams
2020-05-03 3:26 ` Stefan Monnier
2020-05-03 4:37 ` Drew Adams
2020-05-03 8:05 ` Philippe Vaucher
2020-05-03 9:55 ` Alan Mackenzie
2020-05-03 10:26 ` tomas
2020-05-03 15:15 ` Eli Zaretskii
2020-05-03 19:47 ` Drew Adams
2020-05-04 7:32 ` Philippe Vaucher
2020-05-04 8:20 ` Sending plaintext with Gmail (was: Add some aliases for re-related functions) Kévin Le Gouguec
2020-05-04 8:45 ` Philippe Vaucher
2020-05-04 15:09 ` Sending plaintext with Gmail Stefan Monnier
2020-05-04 15:25 ` Kévin Le Gouguec
2020-05-04 15:29 ` Lars Ingebrigtsen
2020-05-05 8:13 ` HTML display in Gnus (was: Sending plaintext with Gmail) Kévin Le Gouguec
2020-05-05 8:24 ` Lars Ingebrigtsen [this message]
2020-05-05 9:26 ` HTML display in Gnus Kévin Le Gouguec
2020-07-17 17:14 ` Kévin Le Gouguec
2020-05-04 15:39 ` Sending plaintext with Gmail Andreas Schwab
2020-05-04 16:51 ` Add some aliases for re-related functions Drew Adams
2020-05-04 17:10 ` Drew Adams
2020-05-04 18:17 ` Philippe Vaucher
2020-05-04 18:33 ` Drew Adams
2020-05-05 2:48 ` Richard Stallman
2020-05-04 3:08 ` Richard Stallman
2020-05-04 10:16 ` João Távora
2020-05-04 3:04 ` Richard Stallman
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=87o8r2vlg5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=schwab@linux-m68k.org \
/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).