Version: (using KDE KDE 3.4.0) Installed from: SuSE RPMs I understand that the reattach feature has been removed in 3.4. I hope there is someway to restore the functionality in some future version. This was a feature I used very often.
For reference: http://marc.theaimsgroup.com/?l=konsole-devel&m=110479099732671&w=2 http://webcvs.kde.org/kdebase/konsole/konsole/konsole.cpp?rev=1.516&view=log Revision 1.492 - (view) (download) (as text) (annotate) - [select for diffs] Mon Dec 20 09:58:36 2004 UTC (2 months, 3 weeks ago) by waba Branch: MAIN Changes since 1.491: +98 -137 lines Diff to previous 1.491 Use normal konsole window for detached sessions
But I want to be able to reattach a session to the original konsole window. On 17 Mar 2005 18:10:28 -0000, Kurt V. Hindenburg <kurt.hindenburg@kdemail.net> wrote: [bugs.kde.org quoted mail]
Kurt, this is a valid wishlist bug. Well, technically it's not a wishlist - it's a regression. In my opinion it should be confirmed and left open until the issue is fixed, however long that may take. Do you have any objections?
Of course this can be left open. However, I don't plan on working on it (way too many more important stuff). As I stated in Comment #1, Waldo was the one who rewrote the detach code and dropped the re-attaching. If people really needs this, consider using screen (although I don't personally use it).
Funny you should mention screen, because I use it as well as sometimes attaching and detaching konsole tabs. In particular, it kind of bugged me that once I detached a session (that I had configured with particular settings) that I couldn't bring it back to my main window, because I had only wanted to temporarily detach it to look at something side-by-side for a moment and didn't want to have to recreate my single-window multiple-tab 'setup'. Perhaps this is an esoteric use of detachable sessions. Nevertheless, thank you for an excellent piece of software. Krishna P.S. Using Konsole's tabs in conjunction with multiple gnu screen sessions is a truly valuable work visualization tool for me. I can noticeably work better because of how both utilities complement each other * when handling quick interrupts in unrelated tasks/mental contexts, * when quickly jumping between related ones, or * when using multiple (terminal-based) tools in a single mental context.
I have the same problem. And yes, I use "screen" a lot. In fact now I have five konsole windows open. One of them has four sessions open. In other, NINE sessions open. Most sessions are "screen". In KDE 3.3, when one of my ssh sessions closed, I just reopened it and detach/reattach the other sessions in order to keep my "natural" session order. Now I MUST close all later sessions and reopen/reauthentificate/rejoin my "screen" sessions, etc. Slow and disturbing. And relogin in some sessions are not an option (no "screen" there, logout kills the task I was doing there). And I agree. This is not a wishlist issue. It is a regresión from KDE 3.3. Thanks for your time and attention.
I just discovered the "ctrl + shift" thing. Much better now, but without a "reattach" option, the "detach" one is of no use and DANGEROUS.
The only way I see this happening, if it is possible to drag tabs between Konsole windows. With the work being done for KDE4, it will be quite a while.
Seconded for this bug. Maybe it'll get fixed for KDE 3.4.4 or 3.5.x?
This is disturbing. Konsole in 3.5 is actually worse than in 3.3. Please fix the tab reattaching bug.
I have begun work in KDE 4 to give Konsole more flexible handling of views and sessions internally, so implementing this will become easier and less messy. I don't plan to implement this in KDE 3.x however. > This is disturbing. > Konsole in 3.5 is actually worse than in 3.3. > Please fix the tab reattaching bug. Please avoid gross generalisations. There has been a regression in one area of Konsole, but there have been many other improvements from earlier versions. This is evident to me when I use the old (from KDE 3.2) version of Konsole on the PCs in my university's labs.
You're right, I may have been too harsh, and it's good to know it will be possible to be get this feature back in KDE 4. I can't recall if I ever used Konsole from KDE 3.2; I run KDE 3.5 on my machine and maintain a copy of KDE 3.3 in a separate place so I can run that version's Konsole.
This may not make any difference if it simply "can't be done", but I see this far more as a bug than a wish. For the loss of the ability to use this intentionally, which is what most people have expressed here, there are workarounds like the aforementioned screen (But since everyone reading this uses Konsole, there is no need to go into the advantages Konsole has over screen). But for the fact that an accidental/unintended action of detaching a session could cause an irreversible event falls squarely in the category of a bug. Looked at from this perspective it would seem better for the detaching functionality to be disabled/removed altogether until it can be fully re-implemented without regressions than exist in its half functioning state where irreversible actions are allowed to take place without warning ( BTW I am not proposing warnings or confirmations as that would be hideously cumbersome.) Once a week during rapid tab manipulation I will irreversibly loose a session to the “detach session” divinities. I doubt that I am alone. Cheers, JPD
> But for the fact that an accidental/unintended action of > detaching a session could cause an irreversible event falls > squarely in the category of a bug I understand your point, but I am fairly sure that there would be more complaints if the detach functionality was removed altogether than if it was left in with the inability to reattach. It is not impossible to re-implement this in KDE 3.5.x, it just needs someone with the time and motivation to do so. > Once a week during rapid tab manipulation I will irreversibly > loose a session to the “detach session” divinities How does the accidental detaching of a tab usually happen? It might be possible to make a small UI change to make this less likely.
Fixing #75653 will also fix this. *** This bug has been marked as a duplicate of 75653 ***