-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support KDE Konsole in run_in_new_terminal function #2023
Conversation
I am honestly a big fan of this as I use Konsole all the time; could you please rewrite .stdout.read() to .communicate()[0] so we can merge it |
@Arusekk done |
This might not work with py2 potentially, but merging, since it is a huge feature for me. |
@Arusekk I found that I was incorrectly defining the MainWindow number, it is not equal to the Window number (from the environment variables), so the split may occur in the wrong terminal. The only solution I have found is checking each MainWindow for activity ( |
I see the problem; the MainWindow instances are numbered first-gap, while Window are numbered unique increasing. This should not result in splitting the wrong terminal, though. The only case that this can go wrong is if you close one of many in-process konsole windows, and then open a new konsole window in the same process. And the new window won't be able to split, but the incorrect number will be higher than any window's number, resulting in qdbus saying |
In the process of using pwndbg together with pwntools, I had an incorrect terminal split. I had |
* Support KDE Konsole in run_in_new_terminal function * Rewrite '.stdout.read()' to '.communicate()[0]'
If KDE Konsole is detected (by the presence of the
$KONSOLE_VERSION
environment variable), a terminal will be split.