From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yamaoka@jpl.org, 28591@debbugs.gnu.org
Subject: bug#28591: 27.0.50; xterm-set-window-title
Date: Fri, 29 Sep 2017 09:05:42 -0400 [thread overview]
Message-ID: <20170929130542.tk47k53s5dibjfoe@logos.localdomain> (raw)
In-Reply-To: <20170929115700.ag4xni2tckiak4nt@logos.localdomain>
On 29/09/17 at 07:57am, Mark Oteiza wrote:
> On 29/09/17 at 01:45pm, Eli Zaretskii wrote:
> > > Date: Tue, 26 Sep 2017 00:08:08 -0400
> > > From: Mark Oteiza <mvoteiza@udel.edu>
> > > Cc: 28591@debbugs.gnu.org
> > >
> > > > > 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.
> >
> > That'd be too drastic, I think. The code did work for you, right? So
> > it definitely works for some configurations out there, and I think we
> > could leave it in Emacs, turned off by default, and allow its optional
> > activation with the proper warning that it might not work for some
> > versions of xterm.
>
> Everything except foregrounding a client works (I did not test this),
> where the following occurs:
Correction: deleting a frame does not restore the window title as
Katsumi pointed out.
I have a shell hook that sets the window title which I keep
forgetting to disable when testing this
next prev parent reply other threads:[~2017-09-29 13:05 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170929130542.tk47k53s5dibjfoe@logos.localdomain \
--to=mvoteiza@udel.edu \
--cc=28591@debbugs.gnu.org \
--cc=eliz@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 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.