unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Oteiza <mvoteiza@udel.edu>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 28591@debbugs.gnu.org
Subject: bug#28591: 27.0.50; xterm-set-window-title
Date: Tue, 26 Sep 2017 00:08:08 -0400	[thread overview]
Message-ID: <20170926040808.zofxjqrl735zeye3@logos.localdomain> (raw)
In-Reply-To: <b4mwp4mb84y.fsf@jpl.org>

On 26/09/17 at 12:45am, Katsumi Yamaoka wrote:
> On Mon, 25 Sep 2017 13:24:24 -0400, Mark Oteiza wrote:
> > Mark Oteiza <mvoteiza@udel.edu> writes:
> 
> >> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 
> >>> The feature looks nice but I want the original title to come back
> >>> when Emacs exits or suspends (even if it launches with -Q).
> 
> >> I posted a patch here
> >> https://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00728.html
> 
> >> but at the moment it's not clear to me how to handle other terminals
> >> that use an xterm- family terminfo.
> 
> I use:
> 
> $ xterm -v
> XTerm(327)
> 
> $ xterm&
> Then the title bar of the launched xterm shows "xterm".
> 
> > The following lightly tested patch appears to do the right thing here.
> 
> Thanks.  I tried.  But nothing seems to be changed unfortunately.
> When I run `emacs -nw' in the xterm, the title becomes to
> "emacs@hostname" but the original title "xterm" is not pushed to
> the `xterm-window-title-stack' variable.  And the title does not
> come back to "xterm" when I exit or suspend Emacs -nw.
> 
> I tried adding `(error "XXX")' to the `xterm--title-handler'
> function but nothing happens (with no error).  So, the function
> doesn't seem to run by way of `xterm-push-title-stack'.

Grr, thanks.  I see what you're seeing in XTerm 330.  I am stumped--not
sure this is possible in Elisp, so I'm inclined to revert.





  reply	other threads:[~2017-09-26  4:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  9:43 bug#28591: 27.0.50; xterm-set-window-title Katsumi Yamaoka
2017-09-25 12:15 ` Mark Oteiza
2017-09-25 17:24   ` Mark Oteiza
2017-09-26  0:45     ` Katsumi Yamaoka
2017-09-26  4:08       ` Mark Oteiza [this message]
2017-09-29 10:45         ` Eli Zaretskii
2017-09-29 11:57           ` Mark Oteiza
2017-09-29 12:51             ` martin rudalics
2017-09-29 13:03               ` Mark Oteiza
2017-09-29 13:05                 ` martin rudalics
2017-09-29 13:05             ` Mark Oteiza
2017-09-29 17:34               ` Eli Zaretskii
2017-09-30 19:26                 ` Mark Oteiza
2017-10-05 10:16                   ` Eli Zaretskii
2017-10-08 20:21                     ` Mark Oteiza
2017-10-09  6:23                       ` Eli Zaretskii
2017-10-09 12:40                         ` Mark Oteiza
2020-08-24 13:39                           ` Lars Ingebrigtsen
2017-09-29 17:29             ` Eli Zaretskii
2017-09-30 19:27               ` Mark Oteiza

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=20170926040808.zofxjqrl735zeye3@logos.localdomain \
    --to=mvoteiza@udel.edu \
    --cc=28591@debbugs.gnu.org \
    --cc=yamaoka@jpl.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).