From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: position on changing defaults? Date: Sun, 09 Mar 2008 16:53:41 -0400 Message-ID: References: <200803050637.m256bXL3008361@sallyv1.ics.uci.edu> <87hcfkdhqk.fsf@stupidchicken.com> <87d4q8sq9c.fsf@jurta.org> <8763w0n393.fsf@catnip.gol.com> <871w6ounk0.fsf@kfs-lx.rd.rdm> <87ablacdxt.fsf@catnip.gol.com> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1205096170 2087 80.91.229.12 (9 Mar 2008 20:56:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 9 Mar 2008 20:56:10 +0000 (UTC) Cc: juri@jurta.org, cyd@stupidchicken.com, emacs-devel@gnu.org, storm@cua.dk To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 09 21:56:36 2008 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 1JYSZO-0006po-GW for ged-emacs-devel@m.gmane.org; Sun, 09 Mar 2008 21:56:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JYSYq-00049T-Fq for ged-emacs-devel@m.gmane.org; Sun, 09 Mar 2008 16:56:00 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JYSWf-0002KR-6E for emacs-devel@gnu.org; Sun, 09 Mar 2008 16:53:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JYSWc-0002IR-Mr for emacs-devel@gnu.org; Sun, 09 Mar 2008 16:53:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JYSWc-0002ID-5l for emacs-devel@gnu.org; Sun, 09 Mar 2008 16:53:42 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JYSWb-00043X-Jw for emacs-devel@gnu.org; Sun, 09 Mar 2008 16:53:41 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1JYSWb-00019K-6S; Sun, 09 Mar 2008 16:53:41 -0400 In-reply-to: <87ablacdxt.fsf@catnip.gol.com> (message from Miles Bader on Sat, 08 Mar 2008 08:27:42 +0900) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:91915 Archived-At: Actually in usual practice, this feature is used with many other movement commands too, not just the arrow keys -- for instance, S-C-home will highlight to the beginning of the buffer in typical MS-type apps (so in emacs, that should work, and so should S-M-<), and S-M-right will highlight the next word (so in emacs S-M-f should do so as well). I don't think this should be applied to all shift keys. Doing it for S-C-home is ok, and for S-M- arrows, but I think it would be a bad idea to have this apply to ordinary Emacs commands such as C-f and M-f. S-M-< is meaningless because the shift key is required to type <. Either every M-< counts as shifted, or none of them do. There's also the "_non_-shifted movement should _deactivate_ the region" issue which Kim mentioned earlier; it occurs to me that perhaps that could be handled simply by having "shift activation" (activating the region by using a shifted movement command) add a _temporary_ post-command hook, which would take care of deactivating the mark appropriately, and would then remove itself from the post-command-hook list. While it would still be using post-command-hook, I think this would be much better than the current cua mechanism, I agree this is a much better way to use post-command-hook than having it on all the time. It may be ok. However, someone presented another way to do it using transient-mark-mode.