From owner-svn-src-all@FreeBSD.ORG Fri Oct 19 18:36:47 2012 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84F22257; Fri, 19 Oct 2012 18:36:47 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 3B8A88FC16; Fri, 19 Oct 2012 18:36:46 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa03.fnfis.com (8.14.4/8.14.4) with ESMTP id q9JIaKdM004247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 19 Oct 2012 13:36:43 -0500 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.2.309.2; Fri, 19 Oct 2012 13:36:06 -0500 Subject: Re: svn commit: r241701 - in head/usr.sbin/bsdconfig: . include share MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="koi8-r" From: Devin Teske In-Reply-To: <20121019170216.GB92674@FreeBSD.org> Date: Fri, 19 Oct 2012 11:36:04 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: <44662B32-966F-4573-987D-EEE8A07C5A16@fisglobal.com> References: <201210181843.q9IIhs6N099621@svn.freebsd.org> <20121019055442.GA9108@FreeBSD.org> <20121019170216.GB92674@FreeBSD.org> To: Alexey Dokuchaev X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.431, 0.0.0000 definitions=2012-10-19_04:2012-10-19,2012-10-19,1970-01-01 signatures=0 Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Devin Teske , src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2012 18:36:47 -0000 On Oct 19, 2012, at 10:02 AM, Alexey Dokuchaev wrote: > On Fri, Oct 19, 2012 at 08:22:36AM -0700, Devin Teske wrote: >> On Oct 18, 2012, at 10:54 PM, Alexey Dokuchaev wrote: >>> How come that new dialog(1) lacks functionality of the old one? >>=20 >> SVN r217309 brought in cdialog to replace our the [unmaintained] dialog. >>=20 >> cdialog is different, but mostly compatible with its predecessor. >=20 > Ah, I guess it might explain the shitty colors I see on newish FreeBSD > screenshots of dialog(1). >=20 I actually prefer the colors in cdialog (more specifically, I prefer the la= ck-of-yellow!). Whenever I want a reminder of bad colors, I run "sade" (which links against= the old libdialog now named lib*o*dialog). When I'm on the physical console, I don't have nearly as much trouble with = the yellow color used both for the title bar and for the hline at the botto= m, but when I'm (say) ssh'd from Mac OS X, that text is just completely unr= eadable to me. I'm curious about how others feel about the use of yellow (specifically tha= t old dialog(1)/libdialog used it a lot and new cdialog-based dialog(1)/lib= dialog doesn't use it hardly at all). I for one embrace my new cdialog overlord. >> The benefits of cdialog far out-weigh the few problems that were reported >> (and then quickly fixed). >=20 > OK, but do we plan to retain the look of original dialog(1)? >=20 It is possible to change the colorings by first creating (if you don't alre= ady have one) a ~/.dialogrc by executing the below command: dialog --create-rc ~/.dialogrc followed by editing said file. So while the default look and feel has changed, it's possible to customize = it to your liking. HINT: I bet if you ran the above command on FreeBSD-8 or lower, it would ma= ke dialog(1) in FreeBSD-9 and higher look like its predecessor. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.