Sometimes logfiles contain some strange characters outside the normal ascii
range if the application crashed. It seems geany simply stops loading the
file at the point of the invalid characters without providing a hint that
it did so.
So either geany should report that it did not load the full file or even
better simply load the file and keep the characters if possible.
In the file I am going to attach, geany only loads up to line 249, but
there are more lines in the file...
Nobody/Anonymous
General
None
Public
|
Date: 2009-11-23 22:02 Addressing your first issue: the attached logfile doesn't open in Geany |
|
Date: 2009-11-12 16:05 > I think somehow the very long lines in the testfile are related. |
|
Date: 2009-11-06 10:48 Hmm, some more testing showed that this is some other problem. Sometimes |
| Filename | Description | Download |
|---|---|---|
| samplecutoff.log.gz | Sample zip of a file that shows the problem | Download |
| Field | Old Value | Date | By |
|---|---|---|---|
| priority | 5 | 2009-11-12 16:05 | ntrel |
| summary | Textfile displayed truncated without warning on illeg. chars | 2009-11-06 10:48 | centic |
| File Added | 349752: samplecutoff.log.gz | 2009-11-06 10:26 | centic |