From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 00:24:23 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E91CD1065670
	for <freebsd-current@freebsd.org>; Tue,  4 Nov 2008 00:24:23 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81])
	by mx1.freebsd.org (Postfix) with ESMTP id 8BDCE8FC0A
	for <freebsd-current@freebsd.org>; Tue,  4 Nov 2008 00:24:23 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: by mail.geek.sh (Postfix, from userid 1000)
	id BC1F024D26; Tue,  4 Nov 2008 02:04:31 +0200 (SAST)
Date: Tue, 4 Nov 2008 02:04:31 +0200
From: Aragon Gouveia <aragon@phat.za.net>
To: sgk@troutmask.apl.washington.edu
Message-ID: <20081104000431.GA94638@phat.za.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386
Cc: freebsd-current@freebsd.org
Subject: RE: TTY or SSH character echoing issue
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2008 00:24:24 -0000

Hi,

> % ~/trunk/cmd
> 
> The strange behavior is that the ~ character does not
> appear on the terminal until after I enter the / character.

In SSH (OpenSSH in any case), ~ is an escape character if sent on a
newline.  What you describe sounds normal.

It can be changed if necessary.  See the -e argument and EscapeChar
configuration directive in ssh(1).


Regards,
Aragon