Bug 139232 - No fast way to switch static linebreak on/off
Summary: No fast way to switch static linebreak on/off
Status: RESOLVED DUPLICATE of bug 141946
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-26 13:38 UTC by krienke
Modified: 2013-12-17 14:10 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 krienke 2006-12-26 13:38:57 UTC
Version:           2.5.5 (using KDE 3.5.5 "release 45" , openSUSE 10.2)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.2-34-default

I am switching over from nedit to kate. nedit had an option to insert hard linebreaks (a line terminated with cr or cr/lf) at a specific cursorposition.
kate has this option too, as well as another concept, the soft linebreak. Now to quickly turn on/off the linebreak there is an entry in the View (German: Ansicht) menu. However it seems that this switch only controls the dynamic linebreak but not a static linebreak. So whats missing is a way to quickly turn on/off the static linebreak in analogy to the menu entry that controls soft linebreaks. 

At the moment its quite confusing if I turn on static linebreak in kates config and then see a menu entry to turn linebreaks on/off that even in this config does not turn the static line break on/off but the dynamic. Either this switch should be renamed to "dynamic linebreak on/off" and a second menu entry should be added to do the same for static linebreaks or this switch should be "intelligent" in that it controls static linebreaks on/off setting if static linebreaks are enabled in the kate setup and dynamic linebreaks if static linebreaks are disabled in the kate setup.

Thanks
Rainer Krienke
Comment 1 Dominik Haumann 2013-12-17 14:10:18 UTC

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