unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.g0@libero.it>
To: emacs-devel@gnu.org
Subject: An issue with GDI? [Windows]
Date: Thu, 14 May 2020 15:55:33 +0200 (CEST)	[thread overview]
Message-ID: <2093331550.612340.1589464533075@mail1.libero.it> (raw)

On Windows I use Cascadia Code font for Emacs. This font was introduced with the development of Windows Terminal.

Now I found that a good configuration was with this in the init.el file:

(setq default-frame-alist
      '(
        (width . 115) ; character
        (height . 49) ; lines
        (left . 840); pixel
        (top  .   0); pixel
        (font . "Cascadia Code-12") ; font
        ))

with it I had 46 line of text useful to write plus 3 were for tool bar etc.

Now a few day ago there was an update of the Cascadia Code font. With this new version I have only 37 useful line of text for writing because the gap between lines increased. 

I flagged the issue to Cascadia Code people:

  https://github.com/microsoft/cascadia-code/issues/266

they suggested to use  

  (setq-default line-spacing SOMETHING) 

but it didn't work because it seems that, by default, line-spacing is already at minimum (nil).

Someone there flagged that the issue could be related to the fact that Emacs and some other app (VIM) use the GDI which is too old. See the discussion following the above link.

Would it help to rebuild Emacs without GDI? The build I am using was done e few week ago with master 20200502_225014.

Ciao,
  Angelo.



             reply	other threads:[~2020-05-14 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 13:55 Angelo Graziosi [this message]
2020-05-14 14:40 ` An issue with GDI? [Windows] Eli Zaretskii
2020-05-14 14:54   ` Angelo Graziosi
2020-05-14 14:53 ` Juanma Barranquero
2020-05-14 17:38   ` Eli Zaretskii
2020-05-15 20:47     ` Juanma Barranquero

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=2093331550.612340.1589464533075@mail1.libero.it \
    --to=angelo.g0@libero.it \
    --cc=emacs-devel@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.
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).