Re: Could #-ignoring in commit message be smarter?

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Sep 4, 2010, 22:44 UTC
Message-ID: <AANLkTinRE9tLBxCXApvJ9dM9cAUVAAcAWn-N1AkW-bVz@mail.gmail.com>
In-Reply-To: <AANLkTinTxFveiuJvCUyB5Hghj-Jy+=LfhPJhtW1UYkSH@mail.gmail.com>

On Sat, Sep 4, 2010 at 22:30, Sverre Rabbelier <srabbelier@gmail.com> wrote:

Show 12 quoted lines

> Heya,
>
> On Sat, Sep 4, 2010 at 17:24, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>> Where I'm referencing the #-character in the commit message itself for
>> some reason, and due to word wrapping it just *happens* to end up at
>> the start of a line. So the commit message silently becomes:
>
> Isn't this rare enough that it's not really a problem? I mean, sure,
> when it happens it's a PITA, but it's about as painful as doing `git
> commit -m "Yay, it works!"` and having bash history magic blow it
> away. After a while you get used to it and either remember to escape
> the bang, or not use it?

With the bash thing you *notice* it, but in most cases like these what you actually do is *not* notice it, then scratch your head a month later at a commit message that makes no sense.

Anyway, it's obviously not a huge issue since we don't have people complaining about it more often. But it's really annoying when it happens.