unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rpluim@gmail.com
Cc: larsi@gnus.org, 42366@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#42366: UTF8 QR codes vs. emacs
Date: Wed, 05 Aug 2020 18:42:11 +0300	[thread overview]
Message-ID: <83wo2d85gs.fsf@gnu.org> (raw)
In-Reply-To: <83y2mt85mp.fsf@gnu.org> (message from Eli Zaretskii on Wed, 05 Aug 2020 18:38:38 +0300)

> Date: Wed, 05 Aug 2020 18:38:38 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: larsi@gnus.org, 42366@debbugs.gnu.org, jidanni@jidanni.org
> 
> What exactly is surprising here?  In a TTY frame, Emacs doesn't
> control the layout: the terminal emulator does.  Emacs just sends
> codes to the terminal device, and that's it.

To clarify: the original complaint, AFAIU, was about the display in a
GUI frame, in which case the layout is entirely ours.  You are now
saying that the problem is on TTY frames, but there we don't control
the layout at all.





  reply	other threads:[~2020-08-05 15:42 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 [this message]
2020-08-06  7:57                   ` Robert Pluim
2020-08-06 13:44                     ` Eli Zaretskii
2020-08-06 14:35                       ` Robert Pluim
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=83wo2d85gs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42366@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --cc=rpluim@gmail.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.
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).