| Summary: | Display corruption - wrong characters displayed | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Robin Green <greenrd> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
File I opened in yi which triggered this bug
record of terminal output made by the script utility Timing information, ESSENTIAL for reproducing this bug when using scriptreplay |
||
Created attachment 36488 [details]
File I opened in yi which triggered this bug
Created attachment 36489 [details]
record of terminal output made by the script utility
Created attachment 36490 [details]
Timing information, ESSENTIAL for reproducing this bug when using scriptreplay
Can't reproduce with latest yi and latest konsole. |
Version: (using KDE 4.3.0) OS: Linux Installed from: Fedora RPMs When I open a certain file in a text editor called yi, running in konsole, the file displays incorrectly at a particular point ("��" instead of "∷" - I hope these characters don't get mangled by Bugzilla!) As installing Haskell packages is non-trivial unless you already happen to have the cabal tool installed, I captured exactly what yi sends to konsole using the "script" utility, so that the bug can be reproduced without needing to install yi. Steps to Reproduce: To actually reproduce the bug with yi, download the attached file Exif-borked.hs and type "yi Exif-borked.hs" in a konsole. Or, to get the exact same result without needing to install yi 1. download *both* typescript and typescript.timing, which will be attached to this bug report 2. type "scriptreplay typescript.timing" in a konsole. Actual results: On one particular line you get: fromFile �� FilePath → IO Exif Expected results: fromFile ∷ FilePath → IO Exif Additional info: If scriptreplay fails to reproduce this bug, try adjusting the speed of playback with: scriptreplay typescript.timing typescript FACTOR where FACTOR is a floating-point speed multiplier (see the scriptreplay man page).