Bug 75507 - knotes replaces tabs with spaces after restart
Summary: knotes replaces tabs with spaces after restart
Status: RESOLVED FIXED
Alias: None
Product: knotes
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Brade
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-18 12:02 UTC by Georgios E. Kylafas
Modified: 2005-01-01 20:40 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 Georgios E. Kylafas 2004-02-18 12:02:32 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
 
OS:          Linux

When I close and reopen knotes, any tab characters contained in notes are replaced by spaces. Tab width is set to 4.
Comment 1 Michael Brade 2004-03-06 23:23:54 UTC
Fixed today, that was a tough one... Thanks for the report!
Comment 2 sami-kde 2004-09-15 13:34:10 UTC
This bug was fixed for a while, but reappeared in knotes 3.3 that comes with Debian unstable, package knotes_3.3.0-2_i386.deb.
Comment 3 Georgios E. Kylafas 2004-09-21 15:59:51 UTC
I confirm this for knotes 3.3 (Gentoo Packages, again), as well.
Did something change in libical since 3.2.x?
Comment 4 Michael Brade 2004-09-21 17:36:56 UTC
Yes, damn, must have. I didn't notice it though and will have time again only 
in two weeks to hack on it. Sorry.

Cheers,
  Michael
Comment 5 Stephen Depooter 2004-11-10 17:31:20 UTC
Do you have any idea what changed in libical/libkcal and where to look for it?
If you have any pointers for what to look for I might be able to fix this.
Comment 6 Michael Brade 2004-11-10 22:20:10 UTC
No, sorry. The problem is that I don't know libical and therefore have to 
debug it. The first bet would be to have a look at the code I fixed with my 
last commit and see if that was changed. But my project thesis took longer 
than planned, that's why I haven't had the time to fix it yet :( Shouldn't 
take long now anymore, but I better stop promising without knowing for 
sure...

Comment 7 Michael Brade 2004-11-28 15:54:53 UTC
Embarrassing... I can't even reproduce the bug. Nothing has been changed in 
libical either since I fixed it last time. It should work since KDE 3.3.0 at 
least.

Comment 8 Stephen Depooter 2004-11-28 22:36:27 UTC
I can reproduce this at work, which is KDE 3.3.0.  But at home here on CVS HEAD from last week sometime, it works fine.

I was digging through the code you changed last time, and nothing seems wrong there.  I think as far as I could tell, that QT might have been messing things up when doing the reading and saving.  I'm not sure how or what though.
Comment 9 Stephen Depooter 2004-12-09 18:08:37 UTC
Looking at the diffs between CVS HEAD and what we have at work (KDE 3.3.0) there don't appear to be any changes in knotes or libical that causes this.  possibly a change in qt or kdelibs somwehere?
Comment 10 Michael Brade 2004-12-11 13:13:02 UTC
> Looking at the diffs between CVS HEAD and what we have at work (KDE
> 3.3.0) there don't appear to be any changes in knotes or libical that
> causes this.
yes, that's what I thought.

> possibly a change in qt or kdelibs somwehere? 
I don't think so. Qt hasn't changed, and there's no special functions in KDE 
libs that I'm using in KNotes. Maybe your distributor screwed things up?

Comment 11 Michael Brade 2005-01-01 20:40:23 UTC
Ok, closing this bug now. Works here, works with the latest release and should 
work generally. If it doesn't, it's most likely the distributor who is to 
blame.

Cheers,
  Michael