It sounds like a good workaround but I think there could be a problem. When vim opens there is the message on the first line and two lines below is a commented text which uses # as comment char. Does the char change when you change the comment char? Michal Staša
Santhos.net www.santhos.net +420 773 454 793 michal.st...@santhos.net On 16 May 2014 12:28, Duy Nguyen <pclo...@gmail.com> wrote: > On Fri, May 16, 2014 at 5:18 PM, Michal Stasa <michal.st...@gmail.com> wrote: >> Hi, >> >> I have stumbled on a weird bug. At work, we use redmine as an issue >> tracker and its task are marked by a number starting with #. When I >> commit some work and write #1234 in the message, it works. However, >> later on when I remember that I forgot to add some files and amend the >> commit, vim appears and I cannot perform the commit because the >> message starts with # which is a comment in vim and thus I get an >> error that my commit message is empty. > > A workaround would be "git -c core.commentChar=@ <command> ..." (@ > could be some other character). But maybe git should detect that the > current commit message has leading '#' and automatically switch to > another character.. > -- > Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
