From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: delete-selection-mode Date: Thu, 18 Mar 2010 19:35:12 +0100 Organization: Organization?!? Message-ID: <87bpelxyu7.fsf@lola.goethe.zz> References: <87ocitw2dl.fsf@stupidchicken.com> <201003130001.o2D01FFQ003489@godzilla.ics.uci.edu> <87vdd1yqe4.fsf@stupidchicken.com> <87eijjzrkd.fsf_-_@mail.jurta.org> <20100317143519.GB4381@muc.de> <87vdcui6oh.fsf@uwakimon.sk.tsukuba.ac.jp> <20100318101223.GB2704@muc.de> <400FB8EA6FB8499AB34297A77E9DCB49@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1268938053 24119 80.91.229.12 (18 Mar 2010 18:47:33 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 18 Mar 2010 18:47:33 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 18 19:47:29 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NsKki-0001b3-2J for ged-emacs-devel@m.gmane.org; Thu, 18 Mar 2010 19:47:28 +0100 Original-Received: from localhost ([127.0.0.1]:38619 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NsKct-0002iC-2X for ged-emacs-devel@m.gmane.org; Thu, 18 Mar 2010 14:39:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NsKZp-00027s-4W for emacs-devel@gnu.org; Thu, 18 Mar 2010 14:36:13 -0400 Original-Received: from [140.186.70.92] (port=58275 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NsKZY-0001uw-EN for emacs-devel@gnu.org; Thu, 18 Mar 2010 14:36:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NsKZF-0007ON-W9 for emacs-devel@gnu.org; Thu, 18 Mar 2010 14:35:39 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:46125) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NsKZF-0007OA-IM for emacs-devel@gnu.org; Thu, 18 Mar 2010 14:35:37 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NsKZ3-0003Zr-Qg for emacs-devel@gnu.org; Thu, 18 Mar 2010 19:35:28 +0100 Original-Received: from p5b2c2262.dip.t-dialin.net ([91.44.34.98]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Mar 2010 19:35:25 +0100 Original-Received: from dak by p5b2c2262.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Mar 2010 19:35:25 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 55 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c2262.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.92 (gnu/linux) Cancel-Lock: sha1:EJdMUsW+MQKZ6avpnF+AtZXqoAg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:122195 Archived-At: "Drew Adams" writes: > The risk you describe exists in theory, and I suppose it occurs > occasionally in practice. But honestly, my impression is that you > simply have not used d-s-mode much or this would not be a problem in > practice. > > 99.999% (no, no proof; just a guess) of computer users out there use > this "risky" behavior everyday, all day long, without exploding (and > without Emac's powerful undo as a remedy). It is an occasional occuring nuisance in one-line entry lines (where it causes extra work), and it would be a perfect menace on multi-line entry, but I don't know of any multi-line entry fields in applications that don't have undo, most particular not with text editors. So please match your descriptions of "the rest of the world" to existing realities. >> the accidental explosion hazard dominates for me (in non-Emacs >> environments, where I can't disable the (mis)feature). > > Well now. That's JUST EXACTLY the problem we're trying to solve by > making the Emacs default behavior resemble the behavior outside Emacs. Applications outside of Emacs don't have a mark concept independent of active regions. Emacs does. Realities don't go away by ignoring them. > Not a problem. It is only when the region is *active* that typing > replaces it. Emacs gives you the best of both worlds: the region can > be active or inactive. With transient-mark-mode, it will be active by default, even when you just wanted to manipulate the mark. > So we should remove t-m-mode as the default? If all region marking operations beginners are accustomed to can create an active region without reverting to transient-mark-mode (and Emacs got there with mouse-selection and shift-selection), why not? It makes things more consistent and avoids accidentally active regions and the connected behavior. >> Is there any evidence that delete-select-mode is instrinsically a good >> thing, disregarding the fact that it has become common? > > Which do you do more often: (a) replace the text in the region or (b) > set mark, move somewhere else, and insert text? Depends on whether I have set the mark for the purpose of creating an active region or not. -- David Kastrup