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: Emacs learning curve Date: Sun, 11 Jul 2010 16:18:12 -0700 Message-ID: <545DBE28C4BB44F79AC10B342F778E96@us.oracle.com> References: <10954D02-E217-49F3-8824-757DA34074AB@gmail.com><83zkxzakr0.fsf@gnu.org> <83pqyva8ms.fsf@gnu.org><87630n6odf.fsf@lola.goethe.zz> <874og670l0.fsf@gmx.de><87k4p257ho.fsf@mail.jurta.org> <87fwzqyn4j.fsf@catnip.gol.com><878w5igcto.fsf@stupidchicken.com><8356A2B998C044939FF9BF8786084025@us.oracle.com> <878w5hws58.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1278890413 27076 80.91.229.12 (11 Jul 2010 23:20:13 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 11 Jul 2010 23:20:13 +0000 (UTC) Cc: 'Juri Linkov' , 'Sebastian Rose' , emacs-devel@gnu.org, 'Tom' , 'Miles Bader' To: "'Chong Yidong'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 12 01:20:11 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 1OY5of-0007Iy-Mu for ged-emacs-devel@m.gmane.org; Mon, 12 Jul 2010 01:20:10 +0200 Original-Received: from localhost ([127.0.0.1]:57518 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OY5oe-0000yS-V4 for ged-emacs-devel@m.gmane.org; Sun, 11 Jul 2010 19:20:09 -0400 Original-Received: from [140.186.70.92] (port=32808 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OY5oY-0000xZ-Pt for emacs-devel@gnu.org; Sun, 11 Jul 2010 19:20:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OY5oX-0005MJ-Fq for emacs-devel@gnu.org; Sun, 11 Jul 2010 19:20:02 -0400 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]:33391) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OY5oQ-0005KI-60; Sun, 11 Jul 2010 19:19:54 -0400 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o6BNJnlH000759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 11 Jul 2010 23:19:50 GMT Original-Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o6BLwNeA007695; Sun, 11 Jul 2010 23:19:48 GMT Original-Received: from abhmt003.oracle.com by acsmt353.oracle.com with ESMTP id 395854961278890289; Sun, 11 Jul 2010 16:18:09 -0700 Original-Received: from dradamslap1 (/10.175.255.126) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 11 Jul 2010 16:18:09 -0700 X-Mailer: Microsoft Office Outlook 11 In-reply-to: <878w5hws58.fsf@stupidchicken.com> Thread-Index: AcshS1wAuQVgHDcmTSu7UM2pxi1koAAAsLeA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090206.4C3A5195.0017:SCFMA4539814,ss=1,fgs=0 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:127074 Archived-At: > > New thread, please. This is a general discussion about the > > Emacs learning curve. > > We're discussing making the Emacs cut/paste behavior closer > to what new users expect. Precisely. And that's what you should call the new thread: "new cut/paste behavior" or "better cut/paste for new users" or some such. That is not part of a _general_ discussion about the Emacs learning curve. Or if it is, then that general discussion becomes a giant pit with multiple rat holes down which subthreads will wind. And those subthreads will not be labeled as such, hence more difficult to find later. Do you want the thread to contain all discussion (implementation details etc.) of each possible change in behavior? Not a good idea. Especially where possible UI changes are concerned - you've seen (I hope) how much of a detour any individual UI change discussion can take. Did someone say "bike shed"?