#902 closed defect (fixed)
Log messages don't strip leading whitespace
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control/log view | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
A lot of people around here, out of some weird reflex, enter one or two blank spaces or sometimes even entire lines on their commit messages, specially when doing it with a text editor on the UNIX command line.
I wonder if there's any harm in having Trac ignore leading whitespace while displaying the log messages on the Revision Log screen. As of now, all the entries with blank lines leading to the actual entry appear as "…" on the Revision Log screen.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
Summary: | Skip leading blank lines on log messages → Log messages don't strip leading whitespace |
---|
comment:2 by , 20 years ago
comment:3 by , 20 years ago
Component: | browser → log view |
---|
The magical argument is none, i.e. omitting the argument.
comment:4 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The display of the log message in the revision log (and in the timeline)
is now working as expected in this ticket, since the new util.shorten_line
implementation made in [1561].
I've been trying to fix it myself using util.lstrip, but not knowing much about python, I wonder what is the magical argument for "all whitespace".
Any ideas?