Bug 204922

To be clear, if I had 5 Konsole3 tabs open when logging out, Konsole would be open with 5 tabs on next login, and any of those that had contained MC sessions, would still have them, all without having to configure anything whatsoever to make happen. My normal usage is plain shells in 1, 3 & 5, and mc in 2 & 4.

(In reply to comment #1)
> To be clear, if I had 5 Konsole3 tabs open when logging out, Konsole would be
> open with 5 tabs on next login, and any of those that had contained MC
> sessions, would still have them, all without having to configure anything
> whatsoever to make happen. My normal usage is plain shells in 1, 3 & 5, and mc
> in 2 & 4.

The issue here was that in KDE3 if MC is installed, you automatically have ´New Midnight Commander´ and ´New Root Midnight Commander´ under Session menu.
In KDE4 you have to create MC profile manually.

The fact is KDE3 konsole ships a couple of profiles (shell,mc,screen) by default and only lists profiles whose command is available in current system. The KDE4 konsole only ships one profile(shell) by default and lists all profiles even when the corresponding command is not available in current system .

So the KDE4 konsole looks not as handy/smart as the KDE3 konsole in this case. But I think the KDE3 way has one big problem: it might surprise/confuse/scare users. After installing mc/screen, users will find new profiles "coming-from-nowhere". Or, after removing mc/screen, users will find old profiles 'disappearing-for-no-reason'. The KDE4 konsole do not have this problem because it behaves in a stupid way.

I think creating a new profile for mc/screen manually is really easy, so the lost handy feature is really not a big deal, especially when taking into account the potential problem mentioned above.

Created attachment 161356 [details]
attachment-252072-0.html

Any more information?

On Sun, Sep 3, 2023 at 5:08 AM Felix Miata <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=204922
>
> Felix Miata <mrmazda@earthlink.net> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |mrmazda@earthlink.net
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

KDE3 never stopped being my primary DE, in part because of this behavioral change in Konsole, which I use a LOT. TDE's Konsole works just as it has in KDE3. I keep several installations of Plasma and TDE, for testing and staying somewhat familiar with them, with Plasma mainly in Tumbleweed.

Created attachment 161397 [details]
attachment-407032-0.html

Sorry, i asked for more information, not history.
What do you mean Konsole needs to respect midnight commander sessions, how
do we can know what sessions are happening in midnight commander, links to
the api, etc.


On Mon, 4 Sep 2023 at 02:03 Felix Miata <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=204922
>
> --- Comment #5 from Felix Miata <mrmazda@earthlink.net> ---
> KDE3 never stopped being my primary DE, in part because of this behavioral
> change in Konsole, which I use a LOT. TDE's Konsole works just as it has in
> KDE3. I keep several installations of Plasma and TDE, for testing and
> staying
> somewhat familiar with them, with Plasma mainly in Tumbleweed.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

I'm not a programmer. I don't know how Konsole3 remembers what it remembers, it just does. Lately it has been plain bash shell in tab 1, root MC in tab 2, root shell in tab 3, root shell in tab 4, and plain MC in tab 5, all in one window on virtual desktop 1. Then in another window on virtual desktop 2, root bash shells in first 2 tabs, and plain bash shells in tabs 3-5.