From owner-freebsd-questions@freebsd.org Wed Sep 30 14:32:43 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63C76A0BDD9 for ; Wed, 30 Sep 2015 14:32:43 +0000 (UTC) (envelope-from danglingpointer@outlook.com) Received: from BAY004-OMC4S19.hotmail.com (bay004-omc4s19.hotmail.com [65.54.190.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 517B51CA3 for ; Wed, 30 Sep 2015 14:32:42 +0000 (UTC) (envelope-from danglingpointer@outlook.com) Received: from BAY169-W42 ([65.54.190.200]) by BAY004-OMC4S19.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 30 Sep 2015 07:31:37 -0700 X-TMN: [MOd+/qgp8WJcPFSfvBrsSizySRQhkx7e] X-Originating-Email: [danglingpointer@outlook.com] Message-ID: From: Dangling Pointer To: "freebsd-questions@freebsd.org" Subject: git diff encoding issue when running via Hyper-V Date: Wed, 30 Sep 2015 14:31:36 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 30 Sep 2015 14:31:37.0303 (UTC) FILETIME=[B6B4A670:01D0FB8C] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2015 14:32:43 -0000 Hi=2C=20 When I run FreeBSD 10.1 or 10.2 x64 via Hyper-V on Windows 10=2C the encodi= ng of `git diff` command emits cluttered text (with lots of "ESC[m" noise) = like: ESC[31m-setup_dirs()ESC[m ESC[32m+ESC[mESC[32msetup_dirs2()ESC[m instead of: -setup_dirs()+setup_dirs2() I don't know what to make of it. I get this behavior in Hyper-V console run= ning FreeBSD's csh and bash as well as when I SSH into the VM. FWIW=2C I have never observed this issue with CentOS and Ubuntu VM running = on the system. Can somebody please let me know if this is a bug or do I need to configure = something? =