Edgewall Software

Opened 17 years ago

Closed 17 years ago

Last modified 15 years ago

#1181 closed defect (fixed)

multiline log messages

Reported by: dieter.verfaillie@… Owned by: Christian Boos
Priority: normal Milestone: 0.9
Component: general Version: 0.8
Severity: normal Keywords: multiline log message
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


Multiline log messages are not being displayed properly in the timeline view and changeset view. In the timeline view all is displayed as one long string (could be normal, to keep the overview small?) In the changeset view, sometimes the newline is shown as [ [ BR ] ] (without the spaces), sometimes it works as expected.

Environment: I'm working from unix like systems with rapidsvn 0.7.0, trac 0.8, subversion 1.1.1, apache 2.0.52

Attachments (1)

Screenshot.jpg (15.9 KB ) - added by dieter.verfaillie@… 17 years ago.
screenshot of changeset view

Download all attachments as: .zip

Change History (5)

by dieter.verfaillie@…, 17 years ago

Attachment: Screenshot.jpg added

screenshot of changeset view

comment:1 by Christian Boos, 17 years ago

I experienced a similar problem (see [1535] and the initial problem report wrongly done in #48).

But I recently tried to do a few commits with the same message, using different methods (svn ci -m, svn ci -F <file> with LF and CRLF line endings, TortoiseSVN) and viewed the resulting changesets with a Trac running on the trunk: the problem seems to be gone.

The systematic escaping of newlines by [[BR]] was done in [776], in order to fix #352.

This solution introduces other side-effects: see #1206 for example

comment:2 by Christian Boos, 17 years ago

Owner: changed from Jonas Borgström to Christian Boos
Status: newassigned

Ok, I understand the issue now: The problem disappeared because I was using Trac on Windows, and [r776-present] does the escaping that way: text.replace(os.linesep, '[[BR]]' + os.linesep)

On Windows, the linesep is CRLF, but the message as provided by subversion is using LF as line separator…

Therefore the problems (but also the #352 feature) are not occuring on Windows… Conversely, #352 works when Trac is running on UNIX, at the expense of the problems described here and in #1206.

comment:3 by Christian Boos, 17 years ago

Resolution: fixed
Status: assignedclosed

Fixed in [1561]

comment:4 by Christian Boos, 15 years ago

Milestone: 0.9

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christian Boos to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.