Home/ Questions/Q 990573
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T05:57:55+00:00

I’ve noticed that git seems to use different vim settings any time I’m writing

  • 0

I’ve noticed that git seems to use different vim settings any time I’m writing a commit message. I have the git+svn install off Macports, and I’ve checked the $MYVIMRC variable: it’s set to the correct file. Still, every time I go to commit a message I have a restriction on 80 characters per line, case sensitive search, and none of the plugins I’ve installed.

It’s probably something silly. Would appreciate a pointer as to what it is.

EDIT: Actually I just checked: my plugins work. It’s only the column width of 80 chars that miraculously comes alive when I type out commit messages.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That’s not a bug, it’s a feature!

    Vim knows about a lot of filetypes – including git commits (and interactive rebases, and config…). There are syntax definitions and ftplugins (filetype-activated plugins) for each of these. One of the settings in the commit ftplugin is textwidth=72. This is done so that the output of git log will look good in a standard-width terminal. If you really want to change it, you could go edit the plugin, but I’d really recommend keeping it.

    The plugin should be in <vim-directory>/vimXX/ftplugin/gitcommit.vim. The XX is the version number, e.g. 72 for version 7.2, and the leading component is generally something like /usr/share/vim.

    P.S. The plugin also defines a command DiffGitCached, which will open the diff to be committed in a preview window. Handy!

    • 0