Bug 174965 - Content of text-file not shown
Summary: Content of text-file not shown
Status: RESOLVED DUPLICATE of bug 167767
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-12 18:11 UTC by kujub
Modified: 2008-11-13 20:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kujub 2008-11-12 18:11:27 UTC
Version:           3.1.3 (using 4.1.3 (KDE 4.1.3), Arch Linux)
Compiler:          gcc
OS:                Linux (i686) release 2.6.26-vanilla

When opening any text file which contains only text but no carriage return / newline the text is not rendered. Instead it looks like an empty file.

As soon as the window is resized horizontally the text is shown as normal.

This is very annoying. And yes there are such files in the wild: Some XML-files, lock-files of openoffice.org 3 ...

Loaded Plugins:

Find files tools view
File system Browser
Terminal tool view

How to Reproduce:

Open konsole and enter:
echo -n 'some text' > some.txt
kate some.txt

Expected Behavior:

Render text contained in file opened.

Additional information:

This affects kwrite too requiring a vertical resize.
Comment 1 Andreas Pakulat 2008-11-12 20:56:12 UTC
May I suggest to check for possibly duplicates next time, before submitting a bug. That helps us actually fixing those that still exist :)

*** This bug has been marked as a duplicate of bug 167767 ***
Comment 2 kujub 2008-11-13 14:16:03 UTC
Sorry about that and for disturbing you again,
but those bug is neither listed in
 "KDE Bug Report Wizard -> Check for Duplicate Bug Reports" (weird imho)
nor in
 "KDE Bug Report Wizard -> Check for Duplicate Bug Reports -> View all open bug reports for product kate." (because already marked as RESOLVED)

The bug was marked RESOLVED at 2008-08-18, but still exists in 4.1.2 and 4.1.3 (!) Shouldn't fixes like this be backported to 4.1.x or is 3.5.x still the only "stable" KDE-version wich benefits from bug-fixes ? (confused)

Comment 3 Andreas Pakulat 2008-11-13 17:57:16 UTC
Hmm, that sounds like a bug in our bugtracker. Just tested and I also couldn't find it by searching for "kate newline" even though it definetly has "newline" in the title. May be worth a bugreport against the bugzilla or bugs.kde.org product (can't recall the exact name right now).

Backports should be done into 4.1.x, but might not always be possible, or might be forgotten. All I can say is that this works with KDE4 from trunk/.
Comment 4 kujub 2008-11-13 19:13:58 UTC
(In reply to comment #3)
> Hmm, that sounds like a bug in our bugtracker. Just tested and I also couldn't
> find it by searching for "kate newline" even though it definetly has "newline"
> in the title. May be worth a bugreport against the bugzilla or bugs.kde.org
> product (can't recall the exact name right now).

It is bugs.kde.org and yes searching it really sucks.

> Backports should be done into 4.1.x, but might not always be possible, or might
> be forgotten. All I can say is that this works with KDE4 from trunk/.

Should we reopen the bug because of that ? (might help for 4.1.4 or 4.1.5)

Comment 5 Andreas Pakulat 2008-11-13 20:06:38 UTC
unfortunately bugzilla doesn't allow to specify in a proper way that a bug is only fixed on a particular version (except comments) so re-opening won't do much good, as developers would have to remember to close it again in 2 months. Apart from that there will only be 4.1.4, no 4.1.5.