| Summary: | Gideon/KATE does not remember state of default breakpoint/bookmark menu selection | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Jon Smirl <jonsmirl> |
| Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | SVN | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jon Smirl
2003-09-11 05:33:58 UTC
Hmm.. I guess. I hardly think this qualifies as a bug, but... If implemented, should this be remembered on 1. "session basis" - last set value for this project or 2. "application wide" - last set value is used for all projects all the time ? It is definitely broken right now. I can set the default to breakpoint, then open another file and it jumps back to bookmark. hmm.. good point. I hadn't noticed. Definitely qualifies as a bug. Upon closer inspection, this one might present a problem... The mark selection menu is part of katepart, so responsibility for persisting the selected option would have to lie there. But.. wouldn't this mean that the selected option would be enforced for all applications that embeds katepart, as I doubt katepart can (or should attempt to) tell the difference? Reassigning to katepart. As far as I can tell, we can't affect it. Leaving it up to the kate developers to figure out if it is currently possible to implement this feature. its simple to fix in kate, will let this value be remembered in config global for all views, if kdevelop is clever enough to give it's own kconfig objects to the read/writeConfig methodes of ktexteditor that won't influence other apps using katepart (and kate or kwrite even not if they are not that clever, as we store our stuff in the katerc or kwriterc) fixed in cvs now |