Opened 17 years ago
Last modified 15 months ago
#6943 new defect
diff renderer has problems processing file names
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-stable-1.6.x |
Component: | rendering | Version: | |
Severity: | minor | Keywords: | diff bitesized |
Cc: | theultramage@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I discovered a glitch in how trac renders unified diffs. Specifically, depending on the old and new filename, the results will vary a lot.
Following are several examples:
same name
-
x.txt
1 1 this is example text 2 2 and one more line 3 no more lines 3 no more lines
different name, no dot in name (in /trunk, this displays as "(a) xxx vs. (b) yyy")
-
(a) xxx vs. (b) yyy
a b 1 1 this is example text 2 2 and one more line 3 no more lines 3 no more lines
different name, dot in name
-
.txt
xxx yyy 1 1 this is example text 2 2 and one more line 3 no more lines 3 no more lines
for reference, this is an image of how the third case looked like at the time of writing:
as you can see, the 'xxx' and 'yyy' replaced the 'old'/'new' columns, and the title is completely wrong.
Attachments (1)
Change History (18)
by , 17 years ago
Attachment: | trac-diff-glitch.png added |
---|
comment:1 by , 17 years ago
I'm a little confused about why '.' is considered a pathsep in source:trunk/trac/mimeview/patch.py line 130. Removing the . seems to make them a little intuitive. What's the use case for having . there (comparing a.txt and a.txt.old?)
comment:2 by , 17 years ago
Oh, and the 'source code' for the diffs above, if anyone needs to reproduce:
{{{ #!diff --- xxx.txt Wed Oct 17 08:44:43 2007 +++ yyy.txt Wed Oct 17 08:44:58 2007 @@ -1,3 +1,3 @@ this is example text and one more line -no more lines +no more lines }}}
comment:4 by , 17 years ago
Keywords: | diff added |
---|
comment:5 by , 16 years ago
Milestone: | 0.11-retriage → 0.12 |
---|
follow-up: 7 comment:6 by , 16 years ago
It is possible that the intent of the . separator was to handle names in the form file.c.r9999 vs. file.c.r12345. In that case it would display as file.c in the diff header, and 9999 / 12345 in the column headers.
However, when the names are not in this form, the renderer fails badly. And I'm still wondering why in example 2 the file names get substituted by 'a' and 'b' instead of just using the file names in the column headers. Who came up with this thing?
comment:7 by , 16 years ago
Replying to theultramage@…:
It is possible that the intent of the . separator was to handle names in the form file.c.r9999 vs. file.c.r12345. In that case it would display as file.c in the diff header, and 9999 / 12345 in the column headers.
That was the case, IIRC.
However, when the names are not in this form, the renderer fails badly.
Right, I should check for a second dot.
comment:8 by , 15 years ago
Milestone: | 0.12 → next-minor-0.12.x |
---|
comment:9 by , 15 years ago
Version: | devel |
---|
Another example: attachment:7512-r9194.2.patch:ticket:7512.
comment:10 by , 10 years ago
Milestone: | next-minor-0.12.x → next-stable-1.0.x |
---|
comment:11 by , 10 years ago
Description: | modified (diff) |
---|
Link to attachment image instead of remote url.
comment:12 by , 10 years ago
Keywords: | bitesized added |
---|
comment:13 by , 10 years ago
Owner: | removed |
---|
comment:15 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:16 by , 5 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
screenshot of how a diff of two differently named files with a dot renders like