unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Font size innacuracies (Windows)
Date: Wed, 02 Mar 2022 22:13:03 +0200	[thread overview]
Message-ID: <83mti8jepc.fsf@gnu.org> (raw)
In-Reply-To: <86lexsn7nh.fsf@csic.es> (juanjose.garciaripoll@gmail.com)

> From: Juan José García-Ripoll
>  <juanjose.garciaripoll@gmail.com>
> Date: Wed, 02 Mar 2022 08:19:30 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> > I don't really understand what problems you are trying to solve.  I
> > see differences in font size and line spacing, but you seem to be
> > bothered by other issues as well, in particular, with variable-pitch
> > fonts, about which you didn't say anything specific
> 
> I have given up variable pitch fonts for the moment. I would like first
> to fix the monospaced font issue. That would make me happy. I mentioned
> the variable pitch font differences, and can provide further examples,
> but I feel monospaced should be easier to debug or understand, and maybe
> solving that also corrects other discrepancies. Don't you agree?

As I don't yet understand well enough what are your problems with
variable-pitch fonts, I cannot say whether looking at fixed-pitch
fonts will identify the same problems or quite different ones.  But
I'm okay talking about the latter if that's what you want.

So what are your problems with fixed-pitch fonts?  The size problem
doesn't sound serious to me: why does it matter that you need to
select a slightly different size in Emacs?

Line spacing differences is probably due to spacing added by VSCode.
You can do that in Emacs as well: see the documentation of the
'line-spacing' variable.  The default in Emacs is not to add any
spacing between lines.



      reply	other threads:[~2022-03-02 20:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 10:24 Font size innacuracies (Windows) Juan José García-Ripoll
2022-03-01 14:21 ` Phillip Susi
2022-03-01 15:16   ` Juan José García-Ripoll
2022-03-01 15:26     ` Robert Pluim
2022-03-01 15:48       ` Juan José García-Ripoll
2022-03-01 17:14     ` Eli Zaretskii
2022-03-02  7:43       ` Juan José García-Ripoll
2022-03-02 20:06         ` Eli Zaretskii
2022-03-01 17:02 ` Eli Zaretskii
2022-03-02  7:19   ` Juan José García-Ripoll
2022-03-02 20:13     ` Eli Zaretskii [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=83mti8jepc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).