Note, KStandardGuiItem::closeWindow and KStandardGuiItem::close uses the
same accelerator, so here I use a variant of KStandardGuiItem::closeWindow
insteand of itself.
Some NVIDIA users still require this option for Konsole to work as
expected
This reverts 66b4a96e93
Thanks to Matthias Kretz kretz@kde.org for patch/info.
BUG: 305307
FIXED-IN: 4.10
So if someone notices later some Qt header is included in the form
of "#include <Class>" instead of the more common form of "#include
<Module/Class>", do not rush changing it.
REVIEW: 105819
That dialog is only about closing one Konsole window , so it should use
KStandardGuiItem::closeWindow() instead of KStandardGuiItem::quit(),
which is for quitting the whole application.
This effectively reverts the change which was made to ask for
confirmation when powering off. That issue needs to be reworked in
next feature release, but for now just revert it since the current
implementation should cause more annoyance than benefit.
BUG: 301458
FIXED-IN: 4.9.0
CCBUG: 127194
Since the menubar and tarbar settings are now global instead of per
profile , those cmdline options are useful to allow users to override
the defautl behavior.
The --hide-menubar and --hide-tabbar options can be used together
to simulate the miminal interface of xterm. I'm not sure whether
--show-menubar and --show-tabbar will be widely used , but add them at
the moment for the sake of completeness.
Now the Qt::WA_TranslucentBackground attribute is always set for the
mainwindow of konsole(regardless of whether compositing is available
when the window is created), just like in konsolepart.
I'm not 100% sure this approach is problem-free, but it works for me so
far under various environments and conditions. Do not hesihate to revert
it if you notice it causes big trouble.
That option is broken for a long time (at least since KDE 4.6.2), yet
there is not a single bug report against it. That is a strong evince
that option is seldom used.
The ideal situation is whenever compositing is available, Konsole
supports translucent background out of box without user guidance.
Sorry for the possible trouble of "resetting" caused by this commit,
but it does not pay off to write extra code dealing with such rename in
master branch
In current code, that method will be effectively called each time a new
session is created. That makes calling setAutoSaveSettings() in the
constructor of MainWindow basically meaningless.
This action will create new tab/session using the same settings(command,
colors, etc) used in current tab/session.
At this moment, this action does not always clone current tab/session
100%. For example, If you change the scrollback setting of current
session temporarily through context menu or dbus method, this action
won't clone the temporary change. Another example is the tab title.
On the other hand, this action works quite well with command line
options(-e, -p, etc) and the 'konsoleprofile' utility.
FEATURE:254976
FEATURE:292518
FIXED-IN:4.9.0
REVIEW:103859
DIGEST:
