Re: [Kile-devel] Editor messing up my tex-file

[Thibaut C. <co...@kd...>]

Le Lundi 3 Novembre 2003 09:52, Michael Frotscher a =E9crit :
> Somehow the editor of 1.6 (contrary to 1.5.2) keeps messing up my
> tex-document by removing carriage returns and line feeds it sort of
> regards unnecessary. This makes the document rather hard to read.
>
> And yes, the option "remove trailing spaces" is not set.
>
> Any idea?

  Yes, I have the same problem and I've seen that before, those few=20
times when I did not have Kile and had to use KWrite to edit a TeX=20
file. I'm pretty sure it's related to the change to the new editor=20
widget... The KDE editor has a rather special way to deal with long=20
lines.

  In the "old" Kile editor, a long line was displayed as several lines=20
but no carriage return character was inserted in it. It was close to=20
the Emacs way, in fact.
  In the new Kile editor, as well as in Kate or KWrite, I've never=20
really understood how it works. Most of the times it seems that long=20
lines are just broken into lines (real ones, with carriage return=20
inserted) that fit the maximum length.

  As a result, opening a file from the old Kile results in a very=20
confusing management of those long lines. If you happen to have=20
activated the editor option "Automatically go to new line" (or=20
something like that), the conversion from the old management to the new=20
can destroy the carriage return characters. Hence the mess in your=20
files...
  I've just spent two hours correcting one of my own documents because=20
of that. I should have known, it had happened to me before...

  Advice: don't ask for automatic creation of new lines, just do it by=20
hand. Once it's done, activate the option. At least, this way, it=20
doesn't mess up with your files and you still see what you're doing.

  I'd really like the editor widget to have an option like Emacs: when=20
using the "old" mode (as defined above), you can see a small arrow at=20
the end of some lines. It means that even if the line seems broken into=20
several lines, there is no carriage return, it's really one big line.=20
It would avoid that kind of confusion...
  It's the only negative point I've seen with the switch to the new=20
editor in Kile, but it's a hell of a bad point... The blame goes to=20
KDE, though, I'll probably file a bugreport about it, as I should have=20
done long ago.

  Regards,

=2D-=20
Thibaut Cousin
Web : http://www.thibaut-cousin.net