[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=461085

--- Comment #10 from tcanabrava at kde.org ---
Markus,

I did indeed consider a less intrusive way to develop the plugin, but then
I realized that a lot of people that answered my request to "how do you use
profiles in konsole" were using the *profile* manager as a way to interact
with different SSH connections (some of them having over 20 - 40 profiles
that differed only in name and the ssh command. This made me think that a
plugin *for* ssh was needed.

I do understand your concerns and I plan to implement a way to disable /
unload plugins in the future, but time has been complex at the moment so I
ask for a bit of patience (or help on the code).
*I* ould personally accept a patch that allows to unload plugins (such the
one in kate) so people can use the plugins if they want, and not being
forced to.


On Sat, Jun 3, 2023 at 1:14 PM Markus Wernig <bugzilla_noreply at kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=461085
>
> --- Comment #9 from Markus Wernig <public at wernig.net> ---
> (In reply to tcanabrava from comment #7)
>
> > Please take in consideration the time I did put on the plugin system, to
> > not say things like "I was fortunate to not realize that the plugins
> > exist", I understand that some frustration can exist, but understand also
> > that this is helping a lot of people that were used to have a visual aid
> to
> > ssh in other systems - such as windows - to migrate to konsole and linux
> in
> > general.
>
> Dear @tcanabrava
>
> I did not want to belittle your work. I am sure the plugin was developped
> with
> much expertise, diligence and the best intentions.
> I also see your point (potentially alleviating the switch to Linux for
> users of
> graphical SSH managers like putty or SecureCRT).
>
> But is there not also the point of long-standing Linux users who do not
> require
> such alleviation? Is it fair to force them to use the plugin even if they
> did
> not choose in any way to install it?
>
> I personally do not think so. Users should have a choice, which software
> they
> want to use.
>
> SSH is a central part of my everyday work, and I choose to manage it in a
> way
> that best fits my needs. Since the sshmanager plugin cannot be configured
> to do
> the same, I do not want to use it.
>
> But that is currently not possible.
>
> Mostly, because you chose to integrate it so tightly with Konsole. It even
> parses the command line and acts upon that (which, by the way, is something
> neither putty nor SecureCRT have ever done - and rightly so). I fail to
> see how
> that would help any Linux novice, on the contrary. In the best of cases it
> will
> make them get used to a way of managing SSH that exists nowhere else and
> will
> be useless to them once they switch to another terminal emulator or desktop
> system. In the worst of cases it will interfere with what they want to do
> and
> drive them away.
>
> Have you ever considered a less intrusive way of integrating sshmanager
> with
> Konsole? I think if it were more of a standalone application (that could
> still
> use the konsole framework, profiles etc.), it would be even more useful -
> to
> Linux novices and existing users alike.
>
> For the time being, I stand with my request for a way to disable the
> plugin.
> This does not mean, however, that I do not appreciate the great work that
> you
> and the other KDE devs are doing!
>
> Currently, I have to do this after every Plasma update:
> chmod 700 /usr/lib64/qt5/plugins/konsoleplugins/konsole_sshmanagerplugin.so
> (Which, by the way, also disables the Ctrl-Shift-F2 shortcut).
>
> Best regards
> Markus
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.