Date: Mon, 19 Sep 2005 20:28:18 -0400 From: "Mike Adewole" <mike@voicenette.com> To: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de> Cc: freebsd-hackers@freebsd.org Subject: Re: syscons and SC_NO_CUTPASTE issue Message-ID: <015401c5bd7a$359fc4d0$6601a8c0@newton> References: <BAYC1-PASMTP03513FF3F9F125D24C2DBDC0990@cez.ice> <c877e0904ae2037688cfbbf6f3492bcc@fs.ei.tum.de>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de> To: "Mike Adewole" <mike@voicenette.com> Cc: <freebsd-hackers@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?015401c5bd7a$359fc4d0$6601a8c0>