loggerhead - doesn't detect new line

That is by design, as line breaks will break the formatting.
You can see your full commit message if you actually go to the revision: http://bazaar.launchpad.net/~timekpr-maintainers/timekpr/trunk/revision/33

Not preserving newlines seems to make any commit message with newlines in it somewhat unreadable.

Has the changes page changed since last September, or am I missing something - I'm struggling to see how preserving the line breaks would break the formatting.

Sorry to comment on a bug marked won't fix, and if I've missed something obvious.

I had this same problem and hacked together a fix. A patch against revision 277 is attached. It can also be found at: https://code.launchpad.net/~pnutzh4x0r/loggerhead/loggerhead-convert-comment-newlines

It's rather unfortunate that this is marked won't fix, since it is really annoying to have long comments unreadable. I also don't see how it breaks formatting.

Didn't realise Martin had marked this won't fix -- I disagree too! Reopening.

My original fix added unnecessary <br/>'s to the annotated view, so please disregard the previously attached patch. Fortunately, I fixed this error with latest commit in my local branch above. Now, fix_width will behave normally (in the same way as in mainline) unless you pass convert_newlines=True:

util.fix_width(some_string, convert_newlines=True)

This should allow backwards compatibility for the fix_width function and allow for the new line converstion functionality.

Well, I actually made the annotate view not use fixed_width in a recent branch, so I removed that again from your branch and merged it :)

Thanks for all your recent patches!

Wonderful! thank you :)