unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44908-done@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#44908: emacs -nw: view-lossage polluted by termcap / terminfo jazz
Date: Mon, 30 Nov 2020 20:48:28 +0200	[thread overview]
Message-ID: <83360qk7er.fsf@gnu.org> (raw)
In-Reply-To: <87blffdu48.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  30 Nov 2020 11:19:51 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 44908@debbugs.gnu.org,  jidanni@jidanni.org
> Date: Mon, 30 Nov 2020 11:19:51 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Does the below fix the problem?
> 
> Yes, that fixes the problem.

Thanks, installed on the emacs-27 branch.

> > (But maybe we should still arrange for recording these events in the
> > dribble file? or is it impossible to have dribble active at this
> > point?)
> 
> Hm...  is it useful to have the events in the dribble file?

They are not events, they are responses by the terminal emulator to
our queries about its capabilities.  Emacs cannot distinguish between
such characters and those the user types, as they are read in the same
way.

Anyway, I convinced myself that the dribble file cannot be open at
this point, since all the functions that use
xterm--read-event-for-query do that during terminal initialization.

So I'm closing this bug report.





      reply	other threads:[~2020-11-30 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 19:25 bug#44908: emacs -nw: view-lossage polluted by termcap / terminfo jazz 積丹尼 Dan Jacobson
2020-11-29 10:23 ` Lars Ingebrigtsen
2020-11-29 15:47   ` Eli Zaretskii
2020-11-29 16:21     ` Lars Ingebrigtsen
2020-11-29 16:36       ` Eli Zaretskii
2020-11-30 10:19         ` Lars Ingebrigtsen
2020-11-30 18:48           ` 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=83360qk7er.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44908-done@debbugs.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).