Bug 311945 - After closing tex file commented paragraph breaks.
Summary: After closing tex file commented paragraph breaks.
Status: RESOLVED DUPLICATE of bug 303598
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: Git
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL: http://img10.imageshack.us/img10/2241...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-19 17:17 UTC by Darkelly
Modified: 2013-02-01 08:56 UTC (History)
0 users

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 Darkelly 2012-12-19 17:17:09 UTC
If was dynamic word wrap, after closing tex file  some paragraphs  break. In the commented paragraphs it couses the part of the commented paragraph become a part of the main text. This problem doesn`t appear until file open.

rus. Если в файле сделать динамический перенос строк, рвутся некоторые абзацы. Пока файл открыт, абзацы можно подтянуть как на 1 рисунке и сохранение не влияет на это. Но после закрытия файла, снова абзацы разрываются. В результате куски коментариев появляются в тексте. 

Reproducible: Always

Steps to Reproduce:
1. Open a file with a big paragraph and comment some big paragraph.
2. Close the file and reopen it.
3. Press F10 for a dynamic word wrap.
4. Commented paragraphe is broken and some its part became a part of the main text.
5. Pull up a string which is broken - now whole paragraph is commented again.
6. Save, close and reopen the file. Press F10 ----> paragraph is broken on 1023 simbol.
Actual Results:  
Press F10 ----> paragraph is broken on 1023 simbol.

Expected Results:  
Press F10 ----> paragraph does not break on 1023 simbol.
Comment 1 Michel Ludwig 2013-01-31 20:30:46 UTC
Forwarding to KatePart.
Comment 2 Dominik Haumann 2013-02-01 08:56:55 UTC
Please go to the config page to the Open/Save item, and either increase the line length limit, or disable it by setting the value to 0.

*** This bug has been marked as a duplicate of bug 303598 ***