From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: CamelHump word movement in Emacs Date: Thu, 19 Nov 2009 16:31:56 -0500 Message-ID: References: <873a4akikh.fsf@thinkpad.tsdh.de> <87skcaevsk.fsf@mandingo.thematica.it> <87y6m2ixl4.fsf@thinkpad.tsdh.de> <87aayipbbi.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1258666402 7604 80.91.229.12 (19 Nov 2009 21:33:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2009 21:33:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Giuseppe Scrivano Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 19 22:33:14 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 1NBEcr-0006m4-Hw for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2009 22:33:13 +0100 Original-Received: from localhost ([127.0.0.1]:46412 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBEcq-0002F5-Q2 for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2009 16:33:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBEbl-0001fs-PO for emacs-devel@gnu.org; Thu, 19 Nov 2009 16:32:05 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBEbg-0001ck-QO for emacs-devel@gnu.org; Thu, 19 Nov 2009 16:32:05 -0500 Original-Received: from [199.232.76.173] (port=44764 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBEbg-0001cX-F0 for emacs-devel@gnu.org; Thu, 19 Nov 2009 16:32:00 -0500 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:60692) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBEbd-0007PV-Oe; Thu, 19 Nov 2009 16:31:57 -0500 Original-Received: from faina.iro.umontreal.ca (faina.iro.umontreal.ca [132.204.26.177]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id nAJLVu8w016342; Thu, 19 Nov 2009 16:31:56 -0500 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id 59D253A0FA; Thu, 19 Nov 2009 16:31:56 -0500 (EST) In-Reply-To: <87aayipbbi.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 19 Nov 2009 20:24:33 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV3410=0 X-detected-operating-system: by monty-python.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:117302 Archived-At: >>> I think this feature is generally useful and has nothing to do with >>> C, so I propose to rename it (and its commands and the file) to >>> `subword-mode' or `camelcase-mode'. >> IIRC the same suggestion to make it generic came up right around the >> Emacs-23 freeze, which is why it didn't happen. If someone wants to >> make this generic *right now* he'd better hurry. > Ok, here it is (attached to this mail). I removed all cc-mode > dependencies (which were all about XEmacs and old emacs version > compatibility anyway). > Is it ok to commit? It needs to add some compatibility aliases or adjust the CC-mode (and maybe other?) code that refers to those functions with their old name. Also, I'd prefer to rename the functions so that they all share a `subword-' prefix. > If yes, how do I do that with CVS? cvs delete progmodes/cc-subword.el > and cvs add subword.el? Yes. Please make sure you commit the add and the delete as a single commit rather than as two separate commits. > There seems to be no renaming command. Indeed, there's no support for renaming. > And what do I have to write into the ChangeLog? Usually I write one entry for the new name that says something like "Rename from ". You can also add second entry for the old name that says "Rename to ". You'll also want to add to the entry for the new name the changes performed (renaming of the functions, ...), of course. Stefan