Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: hput via "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Change header font sizes
Date: Fri, 25 Mar 2022 12:52:09 -0400	[thread overview]
Message-ID: <87bkxuug92.fsf@local.lan> (raw)

GNU Emacs 29.0.50 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo
version 1.16.0, Xaw3d scroll bars) of 2022-03-05
-------       -------       ---=---       -------       -------

I only noticed the change in the visible header face/size? sometime in
the last 2 mnths (or so).

I'd like to revert to old sizes which I think were the same as the
font/face sizes in composition mode

I notice the larger changed sizes in visible headers while reading
posts or mail:

'C-u C-x ='  shows those header font as:

ftcrhb:-PfEd-DejaVu Sans-bold-normal-normal-*-16-*-*-*-*-0-iso10646-1 (#x36)

Visible header size is smaller (Not changed) when composing a post or
mail.  That is, it looks normal to me.

'C-u C-x =' shows that to be:
x:-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso8859-1 (#x4E)

 (I think that is the Default font)

I'd like to see that same (smaller ) header size when reading.

I'm not sure if the change is something I did inadvertently, if that
kind of change can even be done inadvertently.  Or possibly something
changed in emacs trunk.

The version of emacs I'm posting with is only a few days after doing
'git pull' and building from scratch with 'make bootstrap'

Can the change I am noticing be reverted somehow or must I configure
it myself for each header?

If the latter, I am a bit at sea figuring out how to do that.

I've never fully understood the differences between 'face' and 'font'
I do see that 'face' includes more than just size such as color, etc.

What I am seeing looks bad enough to be ungainly.

Can anyone show a basic step thru as to what I must do to make the
headers in reading mode, look like those in composition mode?

The only mention of customizing seem to be about customizing what to
display in the output:

-------       -------       ---=---       -------       -------
Full ouput of 'C-u C-x =' on a header in question:

            position: 67 of 457 (14%), column: 2
            character: w (displayed as w) (codepoint 119, #o167, #x77)
              charset: ascii (ASCII (ISO646 IRV))
code point in charset: 0x77
               script: latin
               syntax: w 	which means: word
             category: .:Base, L:Strong L2R, a:ASCII, l:Latin, r:Roman
             to input: type "C-x 8 RET 77" or "C-x 8 RET LATIN SMALL LETTER W"
          buffer code: #x77
            file code: #x77 (encoded by coding system utf-8-emacs-unix)
              display: by this font (glyph code):
    ftcrhb:-PfEd-DejaVu Sans-bold-normal-normal-*-16-*-*-*-*-0-iso10646-1 (#x5A)

Character code properties: customize what to show
  name: LATIN SMALL LETTER W
  general-category: Ll (Letter, Lowercase)
  decomposition: (119) ('w')

There are text properties here:
  face                 gnus-header-name
  original-date        "Fri, 25 Mar 2022 10:58:47 -0400"



                 reply	other threads:[~2022-03-25 16:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87bkxuug92.fsf@local.lan \
    --to=info-gnus-english@gnu.org \
    --cc=hputn3@zohomail.com \
    /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).