all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Scott Bell <sctb@me.com>
To: 5334@debbugs.gnu.org
Subject: bug#5334: 23.1.91; Term mode prints "0; user@host:~" before each prompt of an interactive SSH session
Date: Fri, 08 Jan 2010 12:25:17 -0700	[thread overview]
Message-ID: <9C978477-0E90-4590-9D27-352F69750FA3@me.com> (raw)
In-Reply-To: <201001081913.o08JDNKn018023@godzilla.ics.uci.edu>

On 2010-01-08, at 12:13 PM, Dan Nicolaescu wrote:

> Scott Bell <sctb@me.com> writes:
> 
>> On 2010-01-07, at 2:37 PM, Dan Nicolaescu wrote:
>> 
>>> Scott Bell <sctb@me.com> writes:
>>> 
>>>> Under GNU Emacs 23.1.91.1 (x86_64-apple-darwin10.2.0, 
>>>> NS apple-appkit-1038.25), Mac OS X 10.6.2, Term mode
>>>> prints the following prompt during an interactive SSH
>>>> session ('ssh host'):
>>>> 
>>>> 0;user@host:~(host:~)$ 
>>>> 
>>>> when PS1 is set to '(\h:\W)\$ ' on the remote host. 
>>>> 
>>>> The string '0;user@host:~' is not displayed when using
>>>> another terminal emulator.	
>>> 
>>> You probably set  PROMPT_COMMAND to something that term.el does not
>>> understand.
>> 
>> That's correct. It looks like PROMPT_COMMAND on the 
>> remote machine is trying to set the title string.
> 
> Does the PROMPT_COMMAND setting come from your .bashrc?
> If yes, then:
> 1. never use it it's overkill, set PS1 to do the same thing instead.
> 2. when setting it, you need to set it conditionally, only when TERM==xterm

It comes from the system bash initialization, I've now 
added PROMPT_COMMAND='' in my .bashrc on the remote 
machine.

>> Should term.el support this escape sequence? If not,
>> should it recognize it but take no action (and also
>> not print undesired output)? This seems like a fairly
>> common feature, but I could be wrong.
> 
> That sequence should only be used for xterm.
> It's been reported that this used to work in term.el in emacs-23.1, no
> idea why it does not work now. I don't have any plans to figure out why
> it does not work anymore, or to do anything about it.

That's certainly fine by me.







  reply	other threads:[~2010-01-08 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9utyuqomkl.fsf@fencepost.gnu.org>
2009-12-13  0:01 ` bug#5198: 23.1; find-file tramp ipv6 not a wildcard Kevin Ryde
     [not found]   ` <87d42drb0u.fsf@gmx.de>
     [not found]     ` <87my1h5onf.fsf@blah.blah>
2009-12-20 10:40       ` Michael Albinus
2010-01-13  0:51   ` bug#5255: marked as done (23.1.90; Wrong prompt in term) Emacs bug Tracking System
2010-01-07 19:07 ` bug#5334: 23.1.91; Term mode prints "0; user@host:~" before each prompt of an interactive SSH session Scott Bell
2010-01-07 21:37   ` Dan Nicolaescu
2010-01-08 17:03     ` Scott Bell
2010-01-08 19:13       ` Dan Nicolaescu
2010-01-08 19:25         ` Scott Bell [this message]
2010-01-13  0:51   ` bug#5334: marked as done (23.1.91; Term mode prints "0;user@host:~" before each prompt of an interactive SSH session) Emacs bug Tracking System

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=9C978477-0E90-4590-9D27-352F69750FA3@me.com \
    --to=sctb@me.com \
    --cc=5334@debbugs.gnu.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.