unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 42366@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#42366: UTF8 QR codes vs. emacs
Date: Thu, 06 Aug 2020 16:35:53 +0200	[thread overview]
Message-ID: <m2eeoj7sfq.fsf@gmail.com> (raw)
In-Reply-To: <83lfir99d0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Aug 2020 16:44:59 +0300")

>>>>> On Thu, 06 Aug 2020 16:44:59 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: larsi@gnus.org,  42366@debbugs.gnu.org,  jidanni@jidanni.org
    >> Date: Thu, 06 Aug 2020 09:57:04 +0200
    >> 
    Eli> To clarify: the original complaint, AFAIU, was about the display in a
    Eli> GUI frame, in which case the layout is entirely ours.  You are now
    Eli> saying that the problem is on TTY frames, but there we don't control
    Eli> the layout at all.
    >> 
    >> I donʼt think I said that. The TTY frame layout looks ok, the gui
    >> frame one has what looks like extra pixels between the characters.

    Eli> Then I don't think I understand what you are saying when I look at the
    Eli> screenshots you posted.  When you say "between the characters", do you
    Eli> mean between two successive lines (i.e., vertically), or do you mean
    Eli> between two adjacent characters on the same line?

I meant between two adjacent characters (did I mix up the screenshots?
entirely possible).

With Liberation Mono, I see thin horizontal white lines (ie between
successive lines)

I guess we could put this all down to font differences.

Robert





  reply	other threads:[~2020-08-06 14:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 14:20 bug#42366: UTF8 QR codes vs. emacs 積丹尼 Dan Jacobson
2020-07-16 15:59 ` Robert Pluim
2020-07-16 17:44   ` 積丹尼 Dan Jacobson
2020-08-05 10:26 ` Lars Ingebrigtsen
2020-08-05 10:44   ` Andreas Schwab
2020-08-05 10:53     ` Lars Ingebrigtsen
2020-08-05 14:19   ` Eli Zaretskii
2020-08-05 14:22     ` Lars Ingebrigtsen
2020-08-05 14:48       ` Eli Zaretskii
2020-08-05 14:54         ` Lars Ingebrigtsen
2020-08-05 15:03           ` Eli Zaretskii
2020-08-05 15:33             ` Robert Pluim
2020-08-05 15:38               ` Eli Zaretskii
2020-08-05 15:42                 ` Eli Zaretskii
2020-08-06  7:57                   ` Robert Pluim
2020-08-06 13:44                     ` Eli Zaretskii
2020-08-06 14:35                       ` Robert Pluim [this message]
2020-08-06 14:40                         ` Eli Zaretskii
2020-08-05 16:49               ` Andreas Schwab
2020-08-05 17:47             ` Lars Ingebrigtsen

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=m2eeoj7sfq.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=42366@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@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.
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).