all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 23819@debbugs.gnu.org
Subject: bug#23819: 25.0.95; display botched badly in xterm window
Date: Wed, 22 Jun 2016 22:04:32 +0300	[thread overview]
Message-ID: <837fdh3v0f.fsf@gnu.org> (raw)
In-Reply-To: <576ADF3D.2050908@cs.ucla.edu> (message from Paul Eggert on Wed,  22 Jun 2016 20:55:57 +0200)

> Cc: 23819@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 22 Jun 2016 20:55:57 +0200
> 
> All this suggests that the issue is not limited to startup. Possibly 
> there are two issues, one at startup and one later. For example, perhaps 
> Emacs is deducing the incorrect terminal type during startup, or perhaps 
> my (typically Ubuntu) clients are reporting an incorrect terminal type 
> during startup.

I think this might happen if we deduce incorrect xterm version.  Can
you modify xterm.el such that it stores the value of 'version' in
xterm--version-handler in a variable?  Then you could report the
values of that variable when you see the problems and when you don't,
and maybe we will learn something that way.





  parent reply	other threads:[~2016-06-22 19:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22  2:01 bug#23819: 25.0.95; display botched badly in xterm window Paul Eggert
2016-06-22 14:54 ` Eli Zaretskii
2016-06-22 18:55   ` Paul Eggert
2016-06-22 19:00     ` Eli Zaretskii
2016-06-22 21:27       ` Paul Eggert
2016-06-22 19:04     ` Eli Zaretskii [this message]
2016-06-23  8:58       ` Paul Eggert
2016-06-23 14:53         ` Eli Zaretskii
2022-01-29 16:55           ` Lars Ingebrigtsen
2022-01-30  2:53             ` Paul Eggert
2022-01-30 16:01               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837fdh3v0f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23819@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.