[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: [Bug 102868] New: dump configuration variables to stdout
From: Leo Savernik <l.savernik () aon ! at>
Date: 2005-03-30 15:50:41
Message-ID: 20050330175039.102868.l.savernik () aon ! at
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=102868
Summary: dump configuration variables to stdout
Product: kate
Version: unspecified
Platform: Compiled Sources
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: kwrite-devel kde org
ReportedBy: l.savernik aon at
Version: (using KDE KDE 3.4.0)
Installed from: Compiled From Sources
KHTML supports dumping the render tree and dom tree to stdout. This eases debugging \
of KHTML quite a lot.
I suggest that kate provides an action to dump the current values of its \
configuration variables to stdout, accordingly.
This would tremendously ease bug reporting, as the reporter is not forced anymore to \
tell in the report something like:
Option x is set to y, and option z is checked, and w is unchecked, ...
Instead, he would simply paste the dump into the bug report.
A dump would look like this:
kate: indent-width 2;
kate: tab-width 8;
...
and contains all existing configuration variables.
The dump action doesn't need to be plugged into any menu, it would suffice to provide \
a tricky keyboard shortcut (like Alt+Shift+A) to dump the current configuration to \
stdout.
Taking further this idea, kate could automatically add this dump to bug reports \
generated from within kate (Help/Report bugs). \
_______________________________________________ KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic