No more misspellings in your VCS commit comments

How many times you wished you could edit your last VCS commit comment to correct a misspelling?

Now you will notice such mistakes because IntelliJ IDEA 10 checks the spelling in the comment field.

And it not just spellchecks the text, it runs the Spelling inspection on it and uses your custom dictionary too. Hit Alt+Enter/⌥↩ on an underlined word and fix it as you normally fix things in IntelliJ IDEA code editor.

Spellchecker is also enabled in other dialogs throughout the IDE, e.g. Search/Replace dialog.

Try IntelliJ IDEA X EAP and let us know your impressions.

This entry was posted in New Features and tagged , , . Bookmark the permalink.

6 Responses to No more misspellings in your VCS commit comments

  1. Igor Kolomiets says:

    Projects’ directory location shown in the example is very inspiring :)

  2. Mike says:

    That really is a great feature — could it be extended to force format via regex? For example, show an error if the commit message doesn’t match the following:

    (?s)(ABC|DEF|XYZ)-d+:.*

  3. Simon Knott says:

    I haven’t had a chance to try it yet, but is it possible to turn off the spell checker for code (including String constants), but leave it on for javadoc, comments and commit messages?

    I deal with a lot of XML parsing and the spell checker is something which always gets turned off straight away, because it highlights so much stuff! It’s a shame because I’d like to leave it on for the human-readable stuff.

  4. yole says:

    Mike,
    The spell checker does not force anything; it just highlights the errors and lets you decide whether to fix them. The kind of validation you desire can be implemented by writing a plugin; I don’t think we plan to implement it as a core feature.

    Simon,
    You can go to Settings | Inspections | Spelling | Typo and turn off “Process code” and “Process literals”. This should do what you want.

  5. Kevin says:

    Is it possible to use Templates or Live Templates in check-in comments?

    We have a check-in comment template (Issue #, Review #, Changes, Testing etc..) we’d like to use for every check-in, and are looking for an easier way to pre-populate it. Currently the VCS comment editor (Perforce in our case) doesn’t seem to let us expand any Live Templates.

    Support for actually creating templates (similar to File Templates) or use of Live Templates (allowing us to bind a template to some character string) would be very useful.

  6. @Kevin: No such functionality now. Your feature request is welcome in our issue tracker: youtrack.jetbrains.net/issues/IDEA

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">