From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: delete-selection-mode Date: Tue, 22 Apr 2008 12:20:08 +0000 (UTC) Message-ID: References: <004a01c8a1a0$7215cdd0$0200a8c0@us.oracle.com> <878wz9btq8.fsf@jurta.org> <85fxthy4qp.fsf@lola.goethe.zz> <87hcdxz9zr.fsf_-_@jurta.org> <87ve2cfk9x.fsf@stupidchicken.com> <200804201931.m3KJVO4X008875@sallyv1.ics.uci.edu> <858wz8ux2w.fsf@lola.goethe.zz> <480BA779.2080507@gmail.com> <853apguv0s.fsf@lola.goethe.zz> <480BAD5C.4090204@gmail.com> <85prskte96.fsf@lola.goethe.zz> <480BB8C0.4020303@gmail.com> <85abjnu5ss.fsf@lola.goethe.zz> <480C31B9.6060900@gmail.com> <480CC3AD.1050403@gmail.com> <480CEF39.8040307@gmail.com> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1208866932 3990 80.91.229.12 (22 Apr 2008 12:22:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Apr 2008 12:22:12 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 22 14:22:44 2008 connect(): Connection refused 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.50) id 1JoHWC-0008C4-4J for ged-emacs-devel@m.gmane.org; Tue, 22 Apr 2008 14:22:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JoHUd-0003LY-CJ for ged-emacs-devel@m.gmane.org; Tue, 22 Apr 2008 08:21:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JoHUY-0003Kb-7R for emacs-devel@gnu.org; Tue, 22 Apr 2008 08:20:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JoHUQ-0003Jn-ST for emacs-devel@gnu.org; Tue, 22 Apr 2008 08:20:57 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JoHUQ-0003Jk-My for emacs-devel@gnu.org; Tue, 22 Apr 2008 08:20:50 -0400 Original-Received: from cpe-69-204-130-115.nycap.res.rr.com ([69.204.130.115] helo=rattlesnake.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JoHUO-0002vS-50 for emacs-devel@gnu.org; Tue, 22 Apr 2008 08:20:50 -0400 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.115) Tue, 22 Apr 2008 12:20:08 +0000 (UTC) In-reply-to: <480CEF39.8040307@gmail.com> (lennart.borgman@gmail.com) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 1) 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:95761 Archived-At: > No, the arrow keys without shift do NOT deactivate the region ... I think that depends on how you activate the region ... 2) If the region was activated with a shifted arrow key then unshifted arrow keys deactivates the region. I think this is what users accustomed to other applications expects. No, the arrow keys without shift do NOT deactivate the region; they deactivate the HIGHLIGHTING for the region. I am not only able to call `exchange-point-and-mark' (which I invoke with `C-x C-x'), which tells me the region continues to exist, but the highlighting reappears. To reproduce this, call emacs -Q -D and expect point to appear in the *scratch* buffer two lines below the default text. Set the mark by calling `set-mark-command' (which I invoke with `C-SPC'). Move point back three line with `previous-line' (which I invoke by pressing `C-p' three times); you will see the region marked with highlighting. Then mark the line on which point is with `move-end-of-line' with a shift key prefix (which I invoke by pressing Shift-Control-e, S-C-e). Two lines of highlighting disappear. You are only able to exchange point and mark on the line although you can pop to the previous mark by prefixing `set-mark-command' with a `universal-argument' (which I invoke with `C-u C-SPC'). The highlighting stays vanished when you call `set-mark-command' with a `universal-argument' but reappears when you call `exchange-point-and-mark'. To get rid of the initial highlighting, emacs -Q -D --eval="(transient-mark-mode -1)" but presumably no one wants experienced Emacs contributors to evaluate `transient-mark-mode' on the command line since we are asked to provide examples with `emacs -q' or equivalent. (For emacs-devel, I think it is both smart and good to call Emacs without evaluating any expressions by --eval or in a .emacs file.) Today's GNU Emacs CVS snapshot, Tue, 2008 Apr 22 10:19 UTC GNU Emacs 23.0.60.19 (i686-pc-linux-gnu, GTK+ Version 2.12.9) started with emacs -Q -D -- Robert J. Chassell GnuPG Key ID: 004B4AC8 bob@rattlesnake.com bob@gnu.org http://www.rattlesnake.com http://www.teak.cc