From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: please make line-move-visual nil Date: Mon, 25 May 2009 14:06:18 -0700 Message-ID: <5ED336AF57EB46B69AFB039907C5C5A0@us.oracle.com> References: <23521879.post@talk.nabble.com> <7b501d5c0905131659r1d79ec56s5a59f76e4713edf9@mail.gmail.com> <23532135.post@talk.nabble.com> <87tz3odq3l.fsf@iki.fi> <23538683.post@talk.nabble.com> <87eiuru24b.fsf@iki.fi> <39370.130.55.118.19.1242397867.squirrel@webmail.lanl.gov> <48914.130.55.118.19.1242592120.squirrel@webmail.lanl.gov> <66C6BA04EBCF4B6DAED69E851627D852@us.oracle.com> <87eiue83i7.fsf@cyd.mit.edu> <87my92dmdt.fsf@cyd.mit.edu> <87eiudewtq.fsf@uwakimon.sk.tsukuba.ac.jp> <831vqdubqy.fsf@gnu.org> <32DB30B2393C495A8763CFCDEF4A8E3D@us.oracle.com> <83vdnosyg4.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243285605 5269 80.91.229.12 (25 May 2009 21:06:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 May 2009 21:06:45 +0000 (UTC) Cc: stephen@xemacs.org, emacs-devel@gnu.org To: "'Eli Zaretskii'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 25 23:06:38 2009 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 1M8hNV-0005NS-E6 for ged-emacs-devel@m.gmane.org; Mon, 25 May 2009 23:06:37 +0200 Original-Received: from localhost ([127.0.0.1]:37707 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8hNU-0002FS-It for ged-emacs-devel@m.gmane.org; Mon, 25 May 2009 17:06:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8hN5-000281-0H for emacs-devel@gnu.org; Mon, 25 May 2009 17:06:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8hN0-00025s-Gm for emacs-devel@gnu.org; Mon, 25 May 2009 17:06:10 -0400 Original-Received: from [199.232.76.173] (port=34109 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8hN0-00025n-5i for emacs-devel@gnu.org; Mon, 25 May 2009 17:06:06 -0400 Original-Received: from acsinet12.oracle.com ([141.146.126.234]:44588) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M8hMx-0004Zo-BJ; Mon, 25 May 2009 17:06:03 -0400 Original-Received: from rgminet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by acsinet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4PL5hKU025207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 May 2009 21:05:45 GMT Original-Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by rgminet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4PL6136023959; Mon, 25 May 2009 21:06:01 GMT Original-Received: from dradamslap1 (/98.210.250.59) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 25 May 2009 14:05:57 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <83vdnosyg4.fsf@gnu.org> Thread-Index: AcndegvFJdMvumesSHW4GP6V+ikdBwAANnWA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt004.oracle.com [141.146.116.13] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010207.4A1B0836.00D1:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/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:111089 Archived-At: > If you come too late in the pretest, yes. Too late in which pretest? My guess is that you would have said the same thing for the first pretest, months ago. Emacs development can drag on for years, and it is a convenient excuse that has been used for a long time that "we are too close to the release" to discuss this or that change or new feature. > If we allow non-critical changes beyond certain point, we will > either never make a release or release a buggy version (because > each change might have, and usually has unintended consequences). Do you really think that restoring this to the previous default behavior would cause problems? If so, do you think we could not afford to take the time to fix those problems? Are you sure this isn't just an excuse to ignore the question? > > That's ridiculous. > > That's life. No, it's just one possible policy choice. Please don't confuse the laws of Nature with choices you have made. > And just to keep this in perspective, we are talking about the default > value of an easily customizable option. How critical could a default > be, even if it turns out to be disliked by many? Using "it's not critical" as the only reason to introduce a bad choice is lame. If you want a better perspective, that's the place from which to view this. How about some _reasons_ supporting this change (beyond "I like it")?