From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 20 00:19:23 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9AD716A41F for ; Tue, 20 Sep 2005 00:19:23 +0000 (GMT) (envelope-from adewole@sympatico.ca) Received: from BAYC1-PASMTP01.hotmail.com (bayc1-pasmtp01.bayc1.hotmail.com [65.54.191.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA18843D46 for ; Tue, 20 Sep 2005 00:19:23 +0000 (GMT) (envelope-from adewole@sympatico.ca) Message-ID: X-Originating-IP: [69.158.176.82] X-Originating-Email: [adewole@sympatico.ca] Received: from newton ([69.158.176.82]) by BAYC1-PASMTP01.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Sep 2005 17:18:56 -0700 Message-ID: <015401c5bd7a$359fc4d0$6601a8c0@newton> From: "Mike Adewole" To: "Simon 'corecode' Schubert" References: Date: Mon, 19 Sep 2005 20:28:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-OriginalArrivalTime: 20 Sep 2005 00:18:56.0737 (UTC) FILETIME=[E3E94D10:01C5BD78] Cc: freebsd-hackers@freebsd.org Subject: Re: syscons and SC_NO_CUTPASTE issue X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 00:19:24 -0000 ----- Original Message ----- From: "Simon 'corecode' Schubert" To: "Mike Adewole" Cc: Sent: Sunday, September 11, 2005 10:01 AM Subject: Re: syscons and SC_NO_CUTPASTE issue > On 08.09.2005, at 11:25, Mike Adewole wrote: > > I propose that: > > (d) the next release of the generic kernel should be compiled with > > SC_NO_CUTPASTE > why? I find cut+paste really useful per default. > besides, can't this be controlled with a sysctl? > cheers > > simon > the problem with the default setting is that it makes mouse support in a TUI environment nearly impossible without patching/recompiling the kernel. For instance, adding mouse support to sysinstall would be easier if cut and paste is delegated to the dialog utility (or other TUI environment) instead of being implemented directly by syscons. sysctl would be the perfect solution but I assumed it may be too big a change for some people. cheers Mike