unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Giuseppe Scrivano <gscrivano@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: CamelHump word movement in Emacs
Date: Thu, 19 Nov 2009 16:31:56 -0500	[thread overview]
Message-ID: <jwvy6m2i4wd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87aayipbbi.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 19 Nov 2009 20:24:33 +0100")

>>> 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 <oldname>".  You can also add second entry for the old name
that says "Rename to <newname>".  You'll also want to add to the entry
for the new name the changes performed (renaming of the functions, ...),
of course.


        Stefan




  reply	other threads:[~2009-11-19 21:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  8:46 CamelHump word movement in Emacs Tassilo Horn
2009-11-19  8:57 ` Giuseppe Scrivano
2009-11-19 11:05   ` Tassilo Horn
2009-11-19 15:22     ` Stefan Monnier
2009-11-19 19:24       ` Tassilo Horn
2009-11-19 21:31         ` Stefan Monnier [this message]
2009-11-20  7:25           ` Tassilo Horn
2009-11-20 13:43             ` Eli Zaretskii
2009-11-20 14:05               ` Tassilo Horn
2009-11-20 14:13                 ` Eli Zaretskii
2009-11-20 14:31                   ` Tassilo Horn
2009-11-20 14:22             ` Stefan Monnier
2009-11-20 14:37               ` Tassilo Horn
2009-11-20 16:07                 ` Stefan Monnier
2009-11-20 17:19                   ` Tassilo Horn
2009-11-20 15:09         ` Chong Yidong
2009-11-20 15:34           ` Tassilo Horn
2009-11-20 21:36             ` Chong Yidong
2009-11-20 16:10         ` Dan Nicolaescu
2009-11-21  0:44           ` Miles Bader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvy6m2i4wd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=gscrivano@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).