| Key: |
CIB-1318
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
James French
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 07/Nov/07 11:58 AM
Updated: 12/Dec/08 04:11 AM
|
|
| Component/s: |
Reporting
|
| Affects Version/s: |
1.2.35
|
| Fix Version/s: |
x.x
|
|
|
When pulse intercepts stdout from commands it appends it to the output file with unix line endings when running on windows. This is not an issue when viewing the log file in pulse as the viewer handles them correctly but it is an issue when looking at the file directly in notepad, especially when running local builds. I think the file should be written using native line endings.
|
|
Description
|
When pulse intercepts stdout from commands it appends it to the output file with unix line endings when running on windows. This is not an issue when viewing the log file in pulse as the viewer handles them correctly but it is an issue when looking at the file directly in notepad, especially when running local builds. I think the file should be written using native line endings. |
Show » |
|
Captured output has wrong line endings on windows
I think an issue here is that Pulse distributes builds across multiple platforms, and transfers these logs between them. In that sense having the line endings the same is useful. If Windows line endings are useful for you, though, we could add that as an option. We would need to ensure it does not interfere with post-processing, but I don't think that is a big issue.