Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Recent change on Emacs master: aggressive word-wrap of header lines in article display
Date: Sat, 11 Dec 2021 21:51:02 +0100	[thread overview]
Message-ID: <87y24qc1c9.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87h7be27vg.fsf@ericabrahamsen.net>

Eric writes:

> I didn't quite follow Bob's progress here, but do you think there's a
> bug to report?

Not really - if anything should be improved it's how Gnus detects that a
face is variable pitch.

I was assuming it was looking at the font, and it isn't.

> It seems weird that header wrapping would depend on variable-pitch or
> not...

It uses the new pixel-fill-region stuff to wrap at the window width. It
makes sense, I think? It's better than at a fixed number of characters,
which looks haphazard for a variable pitch font.

> I realized I mostly don't like the variable pitch because it seems to
> display about 20% larger than the fixed-width fonts, which looks
> terrible (I've seen people complain about this elsewhere, can't remember
> what the issue was).

I guess I have just configured/customized the sizes to match at some
point.

When Lars switched the modeline to variable pitch I switched my
echo-area/minibuffer to variable pitch as well; I think it looks nice
(but it was a bit of a faff to configure:

    ; echo-area face:
    (defface echo-area
      '((t (:family "DejaVu Sans Condensed")))
      "Face for the echo-area")

    ;;; And in custom-set-faces:
    ;;;  '(minibuffer-prompt ((t (:inherit echo-area :foreground "medium blue"))))

    ; This to get variable width font in the line below the modeline:
    (dolist
        (buf (list " *Minibuf-0*" " *Minibuf-1*" " *Echo Area 0*" " *Echo Area 1*"))
      (when (get-buffer buf)
        (with-current-buffer buf
          (setq-local face-remapping-alist '((default (:inherit echo-area)))))))

    ; This as well - and minibuffer-prompt face above!
    (defun my-minibuffer-setup-hook ()
      (buffer-face-set 'echo-area))
    (add-hook 'minibuffer-setup-hook 'my-minibuffer-setup-hook)

gathered from searches/various places :-))


  Best regards,

    Adam

-- 
 "My feet are so tired, my brain is so wired                Adam Sjøgren
  And the clouds are weeping"                          asjo@koldfront.dk



  reply	other threads:[~2021-12-11 20:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 16:32 Adam Sjøgren
2021-12-11 16:58 ` Russ Allbery
2021-12-11 17:41   ` Andreas Schwab
2021-12-11 17:57     ` Adam Sjøgren
2021-12-11 19:27       ` Emanuel Berg
2021-12-11 18:49     ` Russ Allbery
2021-12-11 17:57   ` Adam Sjøgren
2021-12-11 17:31 ` Eric Abrahamsen
2021-12-11 18:01   ` Adam Sjøgren
2021-12-11 18:45     ` Jose A. Ortega Ruiz
2021-12-11 20:01       ` Adam Sjøgren
2021-12-11 19:57 ` Adam Sjøgren
2021-12-11 20:12   ` Adam Sjøgren
2021-12-11 20:23     ` Adam Sjøgren
2021-12-11 20:29       ` Adam Sjøgren
2021-12-11 20:40         ` Eric Abrahamsen
2021-12-11 20:51           ` Adam Sjøgren [this message]
2021-12-11 20:54             ` Eric Abrahamsen
2021-12-11 21:04               ` Adam Sjøgren
2021-12-11 23:21           ` Stephen Berman
2021-12-12  0:15             ` Eric Abrahamsen

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=87y24qc1c9.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).